Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio for Mac

msdn.microsoft.com

Post reply on HN
Print view View original

251–260 of 435 posts

Re: Visual Studio for Mac

#251

Post by bengalister »

ubernostrum wrote: post #77
SiVal wrote: post #17

So Microsoft is treating the Mac more seriously as a professional platform while Apple is treating it less seriously? I'm not saying this in a snarky way; I mean it literally as a change of corporate strategies in both companies. Microsoft seems to be saying, If you are a pro mainly using the Mac for professional work, we want to do a better job of empowering you, and Apple seems to be saying, If you are a pro mainly…

Meanwhile, a "pro" user who's actually used the new Macbook Pro weighs in: http://www.huffingtonpost.co.uk/thomas-grove-carter/one-prof... Spoiler alert: he doesn't agree with the assessment of HN users who haven't actually used it.

I bought a MBP in April this year. It was my first Mac. I am quite happy with it, the retina screen & touchpad are really good, but I don't think my next one will be a MBP. Windows has now the Windows Linux Subsystem and it is actually quite good for Linux development on Windows. (I manually updated it to 16.04). I don't need Cygwin anymore and it compiles to ELF format. I don't know if Microsoft will keep it but if the goal is to attract developers who deploy on Linux, it might attract all the ones that cannot migrate to Linux due to proprietary apps or don't want to tweak their system. I recently tried to use Linux (Ubuntu 16.04 and 16.10) as my primary desktop (once again I think I tried every year since year 2000) but still failed having 2 screens supported with 2 graphic cards, bluetooth headset being connected and sound through HDMI. There's no killer app for me on the Mac (I don't use GarageBand or final cut pro), maybe I miss the viewer that is nice for pdf pages re-ordering or pdf merging (could not find free equivalent on Windows).

Re: Visual Studio for Mac

#252

Post by pjmlp »

Hydraulix989 wrote: post #72

This is absolutely amazing. C# has always been a great language, except the .NET ecosystem (sans Mono) has always revolved around Windows only. Next up, when is VS for Linux?

I guess they will only support it remotely, at least in C++ context.

https://blogs.msdn.microsoft.com/vcblog/2016/06/07/visual-c-...

Re: Visual Studio for Mac

#253

Post by [deleted] »

Kipters wrote: post #50
thebeardedone wrote: post #38

Earlier quoted context omitted.

Hmm I have been googling for the last 15 minutes to find the difference between visual studio and visual studio code and cant seem to find a concrete answer. I thought yours was actually a hint at what it is aimed for but when you go to: http://code.visualstudio.com/ it actually says it supports c++,c#... I still dont get what the difference is.. Having only ever developed on linux I am actually slightly excited to u…

Visual Studio and Visual Studio for Mac are IDEs written in C# and they support C#, C++, VB.Net and many other languages. Visual Studio Code is a text editor built in TypeScript and based on Electron. It supports a broad range of languages, but it's an advanced text editor, not a full fledged IDE

[deleted]

Re: Visual Studio for Mac

#254

Post by mrweasel »

pjmlp wrote: post #249
mrweasel wrote: post #231

Earlier quoted context omitted.

It is my belief that Windows Forms will outlive WPF and/or XAML. Currently WPF is still the "modern" way to doing Windows applications, but at some point Microsoft will come up with some new scheme, and all the WPF developer will jump onto that. The developers that have still not abandoned WinForms will not jump shit when the next thing hits either. To keep the huge group of WinForms developers happy, Microsoft will…

Except that WinForms doesn't work on UWP applications other than via Project Centipede and is officially on support as it was communicated at BUILD 2014.

Of cause. My point is that so many business applications are Windows Forms, and will continue to be so for many years to come.

Removing WinForms will disenfranchise a large group of developers, that for one reason or another, it could just be stubbornness, won't switch. Microsoft will sooner kill of WPF than WinForms, to not lose those developers. At least that's my belief.

But we're talking for desktop applications only.

Re: Visual Studio for Mac

#255

Post by rayiner »

jmkni wrote: post #156
adamlett wrote: post #149

Earlier quoted context omitted.

Are you kidding me? How can you not see that this is nothing more than an arbitrary habit that you've grown comfortable with? Imagine the function keys had never existed to begin with. Don't you think we would have come up with a different way of stepping through code with a debugger? I understand that it's annoying to have to change your habits, but you're a developer for crying out loud: Your job is literally to ch…

Well...pretty much everything you do is an arbitrary habit that you've grown comfortable with . Sleeping in a bed is an arbitrary habit that you've grown comfortable with , why not sleep on the floor, or in the bath? The fact is that when developing and debugging, the function keys represent the most efficient way of stepping through code, and a part of this is to do with their physical presence on the keyboard. I kn…

> The fact is that when developing and debugging, the function keys represent the most efficient way of stepping through code, and a part of this is to do with their physical presence on the keyboard

Emacs users are blinking skeptically.

Re: Visual Studio for Mac

#256

Post by jonathanstrange »

This is very good in general. Now if they only could make a version for Linux and get rid of this whole "application barrier" thinking. Microsoft would probably be the only company right now who could fight the walled garden, developer lock-in approach that continues to destroy personal computing.

But if the past holds any indication for the future, then I'm not holding my breath for it. They'll probably just use the Mac version to introduce slight incompatibilities or make the Mac versions of existing products kind of slower and buggier than the Windows versions. :(

Re: Visual Studio for Mac

#257

Post by Pxtl »

FroshKiller wrote: post #214
72deluxe wrote: post #174

Earlier quoted context omitted.

Yes, and the ability to find call references (who is calling this function, where is it used) from the drop-down menu is really helpful. I miss the ease of access to that sort of functionality in Visual Studio.

Maybe I'm not using the same version of Visual Studio as you are, but Find All References is right there on the context menu when I right-click in VS.

Also shift+F12

Re: Visual Studio for Mac

#259

Post by givinguflac »

JonnieCache wrote: post #246
7Z7 wrote: post #223

Earlier quoted context omitted.

>..musicians,.. I'm running a Logic set up on my 2012 MBP, and I've never felt limited by its capabilities. I've been running Macs for music production for almost 20 years, and in my experience they have all at some point not had quite enough in the bag to let me do what I wanted of them. This is the first one (now fours years old) that has stayed ahead of my needs. I can run multiple copies of Massive, and rows of W…

The people who make film/game soundtracks need a LOT of ram, and fast disks, because they're using terabytes of samples in each project. Also massive has pretty low requirements. The main gripe musicians have with apple is the new OSX breaking their setup every year. The sandboxing in el capitan was particularly disastrous.

It sounds like you're basing this argument on hearsay and not personal experience (shocker.) I have various audio setups with different macs and interfaces and no OS update has broken anything with my setups since 10.6 era.

Re: Visual Studio for Mac

#260

Post by oceanswave »

hiram112 wrote: post #68
BoysenberryPi wrote: post #36

I'm glad to see more Microsoft dev tools on other platforms but don't lose sight of why this is happening. Microsoft is shifting their business to the cloud. They make their money off Azure and other services. In other words, they are making their money mainly off of developers now and its in their best interest to get on the good side of devs which is why they suddenly have a vested interest in open sourcing tools a…

What's the long-term business goal for Azure lock-in? If .Net runs as well on Linux as it does on Windows, then there really is no reason to use Azure over any other cloud provider like AWS where generic CentOS or Ubuntu boxes are no different than their Azure counterparts. Back when .Net was Windows only, they gave it away because the goal was the developers would pay a lot of money for MSDN, GUI apps on Windows, SQ…

> so I'm having trouble figuring why they'd bother giving away VS to Mac users without being forced to run on Azure in production.

It's the trickle up theory of modern development. Get folks using your languages and tools, and if you make it easy to integrate with your cloud services in those tools, that's where the revenue comes in.

It's probably an interesting number how much revenue is generated by various cloud providers for folks who just forgot to shut down their VM

Post reply on HN