Visual Studio For Mac 2017 Stability

• Visual Studio
• Visual Studio For Mac Tutorial
• Visual Studio 2017 Download
• Visual Studio For Mac Download

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 upNew issue

Visual Studio for Mac enables web and cloud developers on macOS to build applications using.NET Core. This video shows how to get started building web applications in Visual Studio for Mac. Developers can use Visual Studio 2017 for Mac to create and tune iOS, macOS, and Android apps, and also create web applications thanks to the software's support for ASP.NET Core.

Have 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 30, 2017

Is there a timeline on adding this support? Or any pointers to how I could help achieve it?

commented Mar 31, 2017

No definitive timeline, but I want to get this done for the 2.4 release. I don't usually bother with releasing stuff for unfinished products (VS for Mac/MD 7), but it might be easy to support it since it doesn't appear to be many api breakages between 6 and 7. If you'd like to help out, I can really use it. All the source is here. They need to be loaded up in the newer versions of VS and XS with the appropriate extension/addin authoring plugins installed, and tested. There are some other outstanding items regarding the addins that need looking at too: #582 - conditionally support MonoMac, or possibly remove it altogether since Xamarin.Mac is now open source. #701 - conditionally support Xamarin.Mac, so it only loads the appropriate stuff when it is installed. #601 - add templates for xaml-based form and dialog to XS. #579 - Fix crashing with VS preview window, which has to do with how the appdomain is setup. I have a local branch with an attempt at fixing it, but I have yet to figure out why it does not kill the appdomain properly when reloading the preview. Cheers! Curtis.

commented May 1, 2017•

edited

I have made it work with Visual Studio for Mac. I created a new directory in the Addins section for visual studio mac it is based off the existing xamarin studio version. created pull request at #793 I have not actually run the extension just had it compile so may need more work

commented May 1, 2017

I couldn't get the add-in to work with VS2017. I'm not really into VS extension development and only tried to get the references to resolve somehow, but it fails with some weird file not found HRESULT upon creating a new Eto project. Any official support on this?

commented May 2, 2017

Hey I created a .mpack file that you can use if you want. In Visual Studio for Mac click the Visual Studio menu then click Extensions then click the Install from file button and select the .mpack file to install the extension. This only works on VS on Mac not for windows version if that is what you where trying to do.

commented May 2, 2017•

edited

Thanks, but I required it for the classic Visual Studio 2017 desktop application on Windows. Actually, I could build the .vsix for it now (using assemblies in my VSSDK directory rather than NuGet packages, don't really understand what's the difference but eh), but it can't really create projects, not being able to find the Eto.Forms NuGet packages somehow (including the available 2.3.0 one instead of the 2.4.0-alpha package when changing it to that). But at least the templates and designer work, the latter quite slow but good enough.

commented Aug 24, 2017

Please write a short update, if anything happens here. Would be nice :-)

commented Sep 2, 2017•

edited

Built using VS 2017 15.3 in Windows. No changes made in code. Just some reference correction from nuget, assembly and target framework to .Net 4.6 Finally every thing working as expected.

commented Dec 12, 2017

I just downloaded and installed extension in Visual studio 2017 v 1.5.4.5 and it does not work. Generating new Eto application throws error: Any thoughts ? Dec 07, 2007  Hi, I've recently purchased a macbook and was wondering if there's a visual studio equivalent used for.net development on mac os x? I've recently been using bootcamp so i can run both os x and windows xp, but am wanting to eliminate the need for two operating systems if i can. Visual studio equivalent for mac. Popular Alternatives to Microsoft Visual Studio for Mac. Explore 25+ Mac apps like Microsoft Visual Studio, all suggested and ranked by the AlternativeTo user community. What is a good free alternative to the MS Visual Studio? Update Cancel. Ad by JetBrains. Rider: fast, powerful, cross-platform.NET IDE by JetBrains. What is the techstack of MS Visual Studio for Mac? Is Visual Studio Ultimate worth $13,299? What is a good web hosting service for Visual Studio? Ask New Question. Alternatives to Microsoft Visual Studio for Windows, Linux, Mac, BSD, Web and more. Filter by license to discover only free or Open Source alternatives. This list contains a total of 25+ apps similar to Microsoft Visual Studio. Show transcribed image text Using Visual Studio or equivalent IDE for Mac, create a website made of one HTML file and XML file named 'books.xml' file. Here we assume the HTML file's name is 'index.htm' for convenience. You can use any file name you like for this HTML file.

