G
Guest
This might be true, but overall VB .NET development time is much improved
over VB6 (Just typing VB6 makes me cringe).
I would much rather take the extra 5.5 seconds for the rare occasion I need
to use the debugger for the much improved development environment. Anyway,
I'm sure Microsoft will fix any slowness issues in future releases. At least
I will be more ready to port my app from 1.1 to 2.0 as opposed to porting
some COM object to 2.0 (which will be must more wasteful than 5.5 extra
seconds starting the debugger).
Overall, your post is quite pointless and naive. You will waste more time
developing in VB6 as opposed to VB .NET. The debugger start time should never
be a factor in your development time. I hope you don't have to start the
debugger so much that it makes that much of a difference.
Ken
over VB6 (Just typing VB6 makes me cringe).
I would much rather take the extra 5.5 seconds for the rare occasion I need
to use the debugger for the much improved development environment. Anyway,
I'm sure Microsoft will fix any slowness issues in future releases. At least
I will be more ready to port my app from 1.1 to 2.0 as opposed to porting
some COM object to 2.0 (which will be must more wasteful than 5.5 extra
seconds starting the debugger).
Overall, your post is quite pointless and naive. You will waste more time
developing in VB6 as opposed to VB .NET. The debugger start time should never
be a factor in your development time. I hope you don't have to start the
debugger so much that it makes that much of a difference.
Ken