BT

New Early adopter or innovator? InfoQ has been working on some new features for you. Learn more

VS2015 Update 2 Focuses on Stability

| by Jeff Martin Follow 5 Followers on Feb 16, 2016. Estimated reading time: 1 minute |

Microsoft has released the first preview of Update 2 for Visual Studio 2015.  This second major update to VS2015 is focused on fixing a significant number of bugs that can occur while using three of the major languages:  C++, C#, and Visual Basic.  Developers who are used to experiencing crashes, out of memory exceptions, and project loading delays are expected to benefit from the patches being introduced in Update 2.  The fixes also address multiple issues that can arise during setup which previously prevented or delayed installation.

Those who use Git with VS2015 may find the addition of Git LFS (Large File Storage) useful.  Git LFS is used to provide Git-like functionality when working with large files.  Rather than store large files (videos, Photoshop files, etc) in Git itself, pointers to these files are stored instead that contain instructions to where these files can be found.  That way large binary files can benefit from some aspects of version tracking without requiring them to be stored directly within Git—a task for which a typical Git repository is ill-suited.  Besides LFS support, Git in VS2015 has been expanded to support reset (--hard and --mixed), cherry-picking, and staging.

Users should additional improvements to the overall performance of VS2015 in several areas that include:

  • Opening and browsing with Team Explorer
  • Reduced startup time when extensions have been installed
  • Stability of keeping managed language projects open for long periods of time
  • Long filename paths in projects under source control

VS2015 Update 2 CTP is available now for experimentation, however it is important to note that it is considered to be a prerelease version and should not be installed in a production environment.  Release notes and a list of repaired bugs are both available on MSDN.

(Feb 24 - Updated to correct wording in last paragraph.  Hat tip to reader Muhammad Ali.)

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Slight Correction by Muhammad Ali

...it is considered to be a prerelease version and should be installed in a production environment.

Probably you meant should not be installed in a production environment.

Re: Slight Correction by Jeff Martin

That is correct. Thanks for the note!

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

2 Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT