My last post covered tips for people creating Nuget packages. This one is important for people consuming Nuget packages.
Some Nuget packages include executables in their tools folder. It is very easy to use these tools within Visual Studio because Nuget makes them available in the path of the Package Manager Console. However, they are very difficult to use outside of Visual Studio, especially in a build script. The problem is the name of the folder containing the installed package includes the version number of the package. If you install NUnit 2.5.1, the nunit-console.exe will be in packages\NUnit.2.5.1\tools. However, if you later upgrade to NUnit.2.5.2, the path to nunit-console.exe will change to packages\NUnit.2.5.2\tools. You will need to change your build scripts every time you upgrade your version of NUnit. That is unacceptable.
The solution is to create a helper that can figure out where the tool lives. If you are using rake for build automation, it is fairly straightforward:
If not, you may want to create a batch file in the root of your project that calls your tool. You can create a tool specific batch file:
Or, if you have lots of tools from different packages, you might just want a generic batch file that allows you to specify the executable name: