B
Brian Victor
In further work on my "baffling unresolved token error" from yesterday,
I have moved to an approach of placing more code in the native .lib
file which is then called from the managed wrapper.
Unfortunately, I seem to be unable to debug the native .lib. It is in
the same solution as my managed code but in its own project. If I set
breakpoints in the .lib's code they are not hit and appear with the
question mark when the program is running, indicating no code match is
available. Every obvious release/debug toggle on the .lib's project is
set to debug.
Is there something I can do to enable debugging of the native code?
Thanks!
I have moved to an approach of placing more code in the native .lib
file which is then called from the managed wrapper.
Unfortunately, I seem to be unable to debug the native .lib. It is in
the same solution as my managed code but in its own project. If I set
breakpoints in the .lib's code they are not hit and appear with the
question mark when the program is running, indicating no code match is
available. Every obvious release/debug toggle on the .lib's project is
set to debug.
Is there something I can do to enable debugging of the native code?
Thanks!