I think we have hit the infamous invisible wall with VB.Net.  It's still a bit early to be looking for solutions, but the solution is having more and more problems.  Vbc.exe errors, general vs.net errors, and interesting times when the IDE doesn't error, it just stops working the way you want anticipate. 

I may be a c# guy stuck in a vb.net world, but I have gotten used to some of the “features” the ide gives us for vb.net.  When they just stop working, it really does make it more difficult to code.  Plus restarting the IDE 5 times a day certainly doesn't help my productivity (isn't vb the “productive” language?  :)  I'm trying to analyze to see if I can put together patterns on when it crashes, but so far it does seem pretty random.  I started a spreadsheet this morning to try to help with that though.

I will probably do some searching this weekend (since I probably wont be checking in and out all weekend like I thought (teamsystem was only tested with 3 physical machines?!  I guess it is an early beta)).  Has anyone gone through this before?  This is a pretty big solution, but it's certainly not a 10k lb gorilla.