Geek Answers Handbook

Team Building and Dotfuscator

I created a solution that included all of my projects, including Dotfuscator projects and installation projects. Some of the Dotfuscator projects confuse only certain assemblies without affecting any of their references. When creating from Visual Studio, this works great. However, when I run the build command, I get the following error:

C: \ Program Files \ MSBuild \ Preemptive \ Dotfuscator \ 4.0 \ PreEmptive.Dotfuscator.Targets (20.3): Error: The external type could not be loaded because its assembly could not be found:

An external assembly is a reference to a running assembly, but it is not part of the obfuscation project.

+4
source share
2 answers

The linked assembly should not be part of the Dotfuscator project, but it should be readable by Dotfuscator. I suspect the referenced assembly is in the same directory as your input assemblies on your workstation, on the way to your workstation or in the GAC. The referenced assembly is probably not located on your build server (or Dotfuscator cannot be found). You can provide Custom assembly loading paths where Dotfuscator will additionally search when trying to resolve referenced assemblies.

A linked assembly is required on the assembly server for Dotfuscator to successfully obfuscate, and the best way is to either ensure that the referenced assembly is in the same directory as the input assemblies, or to use the load path of the custom assembly.

In addition, new in version 4.5.1200, you can first find your user-defined download path, and not the default for searching the latter.

+3
source

C: \ Program Files \ MSBuild \ PreEmptive \ Dotfuscator \ 4.0 \ PreEmptive.Dotfuscator.Targets

This assembly must be on the same server as your machine Agent assembly.

In simple words, assuming TFSServer is the name of the data-layer MAchine (containing the source files), as well as the Build Machine , then the target point access files should be available to it.

Just install dotfuscator on the machine ** TFSServer , and the path will be available to it along with the corresponding target files. **

0
source

More articles:


All Articles