Dennis van der Stelt

The only way to win is to learn faster than anyone else

Community

Email Notifications

News

  • Addicted to Refactor! Pro

I read...

I Use...

Tags

Recent Posts

Archives

Blog Subscription Form

  • Email Notifications
    Go

Weblogs in distress

When you think hundreds of weblogs are going to blog about the new release of Windows Live Writer, Somasegar shares some info on Windows Vista that causes a lot of stress in the .NET blogging community. And I think they're quite right, because as Frans sums it up:

  • Visual Basic 6 runtime and IDE. Supported.
  • Visual Studio.NET 2002. Not supported
  • Visual Studio.NET 2003. Not supported
  • Visual Studio.NET 2005. Supported with SP1 (now in beta) and you've to shut down UAC, till they've fixed that after Vista ships.

That's quite ridiculous! It has been a long time since I've done something in .NET 1.1 but at Class-A we still train people in it, because of various reasons. So I do have Visual Studio 2003 installed. But installing Windows Vista makes sure, as it seems, that installing Visual Studio 2003 isn't necessary as it just won't work! How weird.

I hope someone can tell us that VS2003 actually does work, but seeing the number of comments on Somasegar's post I don't think I have to set my expectations too high.

Update : Here's a quote from Scott Guthrie on Paul Wilson's weblog:

The big technical challenge is with enabling scenarios like advanced debugging. Debuggers are incredibly invasive in a process, and so changes in how an OS handles memory layout can have big impacts on it. Vista did a lot of work in this release to tighten security and lock down process/memory usage - which is what is affecting both the VS debugger, as well as every other debugger out there. Since the VS debugger is particularly rich (multi-language, managed/native interop, COM + Jscript integration, etc) - it will need additional work to fully support all scenarios on Vista. That is also the reason we are releasing a special servicing release after VS 2005 SP1 specific to Vista - to make sure everything (and especially debugging and profiling) work in all scenarios. It is actually several man-months of work (we've had a team working on this for quite awhile). Note that the .NET 1.1 (and ASP.NET 1.1) is fully supported at runtime on Vista. VS 2003 will mostly work on Vista. What we are saying, though, is that there will be some scenarios where VS 2003 doesn't work (or work well) on Vista - hence the reason it isn't a supported scenario. Instead, we recommend using a VPC/VM image for VS 2003 development to ensure 100% compat. Hope this helps - even if the answer isn't entirely what we'd all like it to be, Scott

Technorati tags: , ,
Posted: Thu, Sep 28 2006 11:25 AM by Dennis van der Stelt | with 6 comment(s)
Filed under: ,

Comments

Alex de Groot said:

I definitelly hope Microsoft wakes up and releases a 2005 Project Model which supports 1.1. Most of the users have now both versions installed which is quite annoying and it doesn't provide more functionaly. Licenses aren't the problem as nearly everybody receives the software from their MSDN subscription. Guess we have to e-mail Scott Guthrie :).
# September 28, 2006 2:43 AM

Jan Schreuder said:

@Alex. Have a look at MSBee (http://msdn.microsoft.com/vstudio/downloads/tools/msbee/default.aspx). It allows you to develop for the .Net 1.1 framework using VS 2005.

But I simply cannot understand why VS 2003 is not supported on Vista and VB6 is?!?!?! I hope it means that they haven't tested it yet, so they don't know if it works. Rediculous!!!

# September 28, 2006 3:01 AM

Ramon Smits said:

Not supported is not the same as in that it won't run :) I've not yet read articles about that it didn't install on vista at all. But msbee is quite nice. VS2005 is also a much nicer ide then VS2003. Just combine it with msbee and tdd.net and your done.
# September 28, 2006 3:43 AM

Alex de Groot said:

MSBee isn't a solution. It's just an ugly workaround which allows you to speak with the old MSBuild. I think it's a disguisting solution. Also there are several problems with IntelliSense. And I want MS support, not some community stuff for my primary buildproces. As I can't fallback to patches, garantees, support, etc.
# September 28, 2006 3:46 AM

Dennis van der Stelt said:

Ramon, here's the story from Scott Guthrie. I'll include it in the article as well.

The big technical challenge is with enabling scenarios like advanced debugging. Debuggers are incredibly invasive in a process, and so changes in how an OS handles memory layout can have big impacts on it. Vista did a lot of work in this release to tighten security and lock down process/memory usage - which is what is affecting both the VS debugger, as well as every other debugger out there. Since the VS debugger is particularly rich (multi-language, managed/native interop, COM + Jscript integration, etc) - it will need additional work to fully support all scenarios on Vista. That is also the reason we are releasing a special servicing release after VS 2005 SP1 specific to Vista - to make sure everything (and especially debugging and profiling) work in all scenarios. It is actually several man-months of work (we've had a team working on this for quite awhile). Note that the .NET 1.1 (and ASP.NET 1.1) is fully supported at runtime on Vista. VS 2003 will mostly work on Vista. What we are saying, though, is that there will be some scenarios where VS 2003 doesn't work (or work well) on Vista - hence the reason it isn't a supported scenario. Instead, we recommend using a VPC/VM image for VS 2003 development to ensure 100% compat. Hope this helps - even if the answer isn't entirely what we'd all like it to be, Scott

# September 28, 2006 5:10 AM

Zupancic Perspective said:

# October 3, 2006 9:54 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Please add 7 and 4 and type the answer here: