#TEAMCITY VS AZURE DEVOPS INSTALL#

If your build encounters errors finding Dotfuscator's targets or tasks, see Troubleshooting. This is also true if you have a custom MSBuild project that calls Dotfuscator via its Dotfuscate task. vbproj, etc.) on your build agents immediately after completing the Windows installer. If you followed the recommended Protect Your App instructions, you should be able to build your Dotfuscator-integrated MSBuild projects (.

#TEAMCITY VS AZURE DEVOPS INSTALL#

To install Dotfuscator on a build agent for which you have administrator access, follow the same instructions used for development machines. If your build agents run Windows and are pre-provisioned (long-running, shared across build jobs), you also have the option of running the Windows installer one time on each build agent.ĭepending on your environment, this may be more convenient compared to using the NuGet package. This latter case allows Dotfuscator to be available on build agents which are dynamically provisioned (allocated and deallocated with each build job), such as when using Microsoft-hosted agents on Azure Pipelines. You can provision the package one time per build agent, or you can have your build scripts provision the package on the assigned agents every time a build runs. The NuGet package can be used on any supported OS (Windows, macOS, or Linux).

You can use either package to install Dotfuscator onto Windows machines.įor macOS and Linux machines, only the NuGet package can be used.ĭotfuscator's capabilities vary depending on which package you use and what operating system you run Dotfuscator on. Dotfuscator has two installation packages: the Windows installer (.

Teamcity vs azure devops