In this article, you will find information regarding the current Preview release for Visual Studio 2017. Click the button to download.
This release is not "go-live" and not intended for use on production computers or for creating production code.
We’d love to hear from you! You can report a problem via the Report a Problem option in the upper right hand corner of either the installer or the Visual Studio IDE itself. You can track your feedback in the Developer Community portal. For suggestions, let us know through UserVoice.
Please refer to the Known Issues section.
Top Issues Fixed in this Release
- Fixed issue where the use of RS3 UWP projects produced squiggles in the markups due to missing resources.
- Fixed installer UI reliability issue produced when a user clicks on the launch button after clicking on cancel.
Summary of Updates in this Release
- You can get real time feedback with live unit testing support for your .NET Core projects.
- Visual Studio IDE Improvements
- We’ve added related event clusters to the search queries to help you discover patterns in your application's behavior.
- The SetThreadDescription API is now supported while debugging and the thread names you set will show up in the Threads window and dropdown in the Debug Location toolbar.
- We’ve made usability and icon improvements for high-DPI support and better toolbar responsiveness.
- We enhanced the CMake tools to support the Ninja generator and CTest integration.
Top Issues Fixed in this Release
The Developer Community spoke and we listened. This list provides the issues that received your highest votes and were fixed in this release.
Endless loop when updating the Visual Studio Installer.
"Scanning new and updated MEF components" runs every time Visual Studio 2017 launches.
TFS unexpectedly goes offline when opening a solution.
Build fails to start with solutions built with previous Visual Studio versions.
Several errors are generated during the Attach to Process.
Solution build time is much slower when enabling Lightweight Solution Load.
Pressing the 'Enter' key inserts new line instead of the expected C++ autocomplete.
Git processes are unable to start.
Team Explorer does not recognize previously cloned repository as being part of a VSO project.
Unable to clone Git repository in Team Services.
What's New in this Release
- We added live Unit Testing support for .NET Core projects.
- You can now create .NET Core console applications, and .NET Core and .NET Standard class libraries using Visual Basic.
- Visual Studio now supports creating and running .NET Core 2.0 apps if the SDK is installed separately. Install the latest builds of the .NET Core 2.0 SDK.
See .NET Core 2.0 blog for more details.
We added support for containerizing ASP.NET Core apps as Windows Nano images. You can now select Nano as the container platform. You can do this under File->New Project for ASP.NET Core projects. For your existing projects, it can be added using the Project Context Menu.
We added clusters of related events to the search query results in the Application Insights Search tool. These clusters can help you discover surprising patterns in your application's behavior, like a large volume of exceptions coming from a single country, version, or user.
- The SetThreadDescription API is now supported while debugging using Start Debugging (F5) or Attach to Process (Ctrl+Alt+P). The thread names that are set via this API will now show up in the Threads window and in the Thread dropdown in the Debug Location toolbar. This is not currently supported while dump debugging.
- The Output Window now shows you the console output of an application running inside a Windows Container while debugging.
- We added new support for debugging .NET Core apps you run inside Windows Containers based on Nano Server.
- We fixed the "hidden window" bug that made Visual Studio appear to hang before its main window appeared.
- We increased the clickable target area to make it easier to dismiss notification tips.
- We added support for file globbing outside of your project folder.
Sign in and identity improvements
- We fixed the account picker control so "Re-enter credentials" works more reliably.
- In some cases, the account picker would clear accounts upon re-entering credentials. This fix should resolve that issue.
We increased the clickable target area on Start Page MRU “pins” to make it easier to pin items you care about to the top of the MRU.
Lightweight solution load
- We increased build speed and stability.
- We reduced the number of loaded projects.
- We provided a new option (Figure 1) to let Visual Studio decide what’s best for this solution.
- We improved stability for toggling between folder and solution.
- Open folder extenders can add source control icon to your folders. This allows you to quickly see source control state of your files in Solution Explorer. Currently implemented by SVN.
Continuous delivery tools
We moved these features from the CD4VS extension into Visual Studio:
- Configure continuous delivery for solutions containing ASP.NET projects targeting an Azure App Service.
- Configure continuous delivery for solutions containing ASP.NET Core projects targeting an Azure App Service.
Container development tools
Visual Studio 2017 15.3 preview now supports the breadth of container development across existing .NET Framework apps with Windows Containers, to .NET Core with Windows, and Linux Support. Recent additions include support for your .NET Core applications in containers running Nano server, as well as debugging improvements for .NET Framework applications in containers.
Service fabric tools
This release provides a new stateful ASP.NET Core project template, support for both 2.5 and 2.6 SDK's (and corresponding runtimes) of Service Fabric, as well as several bug fixes.
Redgate ReadyRoll Core:
We updated to version 220.127.116.1102 to add:
- Icon improvements with high-DPI support and better responsiveness in the toolbar.
- Usability Improvements to Project Settings Tab.
- Usability Improvements to Getting Started view, Deployment Summary, and Login Window.
- Added a view for when the target database doesn’t exist.
- Added a ReadyRoll entry under the Tools menu.
- Added support for SQL Authentication when opening SSMS.
Redgate SQL Prompt Core: We updated to version 18.104.22.1687 to improve syntax support for SQL Server 2016, as well as fixed issues around name qualification, and with Azure connectivity.
Redgate SQL Search: We updated to version 22.214.171.1241 to add an icon for high-DPI support.
We enhanced CMake tools for Visual Studio to provide you with support for CTest integration and the Ninja generator, including full support to build, debug, and edit with IntelliSense.
Here are the known issues and available workarounds specific to this Preview release. For known issues in Visual Studio 2017, which will also affect this release, see Visual Studio 2017 Known Issues.
R Tools option missing on Windows 7
R Tools neither install nor appear as an option on Windows 7.
There is no workaround. The update is in works to re-enable the install.
For a current list of issues and workarounds with .NET Core and ASP.NET Core 2.0 see our GitHub page.
Multi TFM .NET Core projects are not supported in Live Unit Testing.
There is no workaround at this time.
Remote Tools for Visual Studio 2017 Preview are not available
We have not made an update for the Remote Tools for Visual Studio 2017 Preview available.
The Remote Tools for Visual Studio 2017 is compatible with Visual Studio 2017 Preview. However, if you are interested in using the latest preview version of the remote debugger, see Run the remote debugger from a file share.
There are multiple issues with the F# Tools in Update 3 Preview 1 which are being addressed. There is no workaround for these issues at this time, save for not using Update 3 Preview 1.
Completion lists do not appear. If a nightly build is installed, a modal dialog will pop up every time completion is attempted to be invoked.
Do not use Update 3 Preview 1.
Glyphs in QuickInfo and Signature Help display incorrect icons.
Do not use Update 3 Preview 1.
Settings for IntelliSense do not load.
Do not use Update 3 preview 1.
R 3.4.0 is not yet supported
R 3.4.0 downloaded from cran.r-project.org is not yet supported due to changes in some native APIs.
Previous versions of R continue to work correctly, including Microsoft R Client as included in the installer. Support for R 3.4.0 will be added in a future update.
Cannot create team projects or update process templates
Customers cannot create new team projects or upload or edit process templates from Visual Studio 2017, version 15.3 Preview 1. Project creation from web access continues to work.
This will be fixed in the next preview. At this time, please use the released Visual Studio 2017, version 15.2 or earlier, if you need to create team projects or upload process templates from Visual Studio.
Error when opening folder if C# and Visual Basic Component is not installed
Error message "Exception thrown by the target of an invocation” when opening folder if C# and Visual Basic Component is not installed.
Install the C# and Visual Basic Component.
Microsoft Test Manager (MTM) client cannot connect to Team Foundation Server or Visual Studio Team Services
MTM client cannot connect to Team Foundation Server or Visual Studio Team Services, blocking users from creating and running tests cases.
This will be fixed in the next preview. At this time, please use the following workaround:
Find the folder in which mtm.exe is installed by searching for mtm.exe in the start menu and choosing 'Open file location' in the right click menu. Edit the 'mtm.exe.config' file present in the same folder to add the following section in configuration -> runtime section:
<dependentAssembly> <assemblyIdentity name="Microsoft.VisualStudio.Threading" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/> <bindingRedirect oldVersion="10.0.0.0-126.96.36.199" newVersion="188.8.131.52"/> </dependentAssembly>
Building a DSL project fails with FileNotFoundException
Building a newly created DSL project fails with FileNotFoundException.
Add the following snippet to assemblyBinding element in MSBuild.exe.config (in
<dependentAssembly> <assemblyIdentity name="Microsoft.VisualStudio.Zip.9.0" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /> <codeBase version="184.108.40.206" href="..\..\..\Common7\IDE\PrivateAssemblies\Microsoft.VisualStudio.Zip.9.0.dll" /> </dependentAssembly>