Changes
Xamarin Studio for Windows was discontinued over a year ago. On Windows use Visual Studio, on Mac use Visual Studio for Mac. Visual Studio for Mac's support for VB.NET is limited. There is a uservoice suggestion for Visual Basic support which you can vote on. There is a uservoice suggestion for Visual Basic support which you can vote on. Visual Studio for Mac's support for VB.NET is limited. There is a uservoice suggestion for Visual Basic support which you can vote on. There is a uservoice suggestion for Visual Basic support which you can vote on.
- NuGet SDK resolver now used to find NuGet SDK packages
- Fixed Synchronous operation cancelled message on stopping debugging
- Fixed debugger hanging when debugging unit tests
- Fixed command line arguments not used with a new project
- Fixed hang when discovering unit tests
- Allow loading of SDK style projects without a main PropertyGroup
- Fixed TargetFramework not being updated in project
- Fixed .xaml.cs code completion in new Xamarin.Forms .NET Standard project
- Fixed default build action for new HTML file
- Fixed SDK version not being parsed from Sdk attribute
- Fixed null reference on opening .NET Core project with sdk version
- Fixed editor errors when .NET Standard assembly referenced in Xamarin.iOS project
More information on all the new features and changes in Visual Studio for Mac 7.6can be found in the release notes.
NuGet SDK resolver now used to find NuGet SDK packages
Visual Studio for Mac now has support for theNuGet SDK resolver. The NuGetSDK resolver will download and install SDKs for SDK styleprojects if these SDKs are missing.
The SDK resolution is done in the backgroundwhen the project is opened and there is currently no visual indication thatthis is happening.
The NuGet library assemblies are not available to the remote MSBuild host used byVisual Studio for Mac so the NuGet SDK resolver was previously failing to load. The NuGet SDKresolver supports a MSBUILD_NUGET_PATH environment variable which is now set byVisual Studio for Mac to point to the directory containing the NuGet assembliesthat are included with the IDE.
Bug Fixes
Fixed synchronous operation cancelled message on stopping debugging
Best Regards Limitxiao Gao MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not. You could also use a local account to access TFS.
This can be beneficial to other community members reading this thread.
Stopping the .NET Core debugger would sometimes result ina dialog being displayed indicating that the debugger operation failed.
Fixed debugger hanging when debugging unit tests
The .NET Core debugger would sometimes hang Visual Studio for Mac when debugging unit tests.The problem was that if the breakpoint was placed on an invalid line then the .NET Core debuggerwould send back the adjusted breakpoint location. Visual Studio for Mac would then send backan incorrect breakpoint line back to the .NET Core debugger, which again resulted in the debuggersending back a corrected line. This would repeat resulting in the IDE and debuggergetting stuck in a loop.
Fixed command line arguments not used with a new project
Creating a new .NET Core console project, editing the project runconfiguration to use extra command line arguments, or to not use theexternal console, then building and running the project would resultin the project run configuration not being used. No extraarguments would be passed to the console project, and the externalconsole would still be used. This could be fixed by closing andre-opening the solution.
The problem was that when the project is re-evaluated, after it iscreated, its run configurations are cleared. The solution’sstartup run configuration would still be usingthe original project run configuration that was no longer used.Changes made to the project run configuration then had no affect. Closing andre-opening the solution fixed this sincethe run configuration defined in the .csproj.user file is re-used when theproject is re-evaluated on reloading so both the solution run configuration andthe project run configuration refer to the same configuration. To fix this,on re-evaluating the project, if the solution’s run configurationrefers to a project run configuration that has been removed thenthe solution’s startup configuration is refreshed.
Note that there is a similar problem with multiple solution runconfigurations that can occur which is not addressed by this fix.
Fixed hang when discovering unit tests
Opening a solution containing a .NET Core test project would sometimesresult in the IDE hanging when discovering tests. On running
kill -QUIT pid
the IDE log would show a background thread and the UI thread bothawaiting test discovery to complete:Allow loading of SDK style projects without a main PropertyGroup
On loading an SDK style project that did not have a main PropertyGroupVisual Studio for Mac would show the error message“Error while trying to load project:Object reference not set to an instance of an object”.
A project may define MSBuild properties in a Directory.Build.props fileinstead of having this in the main project file. It is thenpossible for the main project file to have no main property group.
Directory.Build.props:
MainProject.csproj:
Visual Studio for Mac now handles the missing main PropertyGroup.
Fixed TargetFramework not being updated in project
Changing a .NET Core project’s target framework to a different version inProject Options, then re-opening Project Options and changing thetarget framework version back again, would result in the target frameworknot being updated in the project. The problem was the original target framework theproject had on opening was cached and the changing back to the sametarget framework version was being ignored resulting in the project file notbeing updated.
Fixed .xaml.cs code completion in new Xamarin.Forms .NET Standard project
Creating a new Xamarin.Forms .NET Standard project, thenmodifing the .xaml to add new named UI items, would result in nocode completion in the .xaml.cs file for these new itemsuntil the solution was closed and re-opened. The problem was that the.xaml and .xaml.cs fileswere being removed from the file information held in memorywhen the project was re-evaluated. On re-evaluation, afterthe NuGet restore is first run for the project, the old MSBuild items for the.xaml and .xaml.cs file have the wrong metadata, so they needto be removed, whilst new MSBuild items with the updated metadataneed to be added. The removal was done after adding the updated filesand, since they had the same filename, the new updated files were beingremoved. The removal is now done before adding the updated files toavoid the files being removed incorrectly.
Fixed default build action for new HTML file
Adding a new .html file to the wwwroot folder of an ASP.NET Coreproject would add the file as a None item instead of a Contentitem. This would result in the .html file not being used whenpublishing the project. When ‘dotnet publish’ was used thepublish directory would not contain the .html file.
ASP.NET Core projects have different build actions for files based on where theyare added. A .html file in the root directory would be a None item by default,whilst a .html file in the wwwroot directory would be a Content itemby default. To fix this the default build action for a file isdetermined by the file wildcard information available from the .NETCore SDK.
Fixed SDK version not being parsed from Sdk attribute
The Sdk attribute would have its forward slash / replaced with abackslash which meant Visual Studio for Mac was creating anSdkReference with the wrong name, for example:
Instead of having Microsoft.NET.Sdk.Razor as the name with theversion being separate.
Fixed null reference on opening .NET Core project with SDK version
Opening a SDK style project that used a Sdk attribute with a versionwould show an error message “Error while trying to load project:Object reference not set to an instance of an object”. The problemwas that an SdkResolver can return null from its Resolve method.These null results were added to a list and then an attempt was madeto log the result warnings on a null result.
Fixed editor errors when .NET Standard assembly referenced in Xamarin.iOS project
When a Xamarin.iOS project used an assembly that was compiledfor .NET Standard, such as the assembly in theSystem.Collections.Immutable NuGet package, the netstandard assemblywas not made available for code completion. This then resulted in the text editorshowing errors even though the project could be compiled succesfully.The errors displayed were similar to:
Now a check is made to determineif an assembly is referencing netstandard and if so the facade assemblies,which for Xamarin.iOS will include the netstandard.dll, are made availablefor code completion. Previously only a check was made for the project havingan assembly referencing System.Runtime before including the facade assemblies.
Active1 year, 4 months ago
I've tested creating ASP MVC 5 projects with the latest Visual Studio for Mac. So far some things don't seem to work 100%, like Razor Intellisense (I can live with that) and custom route settings.
I know that it isn't officially supported, but that doesn't mean that it doesn't work, otherwise the project template type wouldn't be there.
My question is:
Can I develop ASP MVC 5 web applications with Visual Studio Mac? Are there problems I will encounter, and if so, can I work around those? How do I deploy it?
I can't use ASP Core (yet) as I have the hosting I must use doesn't support it; only ASP.NET 4.6.
user5470600
1 Answer
No. Applications written targeting the .NET Framework, which the non-.NET Core MVC is based, are not supported. The .NET Framework was built for Windows only. It does not run natively on a Mac.
Daniel A. WhiteDaniel A. White154k4040 gold badges304304 silver badges383383 bronze badges
Visual Studio For Mac Os X
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.