commented Dec 12, 2017

Have you added eto myget to nuget repositories?

commented Feb 1, 2018

VS for Mac and MonoDevelop are now supported with #974. A new version of the addin will be published along with the 2.4 release, or you can build it manually.

commented Feb 4, 2018•

edited

I'm trying to use the new addin with VS for Mac but I'm a bit confused: I can build Eto dll(s) from Visual Studio for Mac EtosrcEto.sln, and it works (updated the develop branch to commit ed2073c (1st Feb 2018, 20:19) I can build the add-in from Etobuildbuild-addin.sh, a Eto.Addin.XamarinStudio_2.3.0.6.mpack gets created but the overall build fails. Only the Eto.Forms.Templates.2.4.0-alpha.nupkg gets created in the EtoartifactsnugetRelease. However the newly created addin installs successfully and I can create a new Eto project, but when I build it nuget complains with the message 'Restore failed for 'Eto.Platform.Mac64 (>= 2.4.0-alpha)'. Should I expect to have it in EtoartifactsnugetRelease? If instead of using nuget I directly add to my solution EtosrcEto.csproj and EtosrcEto.MacEto.Mac.csproj (or EtosrcEto.MacEto.Mac64.csproj) and reference them where needed I can compile fine but when I run my application it crashes with the exception 'Platform type Eto.MacPlatform, Eto.Mac64 was loaded but is not valid in the current context. e.g. Mac platforms require to be in an .app bundle to run.' What am I doing wrong? Thanks

commented Feb 4, 2018

Hey @msasso69, to build the nuget packages you need to use the ./build.sh (on mac), and build.cmd (on windows). I usually do this via a share to a windows VM so they are both run on the same copy of the source files. This ensures the XamMac and Wpf nupkg files are created, which are mandatory for the addin templates. You need the nuget packages to run the Mac/Mac64 platform as it sets up the proper .app bundle build, and tells VS on Mac to run the .app bundle instead of the .exe directly. This stuff is all in build/MacTemplate.

commented Feb 4, 2018

Thanks Curtis, running ./build.sh I can now successfully build all the nuget packages and the initial Eto project created by the addin runs fine :) However I'm not yet able to debug the Eto code, if I reference the Eto projects instead of using the nuget packages I still get the exception: 'Platform type Eto.MacPlatform, Eto.Mac64 was loaded but is not valid in the current context. e.g. Mac platforms require to be in an .app bundle to run.'. The only difference that I found from the Eto test application (that I thought relevant) is a: but even adding it nothing changes :( I think I did not understand what you meant when you told me that everything is in the build/MacTemplate. How do I use it? Thanks for your patience ;)

commented Feb 5, 2018

@msasso69, if you want to use Eto.Mac.csproj or Eto.Mac64.csproj directly without using their nuget packages, you will have to add <import Project='path/to/MacTemplate.targets' /> to your csproj. This is what <UseMacTemplate>True</UseMacTemplate> does for Eto's test projects via the Directory.Build.targets file. When using the nuget packages, this file is automatically imported into your project. Other options include: Use the MyGet nuget packages Build the nuget packages and use them Create a 'XamMac Classic' project (difficult as isn't not readily available in VS for Mac, hence the new way this is done) Use XamMac2 project Hope this helps! Curtis.

commented Feb 6, 2018

Fixed with #986

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Last year at Build, we launched Visual Studio for Mac, our native macOS IDE for developers building cloud, web, and mobile applications using .NET. Updates have been rolling out at a steady pace ever since, and we’re excited to announce the release of Visual Studio for Mac version 7.5. We have also continued to bring more Visual Studio 2017 code to the Mac.

Our mission has always been to delight developers, and we have something for everyone in this release. You can get started by downloading the new release or updating your existing install to the latest build in the Stable channel.

Here are some of the features we’re most excited to share with you:

• ASP.NET Core developers now have full Razor editor support. We’ve also introduced JavaScript and TypeScript support.
• For iOS developers, we added WiFi debugging support for iOS and tvOS applications. We also improved the iOS provisioning system.
• Android developers will enjoy the new Android SDK manager built right into the IDE, as well as a device manager to keep track of all your devices and emulators
• Xamarin.Forms developers will enjoy an improved XAML editing experience
• Cloud developers have support for Azure Functions development using .NET Core.
• We support .NET Core 2.1 RC and C# 7.2.
• Code-styling rules can be configured per-project using .editorconfig files.
• A preview of Team Foundation Version Control support for Team Foundation Server and Visual Studio Team Services is now available.

