You must activate Dotfuscator Professional with a valid license key before you can use it.
Dotfuscator Professional uses two license types:
- User Licenses are intended for developer workstations, evaluations, and configuration activities.
- Build Licenses are intended for build agents and production build systems. Applications protected with a Build License may be publicly distributed.
Licenses can be either floating or non-floating. Floating Licenses support shared and dynamically provisioned build environments and require an Internet connection whenever Dotfuscator runs. Non-Floating Licenses are activated on specific machines and can continue to operate without an Internet connection after activation.
When you purchase Dotfuscator Professional or download an evaluation version, PreEmptive provides a license key. The activation method you use depends on your license type and installation method.
Before You Begin
Before you activate Dotfuscator:
- Install Dotfuscator Professional.
- Have your license key available.
- Verify that you are using the correct license type for your scenario.
Internet Connection Requirements
Dotfuscator requires an Internet connection to activate licenses and validate licensing information.
- Product activation requires access to the PreEmptive licensing services.
- Floating licenses require an active Internet connection whenever Dotfuscator is running.
If your organization uses a firewall or proxy server, ensure that Dotfuscator can reach the following endpoints:
| URL | Purpose |
| https://activation.preemptive.com | Product activation |
| https://licensing.preemptive.com | License validation |
| https://registration.preemptive.com | Product registration |
If these endpoints are blocked, activation or license validation may fail.
Connection Retry Behavior
To reduce build failures caused by temporary network interruptions, the MSBuild targets, MSBuild tasks, and command-line interface automatically retry failed connections after a short delay.
If the licensing service is undergoing planned maintenance, Dotfuscator retries the connection every 30 seconds for up to 30 minutes by default.
You can customize this behavior using the following environment variables:
| Environment variable | Description | Default |
DOTFUSCATOR_MAINTENANCE_RETRY_DELAY |
Delay between connection attempts, in seconds. | 30 seconds |
DOTFUSCATOR_MAINTENANCE_RETRY_TIMEOUT |
Total retry period before reporting a failure, in minutes. | 30 minutes |
Both values must be specified as positive whole numbers.
Authenticated Proxy Support
If your environment uses an authenticated proxy, configure the following environment variables before activating Dotfuscator:
| Environment variable | Description |
DOTFUSCATOR_PROXY_USERNAME |
Proxy username. |
DOTFUSCATOR_PROXY_PASSWORD |
Proxy password. |
DOTFUSCATOR_PROXY_ADDRESS |
Proxy server address. Required only if the proxy is not configured as the system proxy. |
DOTFUSCATOR_PROXY_PORT |
Proxy server port. Required only if the proxy is not configured as the system proxy. |
Choose an Activation Method
Dotfuscator Professional supports the following activation methods:
| Activation method | Recommended for |
| Activation Tool | Windows development machines using the Windows installer. |
| Environment variable | Build agents, automated builds, and NuGet package installations |
| Command argument | CI/CD scripts, MSBuild workflows, and command-line workflows |
The available activation methods depend on the installation method.
| Installation Method | Supported Activation Methods |
| Windows Installer | Activation Tool during installation, Config Editor, environment variable, command-line argument |
| NuGet Package | Environment variable, command-line argument |
Activate Using the Activation Tool
If you install Dotfuscator using the Windows Installer, the Activation Tool launches automatically after installation if Dotfuscator has not already been activated on the machine.
The Config Editor also opens the Activation Tool if Dotfuscator has not yet been activated on the machine.
To activate:
- When the Activation Tool opens after installation or from the Config Editor, select Click here to activate Dotfuscator.
- The Activation Tool opens your web browser to preemptive.com. Enter your credentials and select Log in.
- Enter the License Key and select Activate.
- Your web browser communicates back to the Activation Tool via a localhost HTTP request. Wait for the Activation Tool to verify the activation.
- When the activation succeeds, select Finish.
Dotfuscator stores a license token on the machine. Future executions do not require reactivation.
Activate Using an Environment Variable
Set the DOTFUSCATOR_LICENSE environment variable to a valid license string. Each time Dotfuscator runs, it reads the license information from the environment variable.
This method is recommended for:
- Build agents
- Automated builds
- Dynamic or short-lived environments
- NuGet package installations
- CI/CD systems that store secrets as protected variables
If you have a Build License, your license string is just your license key. If you have a User License, your license string is your license key and your email address separated by a colon, for example: 00000000000000000000000000000000:jdoe@mycompany.com.
Activate Using a Command Line Argument
You can also provide the license directly when Dotfuscator runs.
Depending on your workflow, provide the license by using one of the following options:
- Set the
DotfuscatorLicenseproperty when running MSBuild targets. - Set the
Licenseparameter when running MSBuild tasks. - Pass the
-licenseargument to the Dotfuscator command line interface.
This method is useful for:
- CI/CD scripts
- MSBuild workflows
- Direct command-line workflows
- Automated environments where license values are passed as protected parameters
Verify Activation
After activating Dotfuscator, verify that activation works before using it in a production build.
Confirm that:
- Dotfuscator starts without activation errors.
- The Config Editor opens, if you use the Windows installer.
- Your build or command-line workflow can access the license.
- Build logs do not expose license values.
- Dotfuscator can process a test configuration successfully.
Troubleshooting
If activation fails, check the following items first:
| Issue | What to check |
| Activation Tool does not open | Confirm that you installed Dotfuscator with the Windows installer. |
| Config Editor activation is unavailable | Confirm that the Config Editor is installed and you are running Dotfuscator on Windows. |
| Activation or validation fails | Verify that the required licensing endpoints are accessible through your firewall or proxy configuration. |
| NuGet package activation fails | Confirm that you are using an environment variable or command argument. |
| Build agent activation fails | Confirm that the license variable is available to the build job. |
| License appears in logs | Mask the license variable in your CI/CD system and avoid printing commands that contain secrets. |
| Dotfuscator still asks for activation | Confirm that the license value is valid and available in the environment where Dotfuscator runs. |
Next Steps
After activating Dotfuscator Professional: