I have been tearing my hair out recently due to the problem described in
KB822960. If you haven't experienced it, count yourself very lucky.
Furthermore, Microsoft's online support doesn't like my product ID, and I
really don't want to speak to a random Indian/Asian who I can't understand.

Is there anything I can do apart from twiddling my thumbs until about April
next year for the hotfix to be released as part of the Service Pack?

"Pixa" <Pixa (AT) discussions (DOT) microsoft.com> wrote

If you have the retail Academic Edition, you have two free support
incidents. Your other option is to post in the public newsgroups.
BTW, do you have the article number correct? A Search of MSDN and Google
Groups for "822960" fails to turn up anything except your post here.

Sorry, got the ID wrong - was kb822690

"Pixa" <Pixa (AT) discussions (DOT) microsoft.com> wrote

OK, seems pretty simple to me. You need the hotfix, as you say "I've been
tearing my hair out recently ".
The only way to get a hotfix is to call the closest support number offered
in the link on the KB 822690 page.
As nobody can tell you if or when a service pack might be issued for VS.NET
2003, the only sure way is to use the phone and get the hotfix.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.