supercouture.blogg.se - Will visual studio for mac work with windows version

#Will visual studio for mac work with windows version for free
#Will visual studio for mac work with windows version how to
#Will visual studio for mac work with windows version install
#Will visual studio for mac work with windows version upgrade
#Will visual studio for mac work with windows version portable

In other words, the marketing team should've probably thought a little longer about how to brand this. NET 3.5 and 4.5 or something similar, I suggest installing very old Mono or even better do it on Windows with. So warning is valid and intended, hence closing this as not a bug. Mono by design only supports latest versions of. A few days later, it was closed with this response from a Microsoft employee: Thank you for your feedback! We have determined that this issue is not a bug.

Getting official helpĪfter awhile, I opened a ticket in the developer community forums with all the details above, including what I'd tried. Afterwards, I tried different combinations of Mono release (Project / Active Runtime) to. I downloaded the last release for 2.x, 3.x, etc and installed them all.

#Will visual studio for mac work with windows version install

NET Framework was out when it was released, and I needed to install them? Sure, just a guess, but it seemed logical. Okay, so maybe each Mono version supports whatever version of the. NET Runtimes tab in preferences, all I had was Mono 5. I even tried committing the project to git before this happened so I could restore it, but it showed no changes, so whatever got borked must've been in some hidden file. Once you start doing anything remotely interesting though.Įven after restarting (and reinstalling) VS4Mac, that project appeared to be permanently hosed, and I had to create a new one. it works okay as long as you stay in the lines. This is fairly typical of my experience in VS4Mac. NET alternated between showing an error in the console when I tried to run my tiny app: WARNING: The runtime version supported by this application is unavailable.Īnd sometimes the IDE blew up completely by underlining everything and claiming it could no longer find System.Object or System.Int32. However, switching to an earlier version of. You can right-click a project and choose options to find a dropdown under the "Build" settings, which is very similar to Visual Studio on Windows. NET, which seemed as if it were going to be trivial. So I spent a few evenings trying to target a C# project for an earlier version of. NET values backwards compatibility, but it's not unheard of. That'd actually be pretty unusual, since. I thought I'd setup a local project in Visual Studio for Mac and then turn the clock back a bit to see if maybe how the code was implemented changed between.

#Will visual studio for mac work with windows version portable

Netstandard/.NET Core framework to develop your App so that libraries are more portable (following the blog article above should do).I saw an implementation of some C# code this week that looked like it should work, but wasn't producing the expected results for me using. Hope that helps others whom didn't know what to do and where to start.ĭon't follow tutorials dating from before 2017. But that's also a good way to save your project as well, so that if you screw up (like it happened to me numerous time) you roll back. Here is an article on how to get started from Mac:Ĭons: Always having to commit the code for it's use within UWP. This is easier IF YOU THINK ABOUT CHOOSING THE CORRECT LIBRARIES (working on all platforms, hence check my last advice).įrom VS Mac, compile using macOS as a host! It's the easiest way to develop fastly, and correct your bugs. UWP apps compile fastly and like a charm, so better is to get rid of errors within macOS, IOS, Android, and then go and adapt to UWP. It took me more time debugging than coding within VS Windows.Īfter developing chunk of your app within Visual Studio MAC, the best is to get the code on the windows machine and arrange it to work in UWP. The best being to develop from Mac as you will have FAR LESS ERRORS AND BUGS than in VS for Windows.Ĭorrecting mistakes is really daunting and the best is really to develop from Mac to mitigate the damages, but it won't be hurdles free as well!

What environment to favor while developing, most importantly when you are a C# and Xamarin noob like me?.

Not to mention that you will have to install Ubuntu as another VM in order to setup a. So, prefer something older, but up-gradable (a cheap Macbook pro with 16go of RAM would do). 4go gets you a laggy environment! Really frustrating. Working on 8go of ram computer when you must give 4go of RAM to your VM isn't quite great.

#Will visual studio for mac work with windows version upgrade

An old one even since YOU CAN'T upgrade the ram. It worked like a charm.Ĭons: Buying a brand new IMac while a Macbook pro would have been better.

#Will visual studio for mac work with windows version for free

Buying an Imac, thinking that I could also develop UWP projects within itĪfter realizing that I couldn't, I bought a cheap Windows 7 pro License on ebay (around 5$), and installed it on VirtualBox.įrom there, I upgraded to Windows 10 for free and installed everything.

For those whom imperatively needs to develop their app on all platforms, here is what I did, and the pros and cons: