Re: Dotfuscator and ClickOnce

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I was able to apply a strong name to the application's executable by not doing it in Visual Studio
but as part of the script I was using to run Dotfuscator. So the steps are:'
1. Publish from Visual Studio
2. Apply Dotfuscator
3. Apply strong name to executable
4. Update the .application and .manifest files via Mage.exe.
5. Install

Unfortunately, Dofuscator makes the application unable to access Settings. It appears that the
entire exercise of trying to use Dofuscator for ClickOnce was futile as the results does work
anyway.

Joe Kuemerle <Joe Kuemerle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Linda Liu[MSFT]" wrote:

Doesn't the ApplicationName.exe have to be signed again after applying
Dotfuscator?

After applying Dotfuscator, only the application manifest and deployment
manifest must be updated and resigned.

The error message is:
Strong name signature not valid for this assembly ApplicationName.exe

It looks like you strong-name the assembly. I have tried to strong-name an
executable and apply dotfuscator on it. The result is that the executable
can't run at all.

This occurs because obfuscation changes the binary by renaming all of the
symbols within in and thus the assembly no longer hashes to the original
value of the strong name signature. Whenever a strong named assembly is
obfuscated it must be resigned after the obfuscation has taken place in order
that a new strong name signature is generated. This also applies to
Authenticode signing of assemblies that you wish to obfuscate.

.

Relevant Pages

  • Re: Dotfuscator disassociates derived class when base class is lin
    ... I tried Dotfuscator in the early days I think way back in .NET 1.1 and could ... never get it to behave and I think many other developers have found the same ... any dependency assemblies the input assembly is dependent on. ... obvioously this then defeats the purpose of obfuscation. ...
    (microsoft.public.dotnet.framework.compactframework)
  • RE: DotFuscator Prof- Project lost when changes made
    ... For some reason searching Managed Newsgroups for DotFuscator fails to find ... So to help people find it Obfuscator and Obfuscation and DotFuscator ... > Using a DotFuscator Professional v2.0 Project in Visual Studio 2003. ... > After creating and obfuscating a set of assemblies then closing visual studio ...
    (microsoft.public.vsnet.ide)
  • Re: Problem using obfuscation
    ... I'm using Dotfuscator that comes along with the Visual studio.Net. ... I'm using obfuscation for the first time, so not sure how to use it ... obfuscate multiple assemblies which are using each other's public ... class libraries which use each other's classes too having refrence ...
    (microsoft.public.dotnet.security)
  • Re: Problem using obfuscation
    ... I'm using Dotfuscator that comes along with the Visual studio.Net. ... I'm using obfuscation for the first time, so not sure how to use it ... obfuscate multiple assemblies which are using each other's public ... class libraries which use each other's classes too having refrence ...
    (microsoft.public.dotnet.security)
  • RE: DotFuscator Prof- Project lost when changes made
    ... We have discovered that this problem occurs when the Debug objfuscation has ... If we do not delete the Debug obfuscation it works fine. ... > Using a DotFuscator Professional v2.0 Project in Visual Studio 2003. ... > After creating and obfuscating a set of assemblies then closing visual studio ...
    (microsoft.public.vsnet.ide)