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. 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.

Visual studio for mac mono