Re: C++/CLI integrating third party assembly
- From: "William DePalo [MVP VC++]" <willd.no.spam@xxxxxxxx>
- Date: Fri, 22 Dec 2006 10:42:11 -0500
"kyle.schmidt" <kyleschmidt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:363C2FAC-3E49-4C1D-89CB-D4510F62AE5C@xxxxxxxxxxxxxxxx
My questions then are, what is different between launching a C++/CLI app
through VS2005 without debugging vs through windows explorer that would be
causing things to work differently?
At the risk of asking the obvious, have you set the debugger's working
directory to be the same as the directory that works when you run the
application manually?
Is there something the third party provider could check at run-time to
disable
functionality, but only with the C++ environment? The third party tool has
been
dotfuscated, so is there anything in the dotfuscator that could be
preventing
this from working correctly?
I believe some applications check for the presence of the debugger and
behave differently when it is.
Regards.
Will
.
- Prev by Date: Re: Setting Application Version in VC .Net
- Next by Date: Re: How to compile a vcproj without linking and creating executables?
- Previous by thread: Re: How to compile a vcproj without linking and creating executables?
- Next by thread: Re: C++/CLI integrating third party assembly
- Index(es):
Relevant Pages
|
