Hi
I have a problem with Visual Studio 2002. Now and again, when i start
running a VB.NET application, after the build of the exe is complete,
it takes a minute or more to actually run the exe (2min 20s on the
last count).
Also, once the exe has started i notice that the visual studio is not
in 'debug' mode, it is back in editor mode. Its as if i ran the exe
outside of VS2002.
I created a test application to make sure it wasnt something in my
code where i originally had the problem, this application has one
screen with one button on, thats it!
If i select Debug / Processes in VS2002, my application is listed in
the bottom section and if i select it and select break, it suddenly
springs VS 2002 to life and it recognises that it is attached (or
attaches at that point) to the running exe.
I get this problem whether i have the build configuration set to Debug
or Release and as i said at the start, it doesnt happen all of the
time.
I cannot spot a pattern with this problem and it is really annoying. I
am currently on .NET framework 1.0.3705.
Does anyone know how to solve this, is it an error with .NET framework
1.0 or the visual studio tools for 2002? Its not easy to upgrade as we
have 1.0 framework installed on all clients via a global instal so i
would like to keep with 1.0 if possible. It may be ok to install the
SP's if i have to.
I have admin rights to my PC and the Machine Debug Manager is running.
Thanks
Malcolm
Malcolm - 19 Nov 2004 09:00 GMT
In case anyone else is having this problem, I upgraded to .NET
Framework 1.0 SP3 and dont seem to be having the problem any more.
> Hi
>
[quoted text clipped - 31 lines]
>
> Malcolm