Visual Studio .NET 2003 Service Pack 1 Release Date
Visual Studio .NET 2003 Service Pack 1 is just about ready. Very near the end of our sign off testing a bug was found in the VC Runtime that we felt important to get into the Service Pack for customers. This change resulted in a new round of testing and has moved the release date to August 15, 2006.
Almost there!
Lee Coward
Program Manager
Visual Studio .NET 2003 SP1
Comments
Anonymous
July 17, 2006
PingBack from http://microsoft.wagalulu.com/2006/07/17/visual-studio-net-2003-service-pack-1-release-date/Anonymous
July 17, 2006
I wasn't even aware that there would be a service pack for 2003, I assumed it was 2005.
Here is more information that I found:
http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs03/default.aspx
Bug fixes for that version are gladly accepted.Anonymous
July 17, 2006
Ajourd'hui on ne parle plus que de C# 2.0, .Net 3.0, WPF, WCF, ...., et on oubli Visual Studio 2003,...Anonymous
July 17, 2006
What about 2005 SP1?Anonymous
July 17, 2006
But when is VS2005 SP1?Anonymous
July 17, 2006
I haven't been able to tell if VS 2003 SP1 will include fixes to the .NET 1.1 framework, or will there be a seperate .NET 1.1 SP2?Anonymous
July 17, 2006
Eeer, dude, can you ask your colleague (the PM for VS2005 SP1, if he exists) if we should still hope for SP1 for VS2005?
Thanks,
StoyanAnonymous
July 18, 2006
Ditton on the SP1 for VS2005 request. At least Vs.net 2003 was relatively stable on release. Vs.net 2005 is BETAWARE with a code editor that is so slow that it's virtually unusuable unless you turn off all of the functionality and use it like notepad (I often go and write code in notepad because the code editor is so slow in vs 2005.)
Fix the buggy product that is your current version first, worry about Vs.net 2003 later.Anonymous
July 18, 2006
The performance of the slug that is VS 2005 is enough to explain the Vista delays...
Of course, I doubt people in the OS group are using this beast (Why should they? There's almost no .Net at core of Vista), and if they are, they don't need to wait on hold with PS for an hour for each stinking hotfix.
I can't even begin to count how many hours I've wasted waiting for this POS to catch up with my keystrokes.Anonymous
July 18, 2006
PingBack from http://microsoft.wagalulu.com/2006/07/18/vsnet-2003-sp1-release-date/Anonymous
July 18, 2006
In related news, Microsoft has announced SP1 for Windows 3.1 will be released Q1 2007.Anonymous
July 18, 2006
VS 2005 has tons more bugs than VS 2004. Come on, people. Most of these bugs in VS 2005 are obvious, in your face, annoying ones..... Get Real! Fix VS 2005 First for crying out loud!!!!Anonymous
July 18, 2006
So at this rate, we can expect SP1 for VS2k5 in 2008. What a joke.Anonymous
July 18, 2006
Anyone from Microsoft care to comment? The silence is deafening...Anonymous
July 18, 2006
Would please look around and see how many Cu$tomer$ are asking for the VS 2005 SP 1,
You keep telling us "Migrate to the New VS.NET 2005" and you know it's full of bugs, Well stop working on Visaual Studio 2008 "orcas or whatever!!!" and finish the 2005 version - it's NOT FINISHED YETAnonymous
July 18, 2006
We're still waiting for a release of VS 2005 SP1 before we even consider moving all our projects to .net 2.
VS 2003 SP1 is (will be) very welcome!Anonymous
July 19, 2006
ditto on all the negative comments on VS2005.
Sorry, but there isn't really that much positive to say about VS03 or VS05 for that matter.Anonymous
July 19, 2006
Oh my, what a lot of negative comments! From me and the vast majority of programmers who don't upgrade immediately to the latest compiler, THANK YOU for a much overdue SP1 for VS.NET 2003. We are looking forward to it.Anonymous
July 19, 2006
At the risk of repeating many other commenters' thoughts: Please make a service pack for VS 2005 a priority...
The bugs in VS 2005 are horrendous, and in my experience as a consultant, customers are holding off on migrating to .NET 2.0 (which is a beautiful platform, IMHO) because of the poor tool support.
I experience constant crashes of the VB.NET background compiler myself (which were reported early on in the beta process; but never fixed) which actually made me switch to C#!
I think that releasing a first service pack for a product nearly 3 years after its release date is a joke. It's not what customers need.Anonymous
July 19, 2006
Nate, I think it's important to note that upgrading to the latest version of Visual Studio is not optional in the way that, say, upgrading Office is. If I could run 2003 I would, but the idiotic choice to marry the IDE to the framework version prevents me from doing so.
.Net 1.0 -> VS 2002
.Net 1.1 -> VS 2003
.Net 2.0 -> VS 2005
Can you imagine the outcry if you had to run parallel versions of Word, Excel, and PowerPoint to ensure compatability through the last 4 versions?
I don't appreciate the implication that I and the other who are using 2005 are part of a misguided minority who made a stupid decision in upgrading. In many cases, the issues in 2005 were identified in the beta cycle, not fixed, and in some cases identified as resolved. It's been 9 months since this product was released. How long am I supposed to wait? Want Atlas, themes, generics, master pages, partial classes, etc.? You're basically SOL without 2005.
I am also not willing to lower my expectations to the point where I will blame myself when an expensive piece of software performs poorly. We should all expect better IDE maintenance support than we are receiving.Anonymous
July 20, 2006
VS 2005 bugs have been known from the beginning, which is why so many of us developers stuck with VS 2003.
I would rather work with 1.1 in a more stable VS 2003 environment than 2.0 in an unreliable VS 2005 environment.
I'm looking forward to the sp1 for VS 2003. Mabye I'll upgrade to 2005 after everyone else has done all the testing and the new sp1 for VS 2005 is out.Anonymous
July 20, 2006
It's exactly this kind of attitude that is responsible for it taking over 3 years for a service pack to arrive. You get what you are willing to tolerate.
Unfortunately, the "wait for SP1" attitude doesn't work so well when service packs don't arrive until after the next version ships. In case you haven't noticed, .Net 1.1 doesn't have a lot of momentum anymore.Anonymous
July 21, 2006
I hoped it was a spelling error when I followed the link to this post, hoping to finally get a more usuable .NET 2.0 IDE.
I really can't understand why it takes ages to release bugfixes for the development products - after all, we know better than any other of MS' customers that SW tends to have bugs (if you're not MS and you want to stay on the market, maybe not as many as the horrible VS2005, but that's another story). I'd say there are dozens of severe bugs that are probably already fixed (or could be fixed easily) but obviously nobody at MS bothers to release anything. If I really had a choice when it comes to the IDE, I'd be gone for good :-(Anonymous
July 21, 2006
To all the people hollering for bug fixes to VS 2005 ...
Some of us haven't moved on to VS 2005 because of the bugs in it. So, it would be nice to get the update for VS 2003 so we can keep on working until the VS 2005 product is stable enough to use for production work.
VS 2007,8, or 9 should be out by then.Anonymous
July 21, 2006
PingBack from http://bryanandnoel.hintonweb.com/blog/1969/12/31/update-on-the-upcoming-visual-studio-2003-sp1-release/Anonymous
July 21, 2006
These are circular arguments. 2005 isn't stable because it hasn't had a service pack. You want to wait until it's stable to move to it, i.e. when it gets a service pack. By your reasoning, you need a 2003 service pack because 2005 doesn't have one.
And what exactly are the issues that are causing you so much pain on 2003? They can't be that many, otherwise you wouldn't have moved from 2002. Having spent several years with 2003, I can say that there's no way that it needs a service pack anywhere as much as 2005.Anonymous
July 21, 2006
I can only presume that a subset of the VS2005 code found its way into SQL Management Studio.
How do you manage to get that app to run so S..L..O...W...L...YAnonymous
July 21, 2006
Why o why did I ever leave the great (and free) world of Java? Oh what a let down it has been.Anonymous
July 22, 2006
The comment has been removedAnonymous
July 22, 2006
I could not find any URL where I can report bugs in VS 2003. I tried using Visual Studio .NET 2003 on Windows Vista x64. It just can not be used if the "properties window" is open. It keeps on throwing modal error dialogs with the following error message:
<ErrorMessage>
The following exception has occurred:
ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: '-1' is not a valid value for 'index'
</ErrorMessage>
VS2005 express editions work great. VS 2003 works great on Windows XP Pro x64, and it should have worked on Vista... The first and only issue I encountered with any application in Windows Vista is in Microsoft's own product.
My fix:
Removed the devenv.exe.manifest file to see if the vista common controls are causing the issue. I tried switching common controls version - We actually only have one version and VS 2003 can not be used with it...Anonymous
July 23, 2006
For all the complaints I'm reading here about VS2005, I haven't experienced anything bad with it (apart from dexplore crashing on start). I've been using it since launch, on machines new and old running WinXP.
All the same, even I am impatiently awaiting SP1 for 2005. It's nice and all to continue supporting older versions of products when newer versions are out, but the priority should be on the latest version, first.
So, are we going to see it before the year is out?Anonymous
July 23, 2006
Couldn't agree more with the comments about VS 2005. It is simply put the most bug ridden piece of software I have ever used. I have to suffer it on a daily basis and see the error "Microsoft Visual Basic compiler has encoutered an error and needs to close" or "Visual Studio has encountered an error and needs to close" on a hourly basis. I have last count of the amount of code I have had to write and then re-write as VS 2005 kindly loses it all when it crashes. Microsoft, please listen you your developers. We are happ with VS 2003 but desperately want you to resovle the issues in 2005 AS SOON AS POSSIBLE. Or would you prefer people to switch to Java?Anonymous
July 23, 2006
The comment has been removedAnonymous
July 23, 2006
The comment has been removedAnonymous
July 24, 2006
I have to side with Chris above and say that I haven't experienced a ton of problems with VS2005 and VB.NET 2.0 either. I did encounter the dreaded H8013141e error described in KB915038, but I ended up calling MS Dev Support, waited about 20 minutes, had a hotfix sent within the hour, and everything is working fine now. I do agree that the editor seems pretty slow though.Anonymous
July 24, 2006
Coming from an era when the notion of hand crafting your own IDE was considered practical … it is remarkable to witness the seething complaints directed at VS2005. Expecting Microsoft to be somehow different from the majority of large monolithic capital driven organizations is silly. Add to the mix the fact that a lot of fresh blood is driving the organization now and you have product releases like VS2005.
Keeping shareholders and the market happy has nothing to do with quality and long-term vision. One could argue that rapid obsolescence is in fact the driving force behind much of the success enjoyed by our major technology corporations. This sort of mindset does conflict with situations where product development has to be evolutionary rather then revolutionary.
Switching from VS6 to VS2003 was a BIG change. It would have been easy to question the wisdom of some of the GUI enhancements, but you have to give the young folks a chance to have their kick at the can (speculating). The untimely release of VS2005 is (speculating) mostly about positioning the Microsoft tool chain against the likes of IBM Rational App Developer. IBM’s product may be one of the least used IDE’s, but it commands the attention of those that shell out the biggest dollars for an integrated solution and they also happen to be the folks that are working on some of the biggest money makers. So marketing forces, capitalist inclinations, and the perception of threat drive Microsoft to release early. CNN often gets the story wrong, but they’re always first with the story. Wait a couple hours and you’ll get 100% confirmation, but then you’ll be two plus hours behind real time.
Using Microsoft products is still the shortest path to monetary success for your typical generalist software developer. As long as Microsoft keeps looking over its collective shoulder in panic, that won’t change.
Complain loudly, complain often, but be positive too. The folks reading these blogs are riding the same merry-go-round.Anonymous
July 24, 2006
The comment has been removedAnonymous
July 24, 2006
"Visual Studio 2005 Service Pack 1 ... is currently targeted for final release in Q3 of 2006."
http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs05/default.aspxAnonymous
July 24, 2006
The comment has been removedAnonymous
July 24, 2006
The comment has been removedAnonymous
July 24, 2006
With what's already been said, all I can do is add my $.02. And is that a we need AN IMMEDIATE SERVICE PACK FOR VS 2005.Anonymous
July 25, 2006
I still don't know what all this chatter about VS 2005 being buggy is. It runs fast and never crashes for me. <Shrug>
Very odd to be releasing the first service pack for VS.NET 2003 a year after 2005 though.Anonymous
July 25, 2006
what about this doing? tell me....
thank u!Anonymous
July 26, 2006
I'd like to first thank you for giving us this information. I have been patiently waiting SP1 for VS2003 and appreciate the post.
We've now used VS2005 extensively, developing ASP.NET, PocketPC and Windows applications in it, all from within the same solution, integrating unmanaged C++ and C# code, and I can say that it is lightyears ahead of VS2003. The debugging facilities in particular are so powerful. An excellent product! However I must agree with the sentiments of some of the postings here: it was released a little early and deserved another beta round to iron out the bugs. I only hope that this is appreciated inside MS and that future released will be run through enough beta cycles. Vista included. Customers prefer solid products and don't care if it takes another year to arrive. Obviously the shareholders want results, however from experience , you will spend the time fixing it whether it's on the street or not, and typically it actually costs more to fix things once they're released!
I do also think that MS should update the product support pages that come up if you search for VS2003 SP1, since the information is clearly out of date. Thanks for your information though!Anonymous
July 28, 2006
The comment has been removedAnonymous
August 02, 2006
I think most of the issues currently seem to be with the Visual Basic compiler (KB915038 is one that stands out) .. It would make sense for those of us who constantly have a bad time in VS2005 (VB Devs), while others seem to have little problem (C# Devs). It seems that the people who say they have no problem are using C#.Anonymous
August 03, 2006
How come as VS 2003 SP1 is due out in less than 2 weeks, but the servicing page still docent give a detailed list of fixes?
Also wheres the list of bug fixs for 2005 SP1 as the IDE & compiler bugs in 2005 cause major issues daily.
Could MS also update the 2005 SP1 page with a revised release date (is it still on schedule?).Anonymous
August 03, 2006
How come as VS 2003 SP1 is due out in less than 2 weeks, but the servicing page still docent give a detailed list of fixes?
Also wheres the list of bug fixs for 2005 SP1 as the IDE & compiler bugs in 2005 cause major issues daily.
Could MS also update the 2005 SP1 page with a revised release date (is it still on schedule?).Anonymous
August 08, 2006
It took 3 years for 2003 Service pack , so 2008 will see the service pack 2005. Hold on guys!!Anonymous
August 14, 2006
So is the SP1 still on track for release for tomorrow Aug 15?
Or is it going to be delayed again?Anonymous
August 14, 2006
It's august 15 10:10 , I can't find this service pack anywhere??Anonymous
August 14, 2006
The comment has been removedAnonymous
August 15, 2006
The comment has been removedAnonymous
August 15, 2006
This reminds me of Obsidian Entertainment's patch for Knights of the Old Republic 2. Can't remember how many months the "Patch coming soon" message was displayed. Granted, it wasn't 3+ years.Anonymous
August 15, 2006
Ok, it's August 15th, 2006 at 4:19PM EST and I can't find the Service Pack for VS 2003? Please don't tell me it's delayed yet again. If it is, you are a bunch of liars!!!!!Anonymous
August 15, 2006
Anyone seen the Service Pack Yet?Anonymous
August 15, 2006
I havent yet ...Anonymous
August 15, 2006
Hey MS, where is the update on the update?Anonymous
August 15, 2006
OK,that's so called microsoft style..........Anonymous
August 15, 2006
2 years ago I completely abandoned Delphi because of its uncertain future.
As of this writing, I'm downloading an eval of Delphi 2006. Microsoft looks more fragile than ever this time.
If it wasnt for the tight integration of MSs products, I'd be working with Java now.Anonymous
August 15, 2006
No seriously now, where's the service pack? The delay up to now has been ludicrous... wasn't it supposed to be here over a year ago?! Now we finally have a date, the date has arrived, and the silence from MS is absolutely deafening.
Please abandon this idiotic service pack campaign and make all the hotfixes available for download.Anonymous
August 15, 2006
its now the 16th (1:15 AM) in my time zone and still no sign ...Anonymous
August 15, 2006
Mr. Lee Coward, what happened? Was the announcement premature? Was it intended to placate us; keep us on the hook? Have the interests of VS2003 been overtaken by those of VS2005? Are Microsoft resources stretched too thin? Or are these delays the outwardly expression of internal issues related to competency and professionalism?
Who is responsible and who is accountable? Do these folks wear the same hats, perhaps too many hats?
Looks like the “blog thing” is about to go away now that it’s becoming an embarrassment.
Where has the maturity of this company gone? Have all those folks retired?Anonymous
August 15, 2006
now 10:20 16 Aug (London) , still no service pack still no news!! I watched a netcast the other day with some doofus from MS saying, that although they publish a release date, it doesn't necessarily mean they will stick to that date, Now tell me what is the use of that??Anonymous
August 15, 2006
now 10:20 16 Aug (London) , still no service pack still no news!! I watched a netcast the other day with some doofus from MS saying, that although they publish a release date, it doesn't necessarily mean they will stick to that date, Now tell me what is the use of that?? We give our customers a release date for thier product and we stick to it, our customers generally have a project plan they would like to follow, they generally back this up with paying us on the date we ask for payment! Generally our customers pay for what they get, if we don't deliver we don't get paid. We have to ensure our product is stable and reliable.Anonymous
August 15, 2006
I've downloaded it... there is still a lack of release notes indicating a list of fixes... but I'll wait for that untill running the EXE...Anonymous
August 15, 2006
Where is the download?Anonymous
August 16, 2006
I think the dude means .Net Framework 1.1 cos there is no download for vs.net 2003 yet !!!Anonymous
August 16, 2006
The download is available here:
http://msdn.microsoft.com/downloads/
In the "Most recent developer downloads"
I have no idea why it is not linked from anywhere pertinent.Anonymous
August 16, 2006
DirectLink:
http://www.microsoft.com/downloads/details.aspx?FamilyID=69D2219F-CE82-46A5-8AEC-072BD4BB955E&displaylang=en#RelatedLinksAnonymous
August 16, 2006
unbelievable the amount of useless comments in this posts.Anonymous
August 16, 2006
If you originally installed VS2003 from a network share, and it does not exist anymore... you can't install the service pack, even with the install CD. You have to recreate a network share.Anonymous
August 16, 2006
Sigh a non-working link for the list of changes. What a comedy of errors.
http://support.microsoft.com/default.aspx?scid=kb;en-us;918007.Anonymous
August 16, 2006
Can't say I'm impressed so far. Have just recompiled our numerical library with the new service pack and get a bunch of numerical errors in our numerical tests which are ~3 times slower to run following the upgrade. Anyone esle seeing anything like this?Anonymous
August 16, 2006
Yippeee I got it thanks guysAnonymous
August 16, 2006
The comment has been removedAnonymous
August 17, 2006
To Jason,
I figured out that our application (debug or release version) seems to run ~3-4 times slower when it is launched with the debugger. Without the debugger, the speed is back to the normal like it was in VS2003 without SP1.
We might have an issue here.Anonymous
August 17, 2006
To Marc W.
I couldn't repeat the slowness issue I saw first time round. I wasn't running the compiled code through the debugger at all. The test failures I saw were due to some small differences in random number generation that caused minute differences in test results. All in all, I'm much happier today than I was initially yesterday.Anonymous
August 17, 2006
To Jason,
I've installed the Service Pack on two separate computers and the slowness issue occurs only one of them. Tomorrow I will try to clean up the disk and rebuild the whole project.
Anyway, thank you for your feedback. I guess the problem is on my side.Anonymous
May 29, 2009
PingBack from http://paidsurveyshub.info/story.php?title=dde-team-blog-visual-studio-net-2003-service-pack-1-release-dateAnonymous
May 31, 2009
PingBack from http://woodtvstand.info/story.php?id=1370Anonymous
June 08, 2009
PingBack from http://jointpainreliefs.info/story.php?id=2623Anonymous
June 08, 2009
PingBack from http://hairgrowthproducts.info/story.php?id=151Anonymous
June 15, 2009
PingBack from http://debtsolutionsnow.info/story.php?id=4182Anonymous
June 16, 2009
PingBack from http://topalternativedating.info/story.php?id=3535