Welcome to the new improved debugger -- I know it sorta makes you laugh that
5 years ago in VB6 I could do much more with the debugger. As with much
that is Microsoft, it feels good initially, but when you really start
getting serious with it, it turns into a pile of pooh.
But hey, you do have the ability to browse datasets while debugging -- this
is a nice feature, but again a feature that could have been added to VB7
many moons ago.
If this entire fiasco was to solve DLL hell, well it didn't if anyone goes
unmanaged -- which many do because there ain't enough in .NET 2.0 for
serious developers to stay managed. I rarely hit DLL hell when developing
in VB6 -- is was much more of a one off type of event certainly NOT worthy
of dumping a migration path and starting over from scratch.
Again, why could they NOT continue with a normal migration path?
Rob
"rogsonl" <ro*****@discussions.microsoft.com> wrote in message
news:66**********************************@microsof t.com...
The latest versoin of Microsoft Visual Studio 2005 (Version 8.0.50727.42
RTM.050727-4200 Microsoft .NET Framework Version 2.0.50727) crashes very
often in debug.
1. If you modify a case statement and you stop the run after the change
but
before running, the system crashes.
2. Add a new class and stop the run and the system crashes.
During debug, in the new system, you can add and delete code. You might
expect this to work, I'll add additional areas where the system crashes
during debug.
I am currently doing XML work, but I believe this is not related.
Help!!!
Leon
PS. Is this related to the fact I cannot edit my macros? This is also very
limiting.
