Rank: Guest
Groups: Guest
Joined: 9/17/2007
Posts: 11,670
Points: -1,200
|
Date parsed: 16/04/2008 16:54:56
Date: Wed, 16 Apr 2008 15:54:56 +0100
Bernard wrote:
>
> Hello,
>
> I use a third party tool to protect and encrypt my application. This
> tool modifies the executable file compiled by VS, in order to encrypt
> some parts of the code and embed the protection into it.
>
> Now, when I try to build the Setup project, VS automatically removes the
> modified version of my executable and replaces it with the latest
> compiled version (not protected) before building Setup.msi.
>
> How can I force VS to keep the modified executable ?
>
> Thanks !
I've used the (free after registration) Dotfuscator Extended Community
Edition which fully ties into the IDE (unlike the basic CE version).
This adds a new project type for the obfuscation which can, like the
installer project, use "Primary output from XYZ" as the input.
Similarly, it exposes this interface to the installer project - ie. you
can select the "Primary output from obfuscation project" as the input to
the installer.
I don't know what tool you're using to generate your outputs, but having
something which plays nicely with the normal build process is great. Do
they make a version which works like this?
D
|
Rank: Guest
Groups: Guest
Joined: 9/17/2007
Posts: 11,670
Points: -1,200
|
Date parsed: 16/04/2008 18:44:51
Date: Wed, 16 Apr 2008 16:44:51 +0200
Hello,
I use a third party tool to protect and encrypt my application. This tool
modifies the executable file compiled by VS, in order to encrypt some parts of
the code and embed the protection into it.
Now, when I try to build the Setup project, VS automatically removes the
modified version of my executable and replaces it with the latest compiled
version (not protected) before building Setup.msi.
How can I force VS to keep the modified executable ?
Thanks !
|
Rank: Guest
Groups: Guest
Joined: 9/17/2007
Posts: 11,670
Points: -1,200
|
Date parsed: 17/04/2008 13:08:41
Date: Thu, 17 Apr 2008 11:08:41 +0200
Hello David,
It's solved : I was patching the .EXE located in the .bin/Release folder instead
of obj/Release. Now it works fine.
BTW, the protection tool which I'm using is PC Guard.
Regards,
Bernard
David Hearn a écrit :
> Bernard wrote:
>>
>> Hello,
>>
>> I use a third party tool to protect and encrypt my application. This
>> tool modifies the executable file compiled by VS, in order to encrypt
>> some parts of the code and embed the protection into it.
>>
>> Now, when I try to build the Setup project, VS automatically removes
>> the modified version of my executable and replaces it with the latest
>> compiled version (not protected) before building Setup.msi.
>>
>> How can I force VS to keep the modified executable ?
>>
>> Thanks !
>
> I've used the (free after registration) Dotfuscator Extended Community
> Edition which fully ties into the IDE (unlike the basic CE version).
> This adds a new project type for the obfuscation which can, like the
> installer project, use "Primary output from XYZ" as the input.
> Similarly, it exposes this interface to the installer project - ie. you
> can select the "Primary output from obfuscation project" as the input to
> the installer.
>
> I don't know what tool you're using to generate your outputs, but having
> something which plays nicely with the normal build process is great. Do
> they make a version which works like this?
>
> D
|
