![]() I find the naming 'Visual Studio for Mac' pretty deceptive, since apparently it is not anything like the win32 VS environment, but instead based on Xamarin Studio. Even the tagline is deceptive: 'The IDE you love, now on the Mac'. I would guess this won't let you build/debug win32 or winforms or wpf applications, or install any.vsix extensions from the visual studio marketplace (of which there are lots of useful ones, such as this one to manage translations - ) - correct me if I'm wrong, but if I can't install my.vsix extensions, this is not 'the IDE you love, now on the Mac'. Hi, Rajen Kishna here, Product Manager on Visual Studio for Mac. Our goal with Visual Studio for Mac is to create a native IDE for Mac users with workloads that make sense on macOS. How to open a usb on a mac. That means 'desktop app' development will target macOS and Visual Studio (on Windows) can be used to target Windows. The core of the IDE definitely has a heritage in Xamarin Studio, but this release has brought in so much more with.NET Core/ASP.NET Core development for web apps/services, Unity support for game development and cloud integration with directly publishing your web apps/services and previews of Docker and Azure Functions coming very soon. I don't know if it was a coincidence but I was able to install Xamarin Studio, build the project, got the XamlCTask error, removed it from the project file, built it again getting the XamlCTask missing error, put it back and the build started working. Can't install Visual Studio 2017. I have a system MacOS Sierra - 2 HDD - 1 for System and the other for Home folder /Volumes/MAC STORAGE/ (it is a common drive with a common file system for Mac / Linux / Windows). Quickbooks multi user setup. Extensions is definitely another area we're looking to align more over time. Currently, there is an extensions framework, but you're right that it's different from the one used on Windows. Definitely keep the feedback coming, we're listening and looking to act and prioritize accordingly! 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. Code can be well designed from an architectural perspective and still be slow in areas. I imagine it's due to the minimal feature set (which MS defined). Stuff constantly happening in the background when you click or type something, bottlenecks become more apparent with really large projects and they just haven't dedicated time to improving that, etc. I realize that architecture can't be separated from functionality, but I think the parent was focused on modularity and the ability to reuse various components. > Definitely keep the feedback coming > Our goal with Visual Studio for Mac is to create a native IDE for Mac users.That means 'desktop app' development will target macOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |