Eazfuscator.NET 4.3 can now be deployed via NuGet.
Historically Eazfuscator.NET is deployed as .MSI file that can be downloaded from the website. That's an awesome way of delivering Eazfuscator.NET to your development machine.
There is another use case: delivering Eazfuscator.NET to build servers. Once you have Eazfucator.NET .MSI file, you login to a build server and install it there. Simple.
MSI (Windows Installer) technology is proven and reliable. If you have any doubts about what deployment method to choose for Eazfuscator.NET then please strongly consider MSI.
NuGet
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 not many reasons to do so. However some usage scenarios can not work with MSI. Let's take a look at the list:
Hosted TFS Build Agents may disallow software installs. This depends on TFS administration policies. They may prohibit the installation of third-party software on host machines
Visual Studio Online does not allow software installs
This is the point when NuGet becomes useful for Eazfuscator.NET deployment.
Once NuGet package is installed in your project, Eazfuscator.NET is able to instantly travel to the cloud or a hosted TFS build agent and do the job there. Just like any source part of your project. Thanks to NuGet, Eazfuscator.NET does not need to be installed on machine.
Please note that Eazfuscator.NET package is officially published on a dedicated NuGet server http://www.gapotchenko.com/nuget. Further details are available in Eazfuscator.NET documentation.