Develop apps and games for iOS, Android,
and web using .NET
Use the powerful coding, refactoring, and debugging features in Visual Studio for Mac to enhance your productivity. Some customers using Visual Studio for Mac today. Visual Studio Community for Mac. Free, fully-featured IDE for students, open-source and individual developers.
Code in C#, F#, Razor, HTML5, CSS, JavaScript, TypeScript, XAML, and XML
With the power of Roslyn, Visual Studio for Mac brings IntelliSense to your fingertips. IntelliSense describes APIs as you type and uses auto-completion to increase the speed and accuracy of how you write code.
- I have been using the Visual Studio Debugger on my PC and I really like it. NowI want to switch to a MAC and I would like to know how different the debugger for MAC OS X is from the Visual Studio.
- Visual Studio Code is the first code editor, and first cross-platform development tool - supporting OSX, Linux, and Windows - in the Visual Studio family. At its heart, Visual Studio Code features a powerful, fast code editor great for day-to-day use.
Quick Info tool tips let you inspect API definitions, squiggly lines in the editor highlight issues, in real time as you type.
Use the Visual Studio debugger to quickly find and fix bugs across languages.
The Visual Studio for Mac debugger lets you step inside your code by setting Breakpoints, Step Over statements, Step Into and Out of functions, and inspect the current state of the code stack through powerful visualizations.
As your project grows, chances are, you’ll find yourself restructuring and refactoring code that you or someone else wrote earlier. That’s a whole lot easier when Visual Studio for Mac takes care of the heavy lifting for you.
The Visual Studio for Mac editor supports powerful built-in refactoring options such as Extract Method and Rename, accessible via the Quick Actions menu.
Manage your code in Git or SVN repos hosted by any provider, including GitHub and Azure DevOps. Review diffs, stage files, and make commits from inside Visual Studio for Mac.
Choose the development environment that is right for you. With Visual Studio on both macOS and Windows, you can share your C# and F# projects seamlessly with your team using either OS.
| FEATURES | Visual Studio 2019 for Mac | Visual Studio 2019 |
|---|---|---|
| Web and cloud development using C# | ||
| ASP.NET Core and .NET Core | ||
| Publish to Azure | ||
| Azure Functions | ||
| Azure Connected Services | ||
| Docker container tools | ||
| Desktop development | ||
| WPF and Windows Forms | ||
| UWP | ||
| Mac Apps using Xamarin and C# | ||
| Console apps with C# | ||
| Desktop apps using C++ | ||
| Mobile and gaming | ||
| Mobile development with .NET using Xamarin and C# | ||
| Game development using Unity and C# | ||
| Mobile and game development using C++ | ||
| Other workloads and tools | ||
| Java | ||
| Python | ||
| SQL Server data tools | ||
| Node.js | ||
| Unit testing | ||
| Version control with Git | ||
Create cross-platform apps targeting Android and iOS using Xamarin
Build, manage, and deploy cloud apps that scale to Azure
Create and debug cross platform games and 3D real time applications with Unity
Customers using Xamarin with Visual Studio for Mac
Launch a professional environment tailored to the Mac, free for most non-enterprise users
Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Mar 18, 2017
When trying to debug a MVC Web project in VS 2017 Mac I get the error message: Unable to attach to CoreCLR. dotnet
dotnet --info
|
commented Mar 20, 2017
Got the same issue (also on Sierrs 10.12.4 beta) |
added the area-Diagnostics label Mar 21, 2017
commented Mar 21, 2017
This will be fixed in the next 1.0 and 1.1 service releases and has been fixed in the master branch. |
commented Mar 28, 2017
When will it be available ? Thanks |
commented Mar 28, 2017 • edited
edited
Sierra 10.12.4 is now being pushed as an update by Apple. I installed the update this morning and now I can no longer debug in VS Code ('Unable to attach to CoreCLR.'). I believe this is the same issue reported above. I installed the latest .NET Core SDK ( |
commented Mar 28, 2017
Here is a work around that worked for Gregg Miskelly:
|
commented Mar 28, 2017
Confirmed workaround works. Thanks for the info. When the real fix is released, will I need to 'reverse' the workaround, or will installing the new software get me back to consistency? |
commented Mar 29, 2017
Is there a workaround for Visual Studio Mac ? |
commented Mar 29, 2017
@gregg-miskelly Is there a workaround for VS for Mac? |
commented Mar 29, 2017
I don't have precise steps, but you can work around this by downloading https://vsdebugger.azureedge.net/coreclr-debug-1-9-0/coreclr-debug-osx.10.11-x64.zip, and replacing the version of vsdbg that VS for Mac is using with that version. @DavidKarlas do you have better instructions? |
commented Mar 29, 2017
This fixed it for me, in Visual Studio for Mac:
|
commented Mar 29, 2017
@suqram You just saved my day and night! Thx. |
commented Mar 29, 2017
@suqram it worked well! Thanks |
commented Mar 29, 2017
fix it for me! |
commented Mar 30, 2017
@suqram Excellent! |
commented Mar 30, 2017
Excellent, copying the libdbgshim file as instructed by @suqram did the trick. |
commented Mar 31, 2017
@suqram Excellent! |
commented Mar 31, 2017
Works for me too! thanks! |
commented Mar 31, 2017
@mikem8361 what does this mean? |
commented Mar 31, 2017
A nuget file is a zip file. Rename to .zip and run unzip on it. |
commented Apr 1, 2017
@suqram Work for me as well - thank you. |
commented Apr 1, 2017
@suqram Thanks so much! It works! |
commented Apr 1, 2017
Is this issue fixed in production now, or is it still in workaround? I noticed a new C# Extension and installed it yesterday. Does that contain the fix? |
commented Apr 3, 2017
@robbpriestley Sure seems like it. This is in the changelog for the extension in vs code: (and it's working) |
commented Apr 3, 2017 • edited
edited
Visual Studio Standalone Debugger
I did precisely what @suqram suggested, but now I get a popup when I try to run my application:
I don't get the 'Unable to attach to CoreCLR' message in my Application Output window anymore, so that's fixed. (and to clarify: when I run 'dotnet' or 'dotnet --info' , my results are identical to those from @AAimson) |
commented Apr 3, 2017
@joristt if you have the 1.8.1 extension installed and you are still running into an issue, your issue isn't related to this issue. Please open a new issue, this issue is long enough :). |
commented Apr 3, 2017
I was working on aspnet core when this issue started, and with VS preview it used to start a new Browser with a new debug session. Am i looking for the wrong setting now? |
commented Apr 3, 2017
@gregg-miskelly Yeah you're right, sorry :). You said
and I interpreted that as: replace only the vsdbg Unix executable. Tried copying everything from that zip to the VS Adapter directory 1 minute after commenting here and that fixed the problem. |
commented Apr 3, 2017
@robvdveer by 'VS Preview' you mean 'VS For Mac Preview' correct? If so - VS For Mac hasn't shipped an update vsdbg package containing the fix yet (at least to my knowledge), so you are very likely at the right place. There are two work arounds posted above, but I will give you the latest version of it --
|
commented Apr 3, 2017
Thanks @gregg-miskelly for such a quick response! |
commented Apr 4, 2017
@gregg-miskelly well played. Thanks |
Visual Studio For Mac Debugger Not Working
commented Apr 5, 2017
X Code
@gregg-miskelly saved the day!!!! |
commented Nov 23, 2017
@gregg-miskelly this will work on the visual studio preview the debug gives an execution error |