We’re also shipping improvements to performance and stability, accessibility, and multi-language support, along with fixes for a number of bugs reported by our vibrant developer community. You can find the full list of changes in our release notes.

ASP.NET Core development with Razor, JavaScript, and TypeScript Editor Support

We partnered with the Roslyn and Visual Studio JavaScript tooling teams to reuse Razor, JavaScript, and TypeScript editor source code, bringing the editing experiences you know and love from Visual Studio 2017 to the Mac.

Official Razor support includes IntelliSense and syntax highlighting in .cshtml files

Our JavaScript editor has been rewritten to provide the core editor experience you expect, including IntelliSense, enhanced colorization, and brace completion. We’ve also added TypeScript editing support, which shares the same IntelliSense and colorization as our JavaScript experience.

Use .editorconfig files to Set Code Style Rules in Projects

One of my favorite features is finally here: .editorconfig

Visual Studio for Mac will now format your code following the conventions specified in the .editorconfig file. This will allow you to set your coding style, preferences, and warnings for your project; making it simpler for code that you contribute to other projects to follow the practices of those projects.

Xamarin.Forms Development

We now ship Xamarin.Forms templates that take advantage of .NET Standard Libraries.

Working with XAML just got better, too, with IntelliSense improvements providing better support for self-closing elements and more completions.

Android Development with Xamarin

On the Android side of the house, we added an integrated Android Device Manager dialog, eliminating the need to rely upon 3^rd-party tools for device and emulator management. You can find this under Tools > Device Manager.

iOS Development with Xamarin

iOS fans will enjoy a streamlined Entitlements editor experience, making it a breeze to add capabilities and services to your iOS apps.

Simply open the Entitlements.plist file and jump right in! Not only that, our new Automatic Signing experience makes deploying your application to devices very simple. In the Signing section of the Info.plist editor, you’ll find using Automatic Signing makes the burdens of manually tracking your entitlements and provisioning devices things of the past.

Building Serverless solutions with Azure Functions

Our new Azure Functions templates now support the Azure Functions .NET Core SDK, empowering you to build, debug, and test Azure Functions locally. In addition, item templates provide guidance for building functions using the most common triggers, enabling you to get up and running with new functions in minutes.

After creating a new Azure Functions project, right-click and select Add > Add Function, then choose your favorite function from the template dialog.Check out our documentation for a walkthrough to create your first Function in Azure.

.NET Core 2.1 RC and C# 7.2

Visual Studio for Mac version 7.5 now supports .NET Core 2.1 RC. Major improvements include faster build performance, better compatibility with .NET Framework, and closing gaps in both ASP.NET Core and EF Core. You can read more about the .NET Core 2.1 RC release in the announcement blog post. Support for the newest C# release, version 7.2, is also available today.

Working with your source with Team Foundation Version Control

One of our most popular feature requests has been to add support for Team Foundation Version Control (TFVC) to access source saved in Team Foundation Server or Visual Studio Team Services. We heard you loud and clear! Today, we’re previewing a new extension to do just that.

Visual Studio

To install the extension, navigate to Visual Studio > Extensions… in the Visual Studio for Mac menu and search the gallery for “team foundation”. We support Get, Commit (with associated work items), version history, and more.

Visual Studio For Mac Tutorial

Feedback

We hope you’ll find Visual Studio for Mac version 7.5 as delightful as we do. Let us know what you think! Your feedback helps us improve our products and better understand your needs as a developer.

Please let us know about issues via Help > Report a Problem. You’ll be able to track your issues and receive updates in the Visual Studio Developer Community.

You can also provide product suggestions via the Help > Provide a Suggestion menu and vote on suggestions at the Visual Studio for Mac UserVoice site.

Visual Studio 2017 Download

Miguel de Icaza

Visual Studio For Mac Download

Miguel de Icaza, Distinguished Engineer, Mobile Developer Tools @migueldeicaza Miguel is a Distinguished Engineer at Microsoft, focused on the mobile platform and creating delightful developer tools. With Nat Friedman, he co-founded both Xamarin in 2011 and Ximian in 1999. Before that, Miguel co-founded the GNOME project in 1997 and has directed the Mono project since its creation in 2001, including multiple Mono releases at Novell. Miguel has received the Free Software Foundation 1999 Free Software Award, the MIT Technology Review Innovator of the Year Award in 1999, and was named one of Time Magazine’s 100 innovators for the new century in September 2000.