3 ms·

Visual Studio really needs to drop the large but seldom release schedule. There are so many pieces that just need minor improvements, that must await for these

by dvcc 10y ago

Visual Studio really needs to drop the large but seldom release schedule. There are so many pieces that just need minor improvements, that must await for these gigantic day-to-install releases before they see light. Saying that, I absolutely love VS just wish they actually managed to fix the update/release process.

platz 10y ago
enterprise does not like the rolling-release model.
- vvanders 10y ago
  They've been doing it for VS Code which is now my goto editor for anything not C++ or Java.
- yuhong 10y ago
  Not to mention each new release of Visual C++ for example require a new CRT etc with different file names.
  - petters 10y ago
    I think they talked about this some time ago and that they were (slowly) moving away from new CRTs all the time.
  - anonymfus 10y ago
    >Starting with Visual Studio “14,” we will stop releasing new versions of the CRT with each release of Visual Studio. Whereas before we would have released msvcr140.dll in this forthcoming release, then msvcr150.dll in the next release, we will instead release one new CRT in Visual Studio “14” then update that version in-place in subsequent releases, maintaining backwards compatibility for existing programs. From this post: https://blogs.msdn.microsoft.com/vcblog/2014/06/10/the-great-c-runtime-crt-refactoring/ https://blogs.msdn.microsoft.com/vcblog/2014/06/10/the-great...
    - yuhong 10y ago
      Outdated article I think
jongalloway2 10y ago
The roadmap has been built around major releases, with big updates to internals and major new features, a little less than every 2 years for a while (2008, 2010, 2012, 2013, 2015). But, there have been pretty substantial updates about every 4 months since about 2012 (see https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#2013 https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#2013 and https://www.visualstudio.com/vs/release-notes/ https://www.visualstudio.com/vs/release-notes/). There's a balance between the stability and maintainability big enterprises often want and the feature updates developers (esp. in web and other fast moving segments) want. These updates usually include a lot of new features, pulled in as new VSIX extensions, updates to frameworks, etc., that can add a lot without blocking big corps by significantly changing the core (functionality or user experience). For example, here's the release notes on VS 2013.3: https://support.microsoft.com/en-us/kb/2933779 https://support.microsoft.com/en-us/kb/2933779 - there's a ton of stuff, especially when you consider that all the sub-frameworks (e.g. ASP.NET Web API new release) require tooling updates and testing. As a dev, I want new and shiny ASAP, and VS Code is definitely nice from that point of view. But from the VS point of view, I think the 4 month update cycle has been pretty fast. Disclaimer: Microsoft employee, Nazgûl
- dvcc 10y ago
  The four month cycle isn't bad unless you are doing anything with JavaScript. There it seems like the four-month cycle slowly begins to pile up, and it makes the already impossible task of keeping up with the js-world even harder. Thinking about it, if it weren't for JavaScript/JSX, I would be perfectly happy with the longer release cycle.
  - jongalloway2 10y ago
    I'm with you there. For JS/JSX dev, I'm assuming you know about Mads Kristensen's Web Extension Pack (https://visualstudiogallery.msdn.microsoft.com/f3b504c6-0095-42f1-a989-51d5fc2a8459 https://visualstudiogallery.msdn.microsoft.com/f3b504c6-0095...) and Node Tools for Visual Studio (https://www.visualstudio.com/vs/node-js/ https://www.visualstudio.com/vs/node-js/), right?

by dvcc 10y ago

platz 10y ago

enterprise does not like the rolling-release model.

vvanders 10y ago
They've been doing it for VS Code which is now my goto editor for anything not C++ or Java.
yuhong 10y ago
Not to mention each new release of Visual C++ for example require a new CRT etc with different file names.
- petters 10y ago
  I think they talked about this some time ago and that they were (slowly) moving away from new CRTs all the time.
- anonymfus 10y ago
  >Starting with Visual Studio “14,” we will stop releasing new versions of the CRT with each release of Visual Studio. Whereas before we would have released msvcr140.dll in this forthcoming release, then msvcr150.dll in the next release, we will instead release one new CRT in Visual Studio “14” then update that version in-place in subsequent releases, maintaining backwards compatibility for existing programs. From this post: https://blogs.msdn.microsoft.com/vcblog/2014/06/10/the-great-c-runtime-crt-refactoring/ https://blogs.msdn.microsoft.com/vcblog/2014/06/10/the-great...
  - yuhong 10y ago
    Outdated article I think

jongalloway2 10y ago

The roadmap has been built around major releases, with big updates to internals and major new features, a little less than every 2 years for a while (2008, 2010, 2012, 2013, 2015). But, there have been pretty substantial updates about every 4 months since about 2012 (see https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#2013 https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#2013 and https://www.visualstudio.com/vs/release-notes/ https://www.visualstudio.com/vs/release-notes/). There's a balance between the stability and maintainability big enterprises often want and the feature updates developers (esp. in web and other fast moving segments) want. These updates usually include a lot of new features, pulled in as new VSIX extensions, updates to frameworks, etc., that can add a lot without blocking big corps by significantly changing the core (functionality or user experience). For example, here's the release notes on VS 2013.3: https://support.microsoft.com/en-us/kb/2933779 https://support.microsoft.com/en-us/kb/2933779 - there's a ton of stuff, especially when you consider that all the sub-frameworks (e.g. ASP.NET Web API new release) require tooling updates and testing. As a dev, I want new and shiny ASAP, and VS Code is definitely nice from that point of view. But from the VS point of view, I think the 4 month update cycle has been pretty fast. Disclaimer: Microsoft employee, Nazgûl

dvcc 10y ago
The four month cycle isn't bad unless you are doing anything with JavaScript. There it seems like the four-month cycle slowly begins to pile up, and it makes the already impossible task of keeping up with the js-world even harder. Thinking about it, if it weren't for JavaScript/JSX, I would be perfectly happy with the longer release cycle.
- jongalloway2 10y ago
  I'm with you there. For JS/JSX dev, I'm assuming you know about Mads Kristensen's Web Extension Pack (https://visualstudiogallery.msdn.microsoft.com/f3b504c6-0095-42f1-a989-51d5fc2a8459 https://visualstudiogallery.msdn.microsoft.com/f3b504c6-0095...) and Node Tools for Visual Studio (https://www.visualstudio.com/vs/node-js/ https://www.visualstudio.com/vs/node-js/), right?