Re: C++/CLI integrating third party assembly
- From: "William DePalo [MVP VC++]" <willd.no.spam@xxxxxxxx>
- Date: Fri, 22 Dec 2006 14:28:13 -0500
"kyle.schmidt" <kyleschmidt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AB717137-38B7-4951-8247-B18673EADAF7@xxxxxxxxxxxxxxxx
Is there another flag I can check that is not .NET related?
Well, you can P/Invoke IsDebuggerPresent(). That will tell you if native
debugger is attached. I should mention that I don't know much about the
managed debugging API.
Consider this just thinking out loud ...
but it may be that the third-party stuff sees debugging at a native level as
a bigger threat than at the managed level. And if it is the case that when
you debug your C++/CLI code you are debugging in "mixed" or "auto" mode
unlike the managed mode used for C#, perhaps that's a clue.
As I said, I'm just thinking out loud ...
Regards,
Will
.
- References:
- Re: C++/CLI integrating third party assembly
- From: William DePalo [MVP VC++]
- Re: C++/CLI integrating third party assembly
- Prev by Date: Re: How to compile a vcproj without linking and creating executables?
- Next by Date: How do I Compile from command line instead of inside Visual C++ 2005?
- Previous by thread: Re: C++/CLI integrating third party assembly
- Next by thread: How do I Compile from command line instead of inside Visual C++ 2005?
- Index(es):
Loading