Microsoft released another build 14.0.25424.00 for Visual Studio 2015 Update 3, which is a patch under the KB article KB3165756. This patch builds are cumulative service updates and cover fixes for high-impact bugs noticed by product team and the community.
If you have Visual Studio 2015 Update 3, you should download and install these patch builds in order to work smooth with your favourite IDE installation.
The build that was released last week (12th July 2016) had the version no: 14.0.25422.01.
These fixes part of the patch "KB3165756" dated. 20th July 2016 for Visual Studio 2015 Update 3 addresses high priority bugs that were either found by the product team or reported by the community. After installing this update, the version no. of Visual Studio 2015 will increase to 14.0.25424.00.
Though it is not mandatory, but it would be good if you install this patch as it addresses many fixes related to memory leaks, crash and other priority issues.
You can download this update either from Microsoft Download Center or directly from Visual Studio 2015 by following this path: "Tools -> Extensions and Updates -> Updates -> Product Updates".
This patch includes fixes for the following issues:
- An issue that affects inspecting local variables for code that's embedded in cshtml files occurs in ASP.NET Core applications.
- This update enables you to permanently dismiss the Configuration CI banner in TestExplorer.
- Package encryption contains an outdated flag.
- Potential crashes occur when AAD users who have implicit permissions try to retrieve app names in the Packaging wizard.
- After you install Windows updates, you may see various package load failures when you start Visual Studio. Although this update fixes this issue, you can also delete the ComponentModelCache folder as a workaround.
- A regression in the MFC CMFCToolBarButton button prevents MFC apps from correctly working in Visual Studio 2015 Update 3.
- Applications that use lots of async tasks can fail to display those tasks in the Tasks window.
- Performance issue occur when Visual Studio is started by having the output window open.
- A dialog box opens when you start the XAML designer in a Universal Windows Platform (UWP) app.