MSBuild, dotObuscator 4.1, and ClickOnce deployment problems

[LancashireLad]

I’m trying to obfuscate the source code for a Clickonce Windows forms project using dotObuscator 4.1 (CE+) edition. The goal is to use MSBuild to script the process. However, I’m still having problems getting the signing process to work. I get the following MSBuild script to run okay but the install fails with a hashvalidation error. Basically my script copies the uses the event to backup the original compiled files and then run dotObuscator. The script then copies the obuscated files to the release\bin directory, signs them and regenerates the manifest. I’ve only included the signing part of the script for clarity. General questions: Do I need to sign the EXE file in both the bin\release and obj\release directories? Do I need to sign additional DLLs? It looks like the new manifest is not being generated correctly. Any advice is appreciated. Note: This approach came from an forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=166236&SiteID=1 (Copy obfuscated files to release\bin and release\obj directory) < SignFile CertificateThumbprint ="0d5ef111f89cf3ccc2eb36fa01a42d411f680704" SigningTarget ="C:\..\bin\Release\sharpSh3ll.dll"/>

[LancashireLad]

Reposting as some of the previous message was missing. I’m trying to obfuscate the source code for a Clickonce Windows forms project using dotObuscator 4.1 (CE+) edition. The goal is to use MSBuild to script the process. However, I’m still having problems getting the signing process to work. I get the following MSBuild script to run okay but the install fails with a hashvalidation error. Basically my script copies the uses the event to backup the original compiled files and then run dotObuscator. The script then copies the obuscated files to the release\bin directory, signs them and regenerates the manifest. I’ve only included the signing part of the script for clarity. Do I need to sign the EXE file in both the bin\release and obj\release directories? Do I need to sign additional DLLs? It looks like the new manifest is not being generated correctly. Any advice is appreciated. Note: This approach came from an forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=166236&SiteID=1 (Copy obfuscated files to release\bin and release\obj directory) < SignFile CertificateThumbprint ="0d5ef111f89cf3ccc2eb36fa01a42d411f680704" SigningTarget ="C:\..\bin\Release\sharpSh3ll.dll"/>

[LancashireLad]

AAArgh 3rd time lucky. I forgot to click Ignore HTML tags. I’m trying to obfuscate the source code for a Clickonce Windows forms project using dotObuscator 4.1 (CE+) edition. The goal is to use MSBuild to script the process. However, I’m still having problems getting the signing process to work. I get the following MSBuild script to run okay but the install fails with a hashvalidation error. Basically my script copies the uses the event to backup the original compiled files and then run dotObuscator. The script then copies the obuscated files to the release\bin directory, signs them and regenerates the manifest. I’ve only included the signing part of the script for clarity. Do I need to sign the EXE file in both the bin\release and obj\release directories? Do I need to sign additional DLLs? It looks like the new manifest is not being generated correctly. Any advice is appreciated. Note: This approach came from an forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=166236&SiteID=1 (Copy obfuscated files to release\bin and release\obj directory) < SignFile CertificateThumbprint ="0d5ef111f89cf3ccc2eb36fa01a42d411f680704" SigningTarget ="C:\..\bin\Release\sharpSh3ll.dll"/>