Help!! I have been having all kinds of problems with VC# Express 2005 beta 2. I had been using beta 1 nearly daily for the last 4 months and now all work has come to a complete halt.
*) Editing any form and C# beta 2 nearly always crashes within a few clicks.
*) Starting one of projects a "Cannot dispaly DesignView" error came up from which there was no recovery.
*) I've gotten "possible memory corruption" error when exiting my program in beta 2. I never got that error under beta 1 and I'm using 100% managed code. How do you corrupt memory from 100% managed code I'm not calling into an Win32 or doing anything strange.
*) I get exceptions in the debugger, the exception inspector shows info. If I click "view details" then "ok" then click "view details" again all the details are gone.
*) beta 2 will not read data serialized by beta 1
This is really frustrating. I've been working hard on a project (http://tanjunka.com) for the last 4 months and now all work has come to stop with apparently no way to go forward.
Is there any way I can re-download VC# Express beta 1 I'd be happy to go back until beta 3. I made the assumption that my users would not be able to download the .net 2.0 beta 1 runtime soon so I thought I needed to switch to beta 2 but with it so unstable and broken everywhere, short of MS helping me work through the issues and find the bugs (mine or beta 2's) I'd really like to go back to beta 1.

Can I re-download beta 1? Beta 2 is extremely buggy for me.
aquaseal
Very sorry to hear you are having all these problems.
Unfortunately, we can't continue to support Beta1 installations anymore, since we are trying to use Beta2 to identify problems like the ones you are seeing so that we can fix them before we release the final products. To help us with this, any more information about your project and exactly how and when you are seeing errors would be enormously helpful.
If you could open bugs for each of these unique problems at http://labs.msdn.microsoft.com/productfeedback/ with as much information as possible, we will look at these are try to provide workarounds and make sure the problems are fixed in the final release.
Thanks,
Luke Hoban
Visual C# IDE Program Manager