The C++.NET debugger version 2003 has a VERY SERIOUS
flaw. I have attempted to rebuild this same application
almost a dozen times to get around this bug. I will be
forced to scrap the .NET stuff soon and go back to VC6 or
Borland... Basically, without warning, the debugger loses
track of where source code is for virtual functions. My
attempts to clean the build and delete the ncb file have
had NO EFFECT.
I am using windows forms to produce a MYSQL C-API based
console for a production service. Timer and Controls
originated events occur to call unmanaged C++ code. These
member functions (like most C++ applications that utilize
the language), use virtual functions. I can build 60% of
my app, stepping through it each time to ensure that I can
still debug all of my code. This will become particularly
crucial as my implementations of each derived class start
to diverge from one another. Just as I am starting to
fill stuff out - BOOM - I lose the ability to step through
my code indefinitely and without warning.
PLEASE HELP! I have already posted twice. This newsgroup
has been billed as an alternative to the support offered
by my Universal Subscription. However, when you get no
reply all week, the value of that subscription comes into
question.
Sincerely,
-James A. Renton
