Once you have installed the package and associated your account with the API key your applications will be protected when compiling, it's that simple ✨. It will only be protected when compiling in release mode, so now you can configure all other options.
We are working on individual configuration files, but at the moment all configurations are done in your
.csproj project file.
Select a preset
We have several types of presets, which are protection configurations by a team of cybersecurity engineers.
Maximum Protection: It offers the most complete security overcoming the performance and the recommendations by AI.
Balance: It offers a perfect balance between security and performance of your application that takes full advantage of the options in your edition of Dotnetsafer Shield.
Optimization: Add the maximum possible security by putting application performance and method execution milliseconds first.
To select a preset, you simply have to set the
Where the options are
There is another section in the documentation that explains how to configure custom presets.
Change project name
When you protect outside the web panel, it is always associated to a project (to keep history, settings and have everything synchronized), by default the name of the visual studio project or csproj file is used, if you want to change it or share an existing one, you can do it easily:
If the name already exists in your web panel, it will be used without creating a new one.
Force Shield to always protect
By default, it will only be protected in the build process when in Release mode (to avoid unnecessary protections in development), but if for some reason you are using custom modes or wish to ignore this, you can use the
<ShieldForce> property to make Shield always protect your application.
If, on the other hand, you wish to stop Shield for a while, you do not need to uninstall and delete the configuration if you are going to protect again later, just use
<ShieldEnabled> to pause the service indefinitely until you change it again.