VS.NET Woes...
This medium sized project within VS.NET 2k3 (1 solution, 22 projects) is the direct cause of my recent headaches. It seems that once the solution size exceeds about 15 projects VS.NET just decides to degrade in debugging performance and build success rate.
These days I get the infamous (at least in my mind) error "A failure occurred while attempting to start the compilation.". I wish it would be more descriptive. Time to recycle...
The other error I see allot these days is the IDE locking a specific project's DLL for writing during the build process. I have one specific project in this solution that, for some reason, whenever I make a single change too it I need to literally shut down the IDE, del *.dll;*.pdb and then load the solution back up and try again (yes Im a batch file whore and use them excessively).
I can only hope that MSBuild lives up to my expectations and solves these issues, all from within the IDE.
3 Comments
Comments have been disabled for this content.
Frans Bouma said
Some microsoft employee answered my MS Support blogs with the words that you can call PSS and they will provide a fix for you.
So perhaps you're lucky and they can create a fix for your dll locking problem. All VB.NET developers out there will be very happy to have such a fix.
Jason Alexander said
Yeah, we have the same problem(s) with VS.NET here at Match.com too, with 50+ projects in one solution. Despite the fact that doing a "Get Latest" takes forever, and VS.NET just "goes off in the weeds" with no dialogs or anything, we then have to shut down and restart VS.NET otherwise we get the DLL locking issues.
Very painful. Luckily, twice daily "Get Latest" means we don't have to deal with that headache that often.
But, still. It'll be nice when/if this is fixed.
sds said
reset the permissions on the folder