-
Net Core And Visual Studio For Mac
I've been using Visual Studio Mac for a little while and have just updated it to the released version. I've also downloaded and installed.NET Core 2.0 Preview 1. From a shell prompt I can generate a new Web API project: dotnet2 davec$ dotnet -version 2.0.0-preview1-005977 dotnet2 davec$ dotnet new webapi The template 'ASP.NET Core Web API' was created successfully. This template contains technologies from parties other than Microsoft, see for details. Processing post-creation actions.
- Jan 15, 2018 - NET Core is that you can run it on multiple platforms and architectures. Additionally, in order to run the app on a Mac, you will need access to a Mac that is running. We'll create the applications using Visual Studio 2017.
- Without Visual Studio. Unlike the ASP.NET of the past, you don’t need Visual Studio to build and debug ASP.NET Core applications! If you’re on Mac or Linux, or simply want a lightweight development option, you can use Visual Studio Code, Sublime, Atom, or your favorite text editor to write ASP.NET Core applications.
- I created a new Asp Net Core application. I would like to publish it to linux and mac. I am doing this development on a Mac using Visual Studio 2017 for Mac Professional.
This tutorial shows how to develop a simple web service using Visual Studio for Mac. We’ll go through how to create and debug an ASP.NET Core web service using C#.
Running 'dotnet restore' on dotnet2/dotnet2.csproj. Restore succeeded. I can build and run that project from the shell.
But when I open it in Visual Studio for Mac, the IDE tries and fails to restore: Errors in dotnet2/dotnet2.csproj Unable to resolve 'Microsoft.NETCore.App (= 2.0.0)' for '.NETCoreApp,Version=v2.0'. Unable to resolve 'Microsoft.NETCore.App (= 2.0.0)' for '.NETCoreApp,Version=v2.0 (win)'.
Unable to resolve 'Microsoft.NETCore.App (= 2.0.0)' for '.NETCoreApp,Version=v2.0 (win-x64)'. Unable to resolve 'Microsoft.NETCore.App (= 2.0.0)' for '.NETCoreApp,Version=v2.0 (win-x86)'.
NuGet Config files used: /.config/NuGet/NuGet.Config Feeds used: Restore failed for 'Microsoft.NETCore.App (= 2.0.0)'. Restore failed.
Now that there is Visual Studio for Mac, is it possible to do everything you do on Windows also on Mac? I've read that I should be using ASP.NET Core instead of the full ASP.NET framework if I want to use a Mac. What kind of restrictions does this cause?
For example, can I migrate my web application that I wrote on Windows without a change? I am thinking of switching to Mac as Xamarin iOS development is much easier on Mac due to the restrictions imposed by iOS development. But I also write web API's and MVC pages and I wonder if there will be any problems in that aspect. One other thing that occurred to me is that, will extensions like ReSharper be available in VS for Mac too? As was mentioned in one of the comments you're not able to use the full.NET Framework on Mac so you have some limitations as to the projects you can actually work on. The mobile templates in VS4Mac do not include UWP so if you're doing File - New you won't be able to work on UWP. If you are bringing over a project that includes projects like UWP that aren't exactly supported on Mac you should still be able to work on the code, you just cannot build or deploy.
There is some truth to VS4Mac being a rebranded Xamarin Studio. However, the changes they've introduced over the last year do back up what Miguel said at Build that they took actual bits from VS and replaced the XS components with the actual VS bits like the Debugger. You have to remember that VS4Mac is a Native Mac application and is meant to give you the feeling of working on Mac not PC (as it should). Whether or not VS4Mac is for you is a question that only you can answer.
That answer will vary from developer to developer, and frankly from task to task. It's worth remembering though that VS4Mac is a v1 as far as an integration with the VS code base. I say that to remind you that not all of the features that we all want are going to be there right now. As for support for tools like ReSharper, Microsoft cannot be realistically expected to determine what tools are going to be supported. That really is in the hands of JetBrains and when they decide to get the tooling out to the community. As for the Xamarin Live Player.
Remember it is a preview. Results are bound to vary from developer to developer.
That said my testing to date has shown it's ok for very basic projects, but the second you put a framework behind it and use any sort of reflection it will not work at all and I'm not sure that will change.