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?
Active2 years, 3 months ago
Cannot debug.NET Core Applications on Visual Studio for Mac OSX 10.11.6 Reported by Pauline Cheung Mar 02 at 09:16 AM visual studio for mac debugger If I try to debug.net core applications, I get a popup saying Debugger Operation Failed, Synchronous Operation Cancelled. Visual Studio for Mac not only helps you build cross-platform applications for mobile devices and the cloud with Xamarin and.NET Core on macOS, it also offers all the productivity tools you need to write high-quality code. A.NET Core application can have a file called launchSettings.json, which describes how a project can be launched.It describes the command to run, whether the browser should be opened, which environment variables should be set, and so on. Get started by downloading the Community edition of Visual Studio for Mac for free to begin developing ASP.NET Core web apps, Unity games, and Android and iOS mobile apps, all in C#! Debugging already running Docker Linux.net core container with visual studio 2017 1 How to debug.net Core project with Docker support, using Visual Studio on a remote docker server. Visual Studio for Mac enables the creation of.NET Core solutions, providing the back-end services to your client solutions. Code, debug, and test these cloud services simultaneously with your client solutions for increased productivity.
This builds on version 12.5 and offers several feature tweaks. Looking further into the future, the company has confirmed that the next full update of the DAW will be to FL Studio 20. No doubt those of a superstitious nature will also be relieved. Fl studio beta. Slated for release in 2018, this will mark 20 years of the software - hence the decision to skip versions 13 to 19.
I am thinking of switching to Mac as Xamarin iOS development is much easier on Mac due to the restrictions imposed by iOS development. Unable to open pdf files in internet explorer. But I also write web API's and MVC pages and I wonder if there will be any problems in that aspect.
Rad studio virtual machine. One other thing that occurred to me is that, will extensions like ReSharper be available in VS for Mac too?
John L.John L.
64411 gold badge1010 silver badges2323 bronze badges
1 Answer
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.
Dan S.Dan S.
3,73622 gold badges99 silver badges2222 bronze badges
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Not the answer you're looking for? Browse other questions tagged asp.netvisual-studioxamarinasp.net-corevisual-studio-mac or ask your own question.
Is it possible to debug the .NET Core and ASP.NET Core source code in my projects?
Yes. These instructions are for windows (since we are talking about Visual Studio which only runs on windows. It is also important that we are talking about V2.0 (or later) .NET Core (e.g. what you get from https://www.microsoft.com/net/core#windowscmd)
These steps will allow Visual Studio to find the *.PDB files that are needed for the .NET Core and ASP.NET Core libraries. However you need more than just the *.PDB files you also need the source code itself. Going forward we intend for all our libraries to have 'SourceLink' information so that you can fetch the source directly from GitHub. When this is present, VS will simply fetch the source from GitHub and the experience is beautiful. I have tested this on Visual Studio 15.3 (the latest released version).
This 'it just works' experience (when you step into or set breakpoints on framework code VS should simply fetch the correct source code), should work for V2.0 ASP.NET DLLs (that is Microsoft.aspnet*.dll). Sadly the CoreFX, and CoreClr dlls (Typically System.* dlls), will not be fixed until the V2.01 release (In a few weeks) and thus you need to fetch source code yourself using the instructions below.
Getting source from GitHub
Ultimately you should not need to do this, all our DLLs will have SourceLink information and VS will simply fetch it from GitHub for you. However some of our libraries currently do not have SourceLink information. We will fix this but the experience in that case is VS will ask you where to fetch the file from. You can work around this by fetching the source code from GitHub yourself and pointing VS at it.
![]()
lives in https://github.com/aspnet/Mvc
Once you know the repository, you can fetch the repository and set it to the 2.0.0 version of the source like this.
At this point you can answer the VS dialog prompting you for the source file path. Once you set it for one source file it will work for any other source file in the same directory structure.
You can also set up where VS searches without having to wait to be prompted by right clicking on the solution -> Properties -> Debug Source Files and then add your directory to the 'Directories Containing Source Code'. Once you set up these paths, VS should simply find your source code.
Usb Debugging Is Disabled
Finally there is an option in (Tools -> Options -> Debugging -> General -> Require Source Files to match Exactly) which is set by default. If you have problems getting VS to find your source, you can try unselecting that checkbox to see if your version is wrong and the source checksums don't match.
Mac Visual Studio For Mac Debugging Is Disabled .net CoreASP.NET 2.0 SourceLink (VS fetches from GitHub directly) should be working![]()
The V2.0 ASP.NET DLLs (aspnet.dll) have the needed SourceLink information, they should just work. the instructions above for fetching source code for these DLLs. Please comment below if this is not the case.
Note that we did UPDATE the ASP.NET PDBs so they have sourceLink, which means that if you tried to step into ASP.NET dlls before, you may have already cached an old version of the PDBs and if so, Visual Studio will not try to refetch it. You can force the refetch by exiting Visual Studio deleting the %TEMP%SymbolCache directory and then retrying. In addition once Visual Studio has attempted to fetch a particular source file it will not attempt doing it again. You can clear that history by right clicking on the solution -> Properties -> Debug Source Files and removing all names from the 'Do not look for these source files' textbox.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |