G
Guest
Hi,
The company I work for have a project that has been developed in VC6 for
some time and now and have just moved it to work with our recently installed
Visual C++ .Net (VC7).
We are currently experiencing issues with the speed of the VC7 debugger
compared to debugging in VC6. We know it is the debugger as the debug and
release versions work as quick outside of Visual Studio as they did in vc6.
We believe it is to do with Trace functions, which we have changed to use
traceAppMsg etc and this has helped significantly. However this app throws
exceptions all the time when running rules (by design) and it is the MFC
tracing that is slowing it all down.
Various optimisation settings have been attempted but we have not yet been
able to speed it up to be anywhere near as fast as it used to run in VC6
debugger.
I wonder whether anyone could shed any light on our problems and suggest how
we can get VC7 to debug as quickly as VC6 used to?
Thanks in advance
The company I work for have a project that has been developed in VC6 for
some time and now and have just moved it to work with our recently installed
Visual C++ .Net (VC7).
We are currently experiencing issues with the speed of the VC7 debugger
compared to debugging in VC6. We know it is the debugger as the debug and
release versions work as quick outside of Visual Studio as they did in vc6.
We believe it is to do with Trace functions, which we have changed to use
traceAppMsg etc and this has helped significantly. However this app throws
exceptions all the time when running rules (by design) and it is the MFC
tracing that is slowing it all down.
Various optimisation settings have been attempted but we have not yet been
able to speed it up to be anywhere near as fast as it used to run in VC6
debugger.
I wonder whether anyone could shed any light on our problems and suggest how
we can get VC7 to debug as quickly as VC6 used to?
Thanks in advance