VS IDE hangs at 100% CPU utilization when project opens

[Guest]

This has been the bane of my existence using Visual Studio 2003.

Recipe:
-Use UNC path to browse to directory on Win2003 Server with IIS.
-Double Click the project file, the IDE opens, but notice there is no redraw
in the window in the right panel.
-Wait internibably until impatience forces one to open the Task manager
-Notice that Visual Studio is not (not responding) and can be alt-tabbed to,
but also notice 100% CPU utilization.
-This is a seemingly randome problem, but often I cannot open projects for
days at at time. When this happens, we all laugh, curse Microsoft for selling
crapware to the corporate management - because the developers don't get a
say, and I move on to editing with Notepad and using the command line to
compile my assemblies.

This is the worst of all my VB IDE blues, and if it were up to me I'd get my
money back for this piece of beta-ware.

In our shop we are inadvertantly training a whole generation of programmers
who would rather flip burgers at mcdonalds than use Microsoft tools. That's
why we all donate time to OpenOffice and products like that. MS has made some
real enemies of people who've been forced to use their tools.

 

[Greg Burns]

-Use UNC path to browse to directory on Win2003 Server with IIS.

-Double Click the project file, the IDE opens, but notice there is no
redraw
in the window in the right panel.

If I recall back when I first tried to open a VS.NET proejct from a network
drive (ala my VB 6 days) I ran into all sort of .NET security issues.

I think (IMO) that it is common practice to keep your source code on your
local pc, and you use some sort of source control for your backup needs.

Greg