InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

VS.NET 2003 SP1 Released

Posted by Marcie Jones on Aug 18, 2006

Sections
Development
Topics
Artifacts & Tools ,
Visual Studio ,
.NET ,
Tools ,
IDE ,
Microsoft ,
Programming ,
Agile ,
Companies
The long-awaited Service Pack 1 for Visual Studio.NET 2003 was released earlier this week.  SP1 fixes over 400 VS.NET 2003 bugs , including the top 50% of VS.NET crashes reported using through the Windows Error Reporting Service (via Soma).  Now we know where that information went, and that it was put to good use!  Most notable from the fix list are several IntelliSense fixes, plus resolutions to assorted IDE crashes.  Hopefully a service pack for Visual Studio 2005 will be delivered before 2008.

Note:  at a hefty 156.3 MB for SP1, some users are reporting long download and install times.
  • This article is part of a featured topic series on Agile
interop by Cameron Purdy Posted
Re: interop by Diego Visentin Posted
Re: interop by Sean Alexander Posted
  1. Back to top

    interop

    by Cameron Purdy

    It would be nice if we didn't need both VS 2003 and VS 2005. Microsoft doesn't get that people could (shock! horror!) have both 1.1 and 2.0 projects, or (shock! horror!) the same project deploying to both.

    With Eclipse or IDEA, I can specify a JDK per project, etc., and neither of those is the "owner" or "author" of Java. If they can do it, why can't Microsoft, which owns the standard and the API and the implementation and the tools?

    Peace.

  2. Back to top

    Re: interop

    by Diego Visentin

    In fact with SharpDevelop you can choose the release of .NET framework at project level:
    community.sharpdevelop.net/blogs/mattward/artic...

    Ciao, Diego

  3. Back to top

    Re: interop

    by Sean Alexander

    Actually Cameron, if you are interested in that you should look at MSBee. It allows you to develop .NET 1.1 applications inside of VS2005 thus allowing you to walk away from VS 2003. And going forward I think you will see more of that as they have pushed the generation of the actual MSIL outside of VS thus allowing VS to be somewhat independent of versions of .NET. The release of .NET 3 sometime next year will be the true test if they have figured it all out or not, but for now do a search for MSBee that should get you want you want.

    Hope that helps

    Sean Alexander