Re:Visual Studio for Mac
by 0x0 on Wednesday May 10, 2017 @01:09PM
(#14309789)
I am sure it is a nice product, but the name is causing confusion. In the last few months I have witnessed misunderstandings between clients and consultants who think they agree to deliver a project as a "visual studio solution/project", and only when deliverables start being passed around do they realize that the original win32 visual studio is not the same as the other visual studio offerings, and that you cannot just expect the other offerings to produce the win32 visualstudio .sln and .csproj solution project files or anything that builds with msbuild.exe out of the box etc.
[ Parent
| on HN ]
Re:Visual Studio for Mac
by AsyncAwait on Wednesday May 10, 2017 @02:07PM
(#14310245)
I get how this might happen, but that sounds like there are some fundamental problems at the place where you saw that, I mean if you think that "Windows Phone" for example is the same as "Windows" on your laptop then that I don't think it is Microsoft's fault.
But what if "Windows Phone" was marketed as "The Operating System And Desktop Environment you love, now on your phone"? :)
Re:Visual Studio for Mac
by grovegames on Wednesday May 10, 2017 @03:39PM
(#14310974)
I think that's pretty consistent with the One Windows marketing. Personally, I'd rather have a tool that works with some of the features I want, rather than none of the features I want, because they're taking 5 years to get to feature parity. But that's just me.
How is that even possible? You'd want to specify version numbers for a solution file even if you were keeping things purely in the Windows realm.
Easy. "We are expecting the most recent available version of Visual Studio (by the time the contract is signed)".
Step one level up above the trenches and the people you meet haven't had the time (or even skills) necessary to study the details to determine the fact that "Visual Studio for Mac" is, in fact, not the latest version of Visual Studio in the slightest. And why should they. Delivering a visual studio solution should be as unambiguous as delivering an excel sheet.