The Protect task runs the Dotfuscator Community command line interface on the build host using the specified configuration file and arguments. Later steps in your build can use this to invoke Dotfuscator Community (e.g. When run, the Provision step sets and exposes a build variable called DotfuscatorCEDir, which points to the location of the Dotfuscator Community command line executable on the build host. Only set this if Visual Studio is not installed in the default location on the build host.
The serial number is also available from the Help -> About menu in the Dotfuscator Community GUI. You may need to add "-391" to the end of the serial number you recieved via email. Serial Number: The serial number you received when you registered your local copy of Dotfuscator Community.Add the Provision step to your build definition, anywhere before Dotfuscator Community runs. The Provision step is required in order to activate the Dotfuscator Community command line interface on the build host. Ensure that your build saves the obfuscated output assemblies and the renaming map file as build artifacts (e.g.You can use the Protect task to invoke Dotfuscator Community as a distinct step in your build definition.The Provision task exposes a build variable with Dotfuscator Community's location on the build host. via an MSBuild exec task in one of your projects. You can invoke the Dotfuscator command line interface directly, e.g.The best way to do this will depend on your project: Add a step to run Dotfuscator after your assemblies have been built.Add the Provision task to your build definition.
It is installed by default in Visual Studio 2015 Visual Studio 20 users can install it via the Visual Studio Installer's "Individual Components" tab. If you are using a custom build host, you can verify that Dotfuscator Community is installed by looking for its entry on Visual Studio's Tools menu. Note that Microsoft-hosted agents that include Visual Studio already meet this requirement. Visual Studio 2015, 2017, or 2019 must be installed on your build hosts, with the Dotfuscator Community component installed.
Azure Pipelines is required, or for earlier on-premises installations, Team Foundation Server 2015 Update 4 or later.A Protect task that runs Dotfuscator Community's command line tool, with user-specified arguments.A Provision task that configures Dotfuscator Community at the start of each build, and sets up a build variable that can be consumed in later build steps.The extension installs the following tasks:
The user guide for Dotfuscator Community in Visual Studio 20.Ī blog article explaining how to enable and use the Dotfuscator Community command line interface in your build process: Using the Dotfuscator Community command line interface. You may also find the Dotfuscator Professional user guide to be helpful, especially the section concerning Build Agents. The user guide for Dotfuscator Community. These references will help you get started: This extension is used to integrate Dotfuscator Community into Azure Pipelines.īefore you do that, you should be familiar with Dotfuscator Community itself, which is included with your local copy of Visual Studio. Getting Started with Dotfuscator Community Visit the Visual Studio Marketplace Entry to learn more about adding enhanced protection to your build process. The Dotfuscator Professional Azure DevOps Extension is now available! The Dotfuscator Community extension adds tasks to your Azure DevOps build process that help you protect your applications from unauthorized decompilation, tampering, debugging, and data access. Protect your Applications with Dotfuscator Community