How to install.NET Framework 3.5 SP1 into Visual Studio 2017. Open the Visual Studio Installer (search for it in the Start menu). Choose to modify the installation you desire. Go to the 'Individual Components' tab. Under the '.NET' section choose '.NET Framework 3.5 Developer Tools'.
-->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.8
Visual Studio 2017 for Mac version 7.8 Releases
- May 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 Highlights
This 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
Shell
- We 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 Core
- We 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 Core
- We fixed an issue where the Folder profile would be created with 'Default' configuration instead of 'Release'.
Web Tools
- We 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 templates
- CosmosDB 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.
Xamarin
- We updated the Xamarin Test Cloud agent NuGet version.
- We fixed an issue where the View Archives command would appear in .NET Core projects.
Xamarin.Forms
- IntelliSense in Xamarin.Forms XAML files for FontFamily is now available.
Designers
- We 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.Android
- We 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.iOS
- It 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.Mac
- We 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 Editor
- We 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.
NuGet
- We 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.
Debugger
- We fixed an issue where the debugger would fail when running on an external console on Mojave.
Test Tools
- We 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.
Project System
- We 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 Browser
- We 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.
Accessibility
- We 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.
Other
- We 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.4
released 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.1
released 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.2
released 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.1
released 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
We 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.
Blogs
Take 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 History
You can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.
| Developer Community| System Requirements| Compatibility| Distributable Code| License Terms| Blogs| Known Issues |
Visual Studio 2017 contains many new and exciting features and IDE productivity enhancements tosupport Windows app development, cross-platform mobile development, Azure development, web and cloud development,and more. To try out Visual Studio 2017, see Visual Studio 2017 Downloads.For more information about everything that's new in this release, see theVisual Studio 2017 release notes andWhat's New in Visual Studio 2017.
For Visual Studio Code, see Visual Studio Code FAQ.
For Visual Studio 2017 for Mac, see Visual Studio 2017 for Mac Platform Targeting and Compatibility.
For Visual Studio 2017 for Mac release notes.
For Visual Studio 2017 for Mac, see Visual Studio 2017 for Mac Platform Targeting and Compatibility.
For Visual Studio 2017 for Mac release notes.
Installation
You can install and use Visual Studio 2017 alongsideprevious versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012.
Download
Click a button to download the latest version of Visual Studio 2017. For instructions on installing and updating Visual Studio 2017, see the Update Visual Studio 2017 to the most recent release. Also, see instructions on how to install offline.
Visit the visualstudio.microsoft.com/downloads page to download other Visual Studio 2017 products.
Note: Installation package size will vary depending on your current Visual Studio configuration.
System Requirements
For information on the system requirements for installing and running the Visual Studio 2017 family of products,including Team Foundation Server 2017, see the Visual Studio 2017 System Requirement page andVisual Studio 2017 for Mac Product Family System Requirements.
Feedback and Support
For support, or to submit feedback on Visual Studio, see:
Upgrade Projects to Visual Studio 2017
When following the supported upgrade paths, your Visual Studio source, solutions, and project files will continueto work; however, you should expect to make some changes to sources. While we cannot guarantee binary compatibilitybetween releases, we will do our best to document significant changes to assist you with updates.
Note
For details on how to migrate your projects to Visual Studio 2017, see Porting, Migrating, and Upgrading Visual Studio Projects.
Platform Targeting
Visual Studio provides cutting-edge tools and technologies to create apps that take advantage of thelatest platform capabilities, whether Windows, Android, iOS, or Linux. Visual Studio 2017 also targetsearlier platforms so you can create new apps or modernize existing apps that execute on earlier versionsof Windows while leveraging the enhanced development tools, quality enablement, and team collaborationcapabilities in Visual Studio 2017. For more information, see Managing references in aproject and Visual Studio Multi-TargetingOverview.
Visual Studio 2017 Support for Windows Development
The following table explains the Microsoft Windows platforms for which you can build apps by using Visual Studio 2017.
Build Apps that Run on Windows Clients | Using Tools for Native and Managed Classic Windows Desktop Development | Using Tools for UWP App Development |
Windows 10 | Yes (see notes below) | Yes (see notes below) |
HoloLens | No | Yes See the Windows Holographic Dev Center. |
Xbox One | Not applicable | Yes See the Xbox Dev Center. |
Windows 8.1 (Windows 8) | Yes | Windows Store app development is not available. |
Windows 7 | Yes | Not applicable |
Windows Vista | Yes Remote debugging and profiling tools are not available. | Not applicable |
Windows XP | Yes Managed development requires using Visual Studio .NET multi-targeting. Remote debugging and profiling tools are not available. | Not applicable |
Build Apps that Run on Windows Phone | Using Tools for Native and Managed Classic Windows Desktop Development | Using Tools for UWP App Development |
Windows 10 Mobile | No | Yes (see notes below) |
Windows Phone 8.1 and earlier | No | Windows Store app development is not available. |
Build Apps that Run on Windows Server | Using Tools for Native and Managed Classic Windows Desktop Development | Using Tools for UWP App Development |
Windows Server 2016 | Yes | Yes (see notes below) |
Windows Server 2016, Nano Server Installation Option | Yes, for .NET Core and a subset of Win32 See the Nano Server Dev Center. | No |
Windows Server 2012 R2 | Yes | Windows Store app development is not available. |
Windows Server 2012 | Yes | Windows Store app development is not available. |
Windows Server 2008 R2 | Yes | Not applicable |
Windows Server 2008 | Yes Remote debugging and profiling tools are not available. | Not applicable |
Windows Server 2003 | Yes Remote debugging and profiling tools are not available. Managed development requires using Visual Studio .NET multi-targeting and requires side-by-side installation of Visual Studio 2010. For more information, see: A Look Ahead at the Visual Studio 2012 Product Lineup and Platform Support. | Not applicable |
Build Apps that Run on Windows Embedded Devices | Using Tools for Native and Managed Classic Windows Desktop Development | Using Tools for UWP App Development |
Windows 10 IoT Core | Yes, for a subset of Win32 APIs See the IoT Core API Porting Tool for information. | Yes See the Windows IoT Dev Center for additional tools and resources. |
Windows 10 IoT Mobile Enterprise | No | Yes See the Windows IoT Dev Center for additional tools and resources. |
Windows 10 IoT Enterprise | Yes See the Windows IoT Dev Center for additional tools and resources. | Yes See the Windows IoT Dev Center for additional tools and resources. |
Windows Embedded 8 Standard and 8.1 Industry | Yes | No |
Windows Embedded Compact 2013 | No | Not applicable |
Windows Embedded 7 (Compact, Standard, and POSReady) | No | Not applicable |
Windows Embedded CE 6.0 and earlier | No | Not applicable |
Windows XP Embedded (Including POSReady 2009, WES 2009, WEPOS) | No | Not applicable |
Notes
- For support information regarding Microsoft operating systems, see Microsoft Support Lifecycle and Windows 10 Release Information.
- For support information on Microsoft .NET Framework, see .NET Framework Support Lifecycle FAQand .NET Framework System Requirements.
- Windows 10 Enterprise LTSB edition and Windows 10 S are not supported for development.You may use Visual Studio 2017 to build apps that run on Windows 10 LTSB and Windows 10 S. Remote debuging is supported on LTSB.
- Universal Windows app development for all target platforms is available when Visual Studio is installed on Windows 10.
- Universal Windows apps can be built from the command line when using Windows Server 2012 R2 or Windows Server 2016. UWP development—includingdesigning, editing, and local debugging—is not available on Windows Server. You may deploy these apps to Windows server and debug them remotely.
- Cordova, Unity, and Xamarin can also be used for cross-platform development of Universal Windows Apps on Windows 10.
Visual Studio 2017 Support for .NET Development
Visual Studio 2017 supports development of apps that use any of the .NET implementations. Among the workloads and project types, you can find support for.NET Framework, .NET Core, Mono, and .NET Native for Universal Windows Platform (UWP). Visual Studio 2017 supports the following implementations:
- .NET Framework versions 4.7, 4.6.2, 4.6.1, 4.6, 4.5.2, and 3.5
- .NET Core 2.0, 1.1, and 1.0.
Note
For more information on each of these implementations, and on the common API specification .NET Standard, see .NET architectural components.
Visual Studio 2017 Support for Android Development
Visual Studio 2017 enables you to build native Android apps using Xamarin and C# or using Java/C++, and hybridAndroid apps using Apache Cordova 6.3.1 and JavaScript and TypeScript. The Visual Studio Tools for Unity andthe Unreal Engine enable Android game development. You can also use Visual Studio for Macto build Android apps using a Mac.
You can use Visual Studio setup to easily obtain the Android SDK and Android API levels 19, 21, 22, and 23.You can download additional API levels separately using the Android SDK Manager.You can also use Visual Studio Setup to obtain the Android Native Development Kit (R10E), Java SE Development Kit, and Apache Ant.
For more information, see Android development with Visual Studio andMobile App Development.
Note
For information on .NET development for Android, see .NET architectural components.
Visual Studio 2017 Support for iOS Development
Visual Studio 2017 enables you to build and debug apps for iOS by using Apache Cordova, C++, Unity, or Xamarinand a Mac configured for iOS development when using remotebuild, vcremote, the Visual Studio Tools for Unity,or the Xamarin Mac Agent. Xamarin supports iOS 7 and higher, and requires OS X 10.10 'Yosemite' or higher.Apache Cordova supports iOS 8 and higher, and requires OS X 10.9 'Mavericks' and higher. You can also useVisual Studio for Mac to build iOS apps using a Mac.
Note
For more information, see Cross-platform mobile development in Visual Studio.For information on .NET development for iOS, see .NET architectural components.
Visual Studio 2017 Support for Linux Development
Visual Studio 2017 enables you to build and debug apps for Linux using C++, Python, and Node.js.Creating C++ apps for Linux requires theVisual C++ for Linux Development extension. Creating apps with Python orNode,js, requires that you enable remote debugging on the target Linux machine. You can also create, buildand remote debug .NET Core and ASP.NET Core applications for Linux using modern languages such as C#, VB and F#.
Note
For information on .NET development for Linux, see .NET architectural components.
- CentOS 7.1 and Oracle Linux 7.1
- Debian 8
- Fedora 23
- Linux Mint 17
- openSUSE 13.2
- Red Hat Enterprise Linux 7.2
- Ubuntu 14.04 and 16.04
Note
For more information see https://dot.net/core.
Visual Studio 2017 Support for macOS Development
Visual Studio 2017 enables you to build console applications and ASP.NET applications that target macOS.However, debugging is not supported. For additional macOS development tools choices, try Visual StudioCode or Visual Studio for Mac. Visual Studio Code provides a streamlined,extensible developer tool experience for macOS. Visual Studio for Macprovides a feature-rich IDE that enables you to build native macOS apps, including ASP.NET, using C#.
Note
For information on .NET development forMacOS, see .NET architectural components.
Other Platforms and Technologies
Visual Studio 2017 also supports the following platforms and technologies. For more information, seehttps://visualstudio.microsoft.com/vs/features/.
- Apache Ant
- Azure web apps and connected services, including Azure Data Lake
- Docker
- PowerShell
- Python and Python IoT tools
- Web Development with ASP.NET, HTML5/CSS3, JavaScript, Node.js, Python, or TypeScript
Compatibility with Previous Releases
.NET Framework
.NET 4.7 is is a highly compatible in-place update of .NET 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, and 4.6.2.
Note
For more information, see the Migration Guide to the .NET Framework 4.7, 4.6, and 4.5.
Team Explorer and Team Foundation Server
Team Explorer for Visual Studio 2017 will connect to Team Foundation Server 2017, Team Foundation Server 2015,Team Foundation Server 2013, Team Foundation Server 2012, and Team Foundation Server 2010 SP1.
Silverlight
Silverlight projects are not supported in this version of Visual Studio. To maintain Silverlight applications,continue to use Visual Studio 2015.
Windows Store and Windows Phone apps
Projects for Windows Store 8.1 and 8.0, and Windows Phone 8.1 and 8.0 are not supported in this release. Tomaintain these apps, continue to use Visual Studio 2015. To maintain Windows Phone 7.x projects, use Visual Studio 2012.