Why delay the VS2012 release, Microsoft?

The date is 1st August 2012. Developers have been wondering for weeks when the release of VS2012 and ASP.NET 4.5 will happen. Somasegar, cvp of dev div in Microsoft, has just announced that the final build version of VS2012 is complete.This means the product is ready for release. Dot net developers all over the world are eagerly waiting for the immortal words, “it’s available to download on MSDN”. Unfortunately they haven’t come. Instead, the download will not show up for another 14 days. This seems wasteful to me.

Tell me if I am incorrect, but I believe the delay is that the product has gone to tool vendors to make sure that their tools / plugins will work with the application. This to me seems a very strange thing to do. This product has technically been in the making for 18 months (since the release of VS2010) so giving it to vendors in the final 2 weeks is crazy. What will happen if the vendors report it doesn’t work with their tools? Would Microsoft stop a release for this considering it is so baked into the windows 8 release? I don’t think there is any possibility of that happening at all. Therefore why the delay? I understand that 3rd party vendors are customers that Microsoft have to satisfy, but technically so are we – the users of the product.

My ethos on software delivery is ship early, ship often. I hate when a feature is complete that it has to wait around for 2 weeks before release. Get the product out there, start gathering feedback and get planning to deliver more value to that customer. I understand that VS2012 is not easy to release often. Its a rather large download and there are pricing models around it. But changing the shape of the product to delivery in small chunks that are updatable more often would allow the product to get shaped by its user base. Faster feedback means delivering more customer value. It seems that other departments within Microsoft are now following this model (MVC team, EF team and Nuget team). Delivering like this is becoming more popular (and hopefully will become the standard). Its time to embrace this ethos Microsoft. Its certainly how I would be looking at things in the future if I were the product lead developer.

$0.02

Comments (5) -

Geir-Tore Lindsve
Geir-Tore Lindsve
8/9/2012 9:59:49 AM #

I really doubt that this is the case. One of the major 3rd party tool vendor has already shipped their version with support for VS2012, specifically JetBrains with ReSharper.

I think it's more likely that it is going through a QA period where they make sure that content for MSDN, documentation, commercial processes and other activities are finalized.

$0.02

stack72
stack72
8/9/2012 10:59:13 PM #

If they are going through a QA phase, then IMO it's not complete and ready for release. I still fail to see what can change in 14 days. What happens if something isn't ready - is that going to delay MSDN release?

Xavier Decoster
Xavier Decoster
8/9/2012 11:05:33 PM #

I can only guess about the reasons for this delay, but I couldn't agree more on the ship early, ship often philosophy.

Although I can see an evolution as well:
- we had more previews/betas
- we had these for a few months now (so they shipped earlier than before)
- MVC & EF (and others) are being shipped through NuGet, so we don't have to wait for these product updates until the next Service Pack changing the core Visual Studio installation files

Visual Studio surely could be even more lightweight in my opinion, but to me it seems most pieces of the puzzle are there.

Hence I'm even more wondering why the delay Smile

stack72
stack72
8/9/2012 11:09:26 PM #

I think utilising the Extension manager to be a bit more nuget-esque would allow a more lightweight IDE and for extensions to be shipped more often

This goes back to building those extensibility points I spoke to you about a while back

Paul Stovell
Paul Stovell
8/11/2012 9:24:00 PM #

They haven't had time to go through and remove "Metro" from MSDN Smile

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading

About Me

 

Web Developer. My most used framework is C# with MVC but use Webforms on occasion. Im an advocate of clean, maintainable code and am very passionate for what I do. Absolutely obsessed with Continuous Integration and how it should be used in every day development scenarios. Trying to move towards a system of Continuous Deployment
Follow Me on Twitter

Jetbrains Academy Member

 

MVB Blogger

 

Friends Of Redgate

Month List