I've never seen this one before. This certainly sounds like a bug in the Visual Studio .NET. What you'll need to do is get Visual Studio .NET completely removed from your system. The Knowledge Base article at http://support.microsoft.com/?id=824642 shows you exactly how to remove all traces of Visual Studio .NET so you can try the installation again.
Related Q&A from John Robbins
What is a JAD session? This term is referred to often in job postings and seems like some kind of brainstorm you carry out with a client to define IT...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.