Visual Studio 2015 Update 3 Patch (KB3165756, 14.0.25422.01)


Today, Microsoft released a patch for Visual Studio 2015 Update 3, which was released on 27th June 2016. It is a cumulative update with fixes to the existing Microsoft Visual Studio 2015 Update 3 installation. If you have installed Update 3, install the patch KB3165756 mentioned below.

 

Though it is not mandatory, but good to have install this patch as it addresses many fixes related to memory leaks, crash and other issues.

 

Microsoft released Visual Studio 2015 Update 3 Patch (KB3165756, 14.0.25422.01)

 

These fixes part of the patch "KB3165756" dated. 12th 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.25422.01.

 

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:

    1. Memory leak in Visual Studio when you use the editor light bulb to apply code actions to a C# or Visual Basic file.
    2. Some large C# and Visual Basic projects that contain thousands of source files may experience memory and performance degradation. The reason behind this was compilation symbols unnecessarily realized.
    3. Shared projects may report an error after they are unloaded and reloaded if some of their source files are open.
    4. Visual Studio may crash and cause a stack overflow exception when it generates IntelliSense for some C# files that contain nested generic types.
    5. In ASP.NET .cshtml files, committing code completion after you type the full snippet may cause incorrect snippets to be added to the source file.
    6. Memory leak in the StandardCollector.Service.exe process may encounter when you debug managed code on Windows 7 that has Visual Studio 2015 Update 3 installed.
    7. When you debug JavaScript files by using certain module configurations, the debugger might not load the correct source maps. This will cause the program to crash.
    8. When you edit TypeScript build properties, the outDir option does not save the changes that you made. After you make changes, the build properties page displays the previous state of outDir.

 


If you have come this far, it means that you liked what you are reading. Why not reach little more and connect with me directly on Twitter, Facebook, Google+ and LinkedIn. I would love to hear your thoughts and opinions on my articles directly. Also, don't forget to share your views and/or feedback in the comment section below.

1 comments

  1. this big data update.... where i can find offline ?

    ReplyDelete

 
© 2008-2016 Kunal-Chowdhury.com - Microsoft Technology Blog for developers and consumers | Designed by Kunal Chowdhury
Back to top