Visual Studio 2017 Version 15.6 Preview
[Hello, we are looking to improve your experience on the Visual Studio Blog. It will be very helpful if you could share your feedback via this short survey that should take less than 2 minutes to fill out. Thanks!]
A few days ago we released Visual Studio 2017 version 15.5 and an update to Visual Studio for Mac, and today we are releasing the first preview of the next minor update: Visual Studio 2017 version 15.6. You can either download the Preview, or, if you already have it installed, click on the notification you’ll receive in the product informing you that the update is available.
This latest preview contains new features, productivity improvements, and other enhancements that address our customers’ feedback. Read the feature highlight summary below, and check out the Visual Studio 2017 version 15.6 preview release notes for a more detailed description of what’s new and how to use the new goodness contained in this Preview.
The CPU Usage tool (available during F5 Debugging in the Diagnostic Tools window and in the ALT-F2 Performance Profiler) now displays source line highlighting based on the CPU consumption of specific lines of code. When you view the Call Tree or Caller/Callee views of the CPU Usage tool, the source for the selected function is displayed with CPU consumption indicated on each source line of the function. If CPU performance of a function is a concern, now you can determine specifically what source lines of the function are responsible for the CPU consumption when the function is executing. This feature requires that source information be included in the generated PDB which is controlled by the project settings. Projects for which PDBs do not have source information will be unable to display either the line attribution or the source file.
Team Explorer: In this Preview, we made some improvements to the Git tags functionality, largely based on your feedback via UserVoice. There’s a new Tags tile available in the Team Explorer window so that you can view all the tags in your repo. In addition to create, you can now delete tags, push tags, and create a new branch from tags. Visual Studio Team Services users can now check out pull request branches, which makes it easier to review pull requests, test changes, and build your code.
Managing Secrets: Many of you know that it’s a best practice to keep sensitive settings like connection strings, passwords, or other credentials outside of source code and in a safe place like Azure Key Vault. Last month we introduced the App Authentication Extension which makes it easy to configure your machine to use these protected settings so that you can develop and debug apps locally using your Visual Studio credentials. With Visual Studio Version 15.6 Preview 1, we’ve moved this functionality directly into the main setup, so now everyone has access to this feature by default. Learn more about managing secrets in the cloud.
With Visual Studio 2017 version 15.6 Preview, you now have the ability to create CMake projects the Add New Project dialog. This Preview also provides built-in support for Android NDK r15c and guaranteed copy elision per the C++17 standard. In addition, the ImageWatch extension has been updated to work with Visual Studio 2017
IntelliSense for Python code now no longer requires a completion database. Instead of waiting up to four hours after installing a new package, you can start using it immediately. We have also added experimental support for managing Anaconda packages, new code snippets, and more customizable syntax highlighting. Read our blog post for full details on these improvements and how to enable our experimental features.
Real time test discovery is a new Visual Studio feature for managed projects that uses the Roslyn compiler to discover tests and populate the Test Explorer in real-time without requiring you to build your project. This feature was introduced behind a feature flag in version 15.5, and it will now be on by default in version 15.6. This feature not only makes test discovery significantly faster, but it also keeps the Test Explorer in sync with code changes such as adding or removing tests. Since real-time discovery is powered by Roslyn, it is only available for C# and Visual Basic test projects using xUnit, NUnit, and MSTest. To learn more, check out the Real Time Test Discovery blog post and Channel9 video.
With this Preview, Visual Studio now supports configuring continuous delivery to Azure for Team Foundation Version Control (TFVC), Git SSH remotes, and Web Apps for containers. Read more about these features on this post about Continuous Delivery Tools for Visual Studio.
WCF Connected Services
The WCF Web Service Reference connected service provider now supports updating an existing service reference. This simplifies the process for regenerating the WCF client proxy code for an updated web service. To use this new feature, open the context menu of a service reference folder to be updated and select the ‘Update Microsoft WCF Web Service Reference Provider…” option. This will regenerate the Reference.cs file using the settings for which the file was originally generated. Please note, this feature is not supported for service references added to the project using a previous version of Visual Studio 2017.
Try it out today!
If you’re not familiar with Visual Studio Previews, take a moment to read the Visual Studio 2017 Release Rhythm. Remember that Visual Studio 2017 Previews can be installed with other versions of Visual Studio and other installs of Visual Studio 2017 without adversely affecting either your machine or your productivity. Previews provide an opportunity for you to receive fixes faster and try out upcoming functionality before it becomes mainstream. Similarly, the Previews enable the Visual Studio Engineering team to validate usage, incorporate suggestions, and detect flaws earlier in the development process. We are highly responsive to feedback coming in through the Previews and look forward to hearing from you.
Please Install the Visual Studio 2017 Preview today, exercise your favorite workloads, and tell us what you think. You can report issues to us via the Report a Problem tool in Visual Studio or you can share a suggestion on UserVoice. You’ll be able to track your issues in the Visual Studio Developer Community where you can ask questions and find answers. You can also engage with us and other Visual Studio developers through our Visual Studio conversation in the Gitter community (requires GitHub account).