I've had it completely with Microsoft's Hotfix policy for VS.NET 2002/3. This is the most lowest form of support you possibly can get. What's the problem? Well, the (in)famous 'Cannot copy assembly <Referenced Assembly> to file <Current Project Output Folder>\bin\Debug\Release\<Referenced Assembly>.dll. The process cannot access the file because it is being used by another process' error.
The thing is, Microsoft already fixed it in October 16th, 2004. That's right, almost 9 months ago. Please see the details of this crappy bug and its fix here:
My problem is that I have to support my customers who run into this error sometimes with our assemblies. They have it referenced in 1 ASP.NET application but still get this error once in a while. I'm pretty fed up with telling my customers there is a fix but they can't receive it from me because I'm not allowed to distribute the fix. That's right, I have it right here on my harddrive.
So, I'm pretty close to distributing the fix to my customers so they're happy and this stupid bug won't happen to them. But it's better if Microsoft does this. The fix is already available, all they have to do is to make it a public download. Perhaps if all ISV's who sell / distribute signed assemblies which are used in ASP.NET applications (as that's the problem, the assemblies can't be signed apparently) and which aren't in the GAC push MS to release this hotfix, we ALL are better of.
After all, it's been 9 months since the fix, for crying out loud! Microsoft support? Don't make me laugh. Take this: in Open Source land, this wouldn't have happened: either the fix was distributable, or the fix was already in the core downloadable product. Microsoft, if you want to win from Open Source so badly, start by supplying fixes to the developers who are still on your side.