An error occurred during search results load.
NuGet is the package manager for the Microsoft development platform. It allows to quickly add a library or a tool to your project.
Eazfuscator.NET is not exception and can be added to your solution via NuGet too.
Why ever bother to use NuGet when we have MSI? A good question. Actually, there are no many reasons to do so. However some usage scenarios can not work with MSI. Let's take a look at the list:
This is the point when NuGet becomes useful for Eazfuscator.NET deployment. So, let's add Eazfuscator.NET NuGet package to your solution:
To do that, please go to
Options window will show:
Please ensure there is a registered package source with
gapotchenko.com name and
http://www.gapotchenko.com/nuget URL as shown above.
Open context menu for solution and click on Manage NuGet Packages for Solution... item:
NuGet packages management window will open:
Please ensure you are going to install
Eazfuscator.NET (Official) package from
gapotchenko.com source and
The projects remain intact, e.g. they don't become protected or unprotected. They behave the same way they did before.
So, the basic workflow of project integration remains the same:
You can launch Eazfuscator.NET Assistant from Desktop, or you can invoke it from Package Manager Console, it does not matter. It just works no matter what deployment method is in use currently.
Well, it does obfuscation for projects that are considered as protected, e.g. were dropped to the green zone any time before or after. This is the very same behavior of MSI-deployed Eazfucator.NET.
The big difference is this: Eazfuscator.NET is now able to travel to the cloud or a hosted TFS build agent and work there. Just like any source part of your project. Thanks to NuGet, Eazfuscator.NET does not need to be installed on machine.
Eazfuscator.NET does not support NuGet package restore. Instead, Eazfuscator.NET package should be stored together with your sources.