The name of the project will be the
name of the solution in Visual Studio, but this can be edited. The application will be associated with the project in the ByteHide account of the user who is logged in at that time. Or one will be created with that name.
Project applications will appear in the left side, while the name of the application file to be protected will appear in the
File to protect field on the right side.
If your application does not appear on the left side, and the
file to protect field appears empty, you must manually type the name of the
.dll file to protect so that the extension recognizes it correctly.
Default and custom protections
The protections will apply to all the applications that a project has. Different protection profiles offered by the
Shield can be chosen.
If you need a custom configuratio for the protection of your project, you can add the corresponding configuration file in the project folder and select the
Find manual settings. In this way the protections that this file contains will be applied.
Configure release and debug
The Dotnetsafer extension allows you to apply security settings only on the
Build Profile of your choice. You will have full control over when you want to use it. You can choose to do it only in the
Release Build or in the
You can also configure the execution of the ByteHide Shield protections during any of the
Custom Build Profiles you have.
Here we have a profile called
Testing, and this will be the one that we will have selected in the extension to be executed in the build process.