Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Disclaimer: I work for PreEmptive Solutions, the makers of Dotfuscator.</p> <p>The issue with Jared's solution is that a post build task executes too late in the build process as the ClickOnce build steps create the manifests (including assembly signatures, which obfuscation changes) long before the post build fires. You can hack the MSBuild file (your .csproj/.vbproj) file to call the obfuscation task in the AfterCompile step and have the obfuscator dump the obfuscated assemblies into the builds bin directory but this is a pain.</p> <p>A second alternative is to use the Mage/MageUI tools to recreate the ClickOnce manifests by publishing your application, obfuscating the assemblies, overwriting the published assemblies with the obfuscated versions and then running Mage to recreate the manifests as shown <a href="http://msdn.microsoft.com/en-us/library/xc3tc5xx.aspx" rel="noreferrer">here</a>. Documentation for the Mage utility is <a href="http://msdn.microsoft.com/en-us/library/acz3y3te(VS.80).aspx" rel="noreferrer">here</a>.</p> <p>A third alternative is if your obfuscator is Dotfuscator Professional edition version 4.6.1010 or higher. Dotfuscator has the ability to directly read a ClickOnce deployment manifest as an input, obfuscate the assemblies and output both the obfuscated assemblies and fully updated manifest files. See <a href="http://www.preemptive.com/images/stories/dotfuscator_documentation/Dotfuscator/ClickOnce_Package.html" rel="noreferrer">here</a> for a starting point.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload