Обзор Visual Studio For Mac

Return to site

Обзор Visual Studio For Mac

Introducing Apple silicon and a new visual appearance. Porting Guidance. Build a native Mac app from the same code base as your iPad app. In this video I am teaching How can you use your Macbook to develop Csharp or Asp.net core applications using Visual Studio IDE. Copyright© are reserved unde. The Visual Studio for Mac editor supports powerful built-in refactoring options such as Extract Method and Rename, accessible via the Quick Actions menu. Integrated Source Control Manage your code in Git or SVN repos hosted by any provider, including GitHub and Azure DevOps. Visual studio for mac free download - Visual Studio Community, Visual Studio Professional 2017, Visual Studio Booster, and many more programs.
Visual Studio has not always been as user-friendly on the Mac as it is on a Windows machine. Lately, however, the stable release of VS for Mac is really starting to feel like a simple, but luxurious cousin to Visual Studio 2019. Different, but related. Installation on a Mac is quick, simple, and allows you to get into coding right away - whether you are already familiar or an Apple-only dev getting into something new like Xamarin.
Visual Studio for Mac bears a striking similarity to xCode's solution navigation feel, but brings the power of VS intellisense and an ability to focus on your code in a much cleaner looking environment. In my opinion, this brings the best of both worlds together. But don't take my word for it: here are five reasons to give Visual Studio for Mac another go!
1. The C# Editor in Visual Studio for Mac is Completely NewRoslyn, the .NET compiler platform, is now in the Visual Studio for Mac editor - making your intellisense as powerful as its big brother on Windows. Marrying the functionality ported over from the Roslyn compiler with the (frankly, beautiful looking) simplicity of a native-feeling Mac UI editing experience gives this girl all the feels. It has full support for third-party Nuget packages for .NET Core (utilizing .NET Standard) along with Unity, Xamarin and Cocoa apps.
I didn't notice a big difference gating my progress of a .NET Core app. At this point, I don't know why I would switch over to a windows VM in order to build a microservice API in .NET Core at all!
Finally, I'm loving that VS for Mac now includes 'Go to implementation' as an option in the latest release. Exciting! The C# experience is pretty great now.
2. CLI Developers Can Open .NET Core Projects in TerminalAh, the command line. Many developers love using it for .NET Core instead of the 'visual' click and drag aspect of the Visual Studio IDE. At first, the use of command line programming with ASP.NET Core was the only way you could build those apps. Over time, and especially with the release of Visual Studio 2019, the File > New Project templates for ASP.NET Core apps have been baked into the install bringing a truly visual experience to that build.
For a while, it was unclear if the same command line net new project CLI functionality would be available on Mac, but I am happy to report that it is and it works beautifully! The use of the Terminal app brings that experience to you harcore command line devs.
3. Improved Build Time for XamarinRemember those build and deploy coffee breaks? Well say goodbye (unless you don't want to of course). On one of my Xamarin projects I saw a super impressive 30% faster incremental build time. That's not an insignificant improvement.
This metric is also supported by the April 2019 press release from the VS for Mac team. I used to design my development process in such a way that I could multitask to stay efficient and productive. I'm happy to report those days are gone with much improved build speeds, making the Xamarin app building process something I can say I truly enjoy.
4. .NET Core 3 Support Available Right Out of the GateDoes Visual Studio 2019 have .NET Core 3 support? Yes, but that's no reason to jump over to your Windows machine! You can use all the same, wonderful new stuff on your Apple machine, too.
In fact, I'd argue that Visual Studio for Mac is an excellent place to start learning how to build apps for .NET Core 3. With fewer small windows everywhere like it's Windows-based cousin, VS for Mac allows for a more-focused process.
5. Robust Source Control OptionsThis is where some 'same but different' comes into play. I find that developers coming over from Swift or Objective C development enjoy the experience of source control within Visual Studio for Mac. While there IS a difference in the process for Windows users, I don't find it particularly difficult. Visual Studio for Mac supports Git and Subversion built into the IDE, as well as TFS with a little more effort.
I have used the Github Desktop app for source control of my folders without much issue. This is also my source control workflow for VS Code, and while it is not integrated into the IDE of VS for Mac, it's also not a bad option. For the hardcore command line peeps, you can alternatively use Git inside the CLI tool Terminal, which is native to Apple OS. There is no learning curve here at all for developers who use command line.
Who Should Use Visual Studio for Mac?Visual Studio for Mac is a strong choice for many developers and many use cases. Here are a few that come to mind:
.NET users building Xamarin mobile apps that require IOS builds will benefit tremendously from having all their development on a single machine. Microsoft office for mac.
Developers working with .NET Core, who love working on a Mac, and currently use a virtual machine or Bootcamp to run Visual Studio in a windows environment will benefit from not having to switch over from the Apple operating system constantly.
Unity game developers will find VS for Mac be very intuitive option.
The last group to come over will be .NET Framework developers who have worked with Visual Studio on Windows as their only option for .NET 4.7.2 for example. Sadly no, .NET Framework cannot run on VS for Mac. However, once you are ready to start building your apps or microservices in .NET Core - check it out!
New functionality, extensions and templates are all coming this next year to Visual Studio for Mac that make living in harmony with Apple + Microsoft a real joy.
Learn More About .NET Core, Xamarin, Apple & OAuthIf you'd like to learn more about ASP.NET, Xamarin, or Apple, we've also published a number of posts that might interest you:
For other great content from the Okta Dev Team, follow us on Twitter and Facebook!
 Please enable JavaScript to view the comments powered by Disqus. 
-->Developer Community |System Requirements |Compatibility |Distributable Code |Xamarin |Blogs |Servicing |
Click the button to download the latest version of Visual Studio 2017 for Mac. For instructions on setup and install, see the Setup and Install Visual Studio for Mac documentation.
To learn more about Visual Studio 2017 for Mac, see Mac System Requirements and Mac Platform Targeting and Compatibility.
To learn more about other related downloads, see the Downloads page.
What's New in 7.8Visual Studio 2017 for Mac version 7.8 ReleasesMay 13, 2019 – Visual Studio 2017 for Mac version 7.8.4 
March 12, 2019 – Visual Studio 2017 for Mac version 7.8.3
February 28, 2019 – Visual Studio 2017 for Mac version 7.8.2
February 22, 2019 – Visual Studio 2017 for Mac version 7.8.1
February 20, 2019 – Visual Studio 2017 for Mac version 7.8
Release HighlightsThis release focuses on improving the quality in Visual Studio for Mac through bug fixes, performance improvements, and reliability improvements.
We also updated the version of NuGet to 4.8, .NET Core SDK to 2.1.504, and .NET Core Runtime 2.1.8
Visual Studio 2017 for Mac version 7.8 (7.8.0.1624)released February 20, 2019
ShellWe fixed an issue where custom key bindings for Remove Unused and Sort (Usings) don't work.
We fixed an issue where switching from the application and returning, does not focus on the editor correctly.
We fixed an issue where the cursor in editor window is lost when switching applications.
We fixed an issue where focusing out/into Visual Studio changes the default focused element on the UI.
We fixed an issue where Visual Studio for Mac would fail to track file changes for files in certain folders.
We fixed an issue where Visual Studio for Mac doesn't remember opened files.
We fixed an issue where the Toolbar selector for build configuration is disabled.
We fixed an issue where adding a new folder to a project does not allow instant renaming.
We fixed an issue where Start Debugging after Start without Debugging results in an exception for ASP.Net projects.
We fixed a performance issue with build output search.
The Run Item command on the Solution Explorer has been renamed to Run Project.
We fixed an issue where the welcome page is shown when loading a solution from finder.
.NET CoreWe updated to .NET Core 2.1.8 to include a security update.
We fixed an issue where the create button doesn't create new project for .NET Core 3.0 preview 2.
We fixed an issue where .NET Core 3.0 can be selected in the New Project dialog when it is not supported.
We removed the VB.NET option from .NET Core projects.
ASP.NET CoreVisual Studio For Mac OsWe fixed an issue where the Folder profile would be created with 'Default' configuration instead of 'Release'.
Web ToolsWe fixed an issue where Publish to Azure creates a profile with the wrong name.
We fixed an issue where application arguments are not passed to the Azure Functions host.
We added the following additional Azure Functions templatesCosmosDB trigger
EventHub trigger
IoT Hub trigger
SendGrid trigger
ServiceBus Queue trigger
ServiceBus Topic trigger
We fixed an issue where it was not possible to publish to Azure API App instances.
XamarinWe updated the Xamarin Test Cloud agent NuGet version.
We fixed an issue where the View Archives command would appear in .NET Core projects.
Xamarin.FormsIntelliSense in Xamarin.Forms XAML files for FontFamily is now available.
DesignersWe fixed an issue where the toolbox regressed Android designer usage.
We fixed an issue when attempting to drag and drop controls to iOS storyboards from the Tool Box after searching for controls does not work.
Xamarin.AndroidWe fixed an issue where the JDK notification was shown on the welcome page, even for non-Android projects.
We fixed an issue where launching Visual Studio for Mac without any Java installed shows 2 system prompts to install Java.
We fixed an issue where the Android resource update could occur at the same time as a build which could then cause build issues.
We fixed an issue where Visual Studio for Mac would fail to upload APK to Acer Chromebook R11.
We fixed an issue where new Android apps have uppercase letters in the package name.
We fixed an issue where 'Your project is not referencing the 'Mono.Android.Version=v8.1' framework' when AndroidUseLatestPlatformSDK is true.
We fixed an issue where Visual Studio for Mac does not recognize AndroidManifest in specific build configurations.
We fixed an issue where opening the Report A Problem dialog also displays 'Install JDK' dialog.
We fixed an issue where the Google Play SDK warning is shown even when publishing Ad-Hoc.
Xamarin.iOSIt is now possible to choose .pdf files for image assets that do not support vector images.
We fixed an issue where Visual Studio for Mac erroneously indicates that a Xamarin.Mac property is unavailable.
We fixed an issue where it is not possible to choose devices for named colors in the asset catalog.
We fixed an issue where the iOS simulator is no longer brought to front when starting a debug session.
We fixed an issue where Native References not working in iOS library projects and appear to be ignored.
We fixed an issue where deleting a Native Reference does not delete the the file on disk.
We fixed an issue where the Debugger doesn't connect to a keyboard extension on any device.
Xamarin.MacWe fixed an issue where .xib templates seem to need customObjectInstantitationMethod='direct' added.
We fixed an issue where it is not possible to change the target framework version for Xamarin.Mac full on re-opening project options.
We fixed an issue where the project options for a Mac build (classic) shows incorrect UI.
Code EditorWe fixed an issue where the code fix preview window is too small.
We fixed an issue where error squiggles were not up to date.
We fixed an issue where the editor would freeze while typing
We fixed an issue where Changing the tab would not allow you to search a file
We fixed an issue where Using statement indenting is incorrect.
We fixed an issue where Roslyn throws a fatal exception (System.ArgumentOutOfRangeException).
We fixed an issue where formatting of parameters across multiple lines is incorrect.
We fixed an issue where the constructor generator would cause Visual Studio for Mac to crash.
We fixed an issue where smart semicolon placement causes incorrect semicolon placement.
We fixed an issue where typing can be slow in large files when accessibility is enabled.
We fixed an issue where a fatal error can occur when trying to navigate inside the editor using VoiceOver.
We fixed an issue where the caret location in quick fix margin is incorrect.
We fixed a performance issue where indent correcting is taking up too much time on large files.
We fixed an issue where Intellisense soft-selection is confusing.
We fixed an issue where Visual Studio for Mac can't open .targets files.
We fixed an issue where the display updates partially when commenting a collapsed method.
We fixed an issue where C# syntax highlight doesn't work for some of the keywords.
We fixed an issue where invoking some snippets from the toolbox in .cs files leads to poorly formatted code.
We fixed an issue where pressing Down to choose the closing tag completion in XAML IntelliSense closes the completion window.
We fixed an issue where the file 'redacted' could not be opened.
We fixed an issue where sometimes pasting fails in XAML files.
We fixed an issue where, when adding an attribute via Intellisense, it does not trim 'Attribute' from the name.
We fixed an issue where code suggestion does the wrong thing when ( is pressed after a stray arrow key.
NuGetWe fixed an issue where Visual Studio for Mac crashes after 'Could not add packages' error.
We updated the version of NuGet to 4.8.
NuGet package diagnostic warnings are now shown in the Solution Explorer. Any diagnostics warnings will be rendered with a warning icon and the full text of the warning available as a tool tip.
We fixed a set of issues with NuGet:problem while restoring NuGet packages which don't have stable version.
The VS4Mac bundle nuget version is too old: 4.3.1.
Referencing packages conditionally using variable does not work correctly.
Xamarin.Forms app with multi target framework library referenced fail to build.
Visual Studio Mac Csproj build not support Item contidion.
Support conditional NuGet PackageReferences in multi-targeting projects.
Show per-framework dependencies when multi-targeting.
VS cannot build F# dotnet core solution.
Nuget restore ignore build targets.
NuGet restores the wrong version of Microsoft.AspNetCore.App.
DebuggerWe fixed an issue where the debugger would fail when running on an external console on Mojave.
Test ToolsWe fixed an issue where xUnit Fact 'DisplayName' not shown in test explorer if the name has a period at the end.
We fixed an issue where the text editor unit test integration ('Unit test 'name' could not be loaded') would fail.
We fixed a performance issue where the 'Test Results' pane has bad performance when very large amounts of text are shown.
We fixed an issue where the unit test integration in the editor does not properly trigger test cases.
We fixed an issue that could cause xunit to fail to restore.
F#We fixed an issue where open statements for F# must be manually added when pasting/writing code.
We fixed an issue where new F# projects shows IntelliSense errors.
We fixed an issue for F# projects where Visual Studio for Mac overwrites the project GUID to be lowercase instead of uppercase.
Visual Studio For Mac FreeProject SystemWe fixed an issue where the copy & paste of a XAML file causes a disassociation between the .xaml and .xaml.cs files.
We fixed an issue where files are being added to ItemGroup.Compile(Remove) and this related issue - Error type of namespace not found.
We fixed an issue where an invalid C# file is created with a new library project.
We fixed an issue where it is not possible to create a culture specific .resx file through the 'New File .' menu in the Solutions Explorer context menu.
Assembly BrowserWe fixed an issue where the Assembly Browser shows the wrong icon for properties.
We fixed an issue where System.DayOfWeek enum (Wednesday) does not appear to be assigned a value.
AccessibilityWe fixed a number of accessibility issues in this release, including several VoiceOver issues in the Debugger and in creating iOS developer certificates, and Keyboard issues in the Android SDK Manager.
OtherWe fixed an issue where unchecking the Organize Using > Place System directives first setting does not save.
We fixed an issue where Visual Studio for Mac is not remembering settings.
We fixed an issue where Checking for updates can result in multiple prompts to sign in.
Visual Studio 2017 for Mac version 7.8.1.4released February 22, 2019
We fixed an issue where Visual Studio for Mac becomes unresponsive when selecting two column view.
Visual Studio 2017 for Mac version 7.8.2.1released February 28, 2019
We fixed an issue where Debugger features sometimes don't work as expected with Unity.
Visual Studio 2017 for Mac version 7.8.3.2released March 12, 2019
This release contains an updated 4.8 NuGet Client, which in turn closes a NuGet Client vulnerability.
We fixed an issue where Using Git to publish an existing project to a new remote repository was not working.
We fixed an issue where Git remote operations were failing in Visual Studio for Mac:.
We fixed an issue where Tooltips not being shown for F# solutions.
We fixed an issue where The Report a Problem dialog crashes Visual Studio for Mac when entering details.
We fixed an issue where Visual Studio for Mac crashes while using Report a Problem if the debugger connection is lost.
We fixed an issue where Two sign in popup windows would show if you weren't signed in and tried to Report a Problem.
We fixed an issue causing warnings about missing icons to show up in the log files when using Report a Problem.
We fixed an issue preventing build messages from displaying in the Build Output window after building Docker Compose projects.
Visual Studio 2017 for Mac version 7.8.4.1released May 13, 2019
This release fixes an issue where (Visual Studio for Mac 7.8.3 crashes after loading a second solution)[https://developercommunity.visualstudio.com/content/problem/509716/visual-studio-783-build2-crashes-after-loading-a-s.html].
Feedback & SuggestionsVisual Studio Code For MacWe would love to hear from you! You can report a problem through the Report a Problem option in the Visual Studio for Mac IDE, and track your feedback in the Developer Community portal. For suggesting new features you can use Suggest a Feature, these are also tracked in the Developer Community.
Visual Studio For Mac DownloadBlogsTake advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.

Visual Studio 2017 for Mac Release Notes HistoryYou can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.
Top of Page