I've been working on chocolatey. Think application packages. Think #chocolatey #nuget.

Basically you put your executables in the tools folder (or elsewhere) local to a project, but really you want that to go to a machine level nuget repository because you may want to have access to that executable machine wide. Chocolatey allows for this and kind of opens up an another area for nuget: application packages.  Not having application packages is the one thing that has slowed me down from bringing over some of my apps from gems to nuget - because they are applications and not libs. 

With chocolatey you can install an application nugget like roundhouse / lessmsi / warmup / opensslkey onto the machine and then be able to call it from the command line and powershell.

UAC assertion: I was able to figure out uac assertion in nuget. Not sure how many any other packages are doing this yet. If you need a good example, take a look at chocolatey.

I am hoping to put together a video soon as well to show the power of what it can do.

For those that have been putting their applications in the tools folders, like NUnit (thanks Charlie!), you can instantly use chocolatey to install and use nunit.

 'chocolatey install nunit'

When it is done type

 'nunit'

Or pick one of the other executables that come with nunit. :D

Interesting! So generally, you can run it on any package that contains a tools folder? I tried to run it on a random package that doesn't have tools (just to try!), and it failed with:

chocolatey.bat : You cannot call a method on a null-valued expression.At line:1 char:11

Might make sense to detect the situation and give some guidance.

Other thought: should chocolatey uninstall itself from the project after it's installed machine level?

Hey, you're the one who came up with that crazy self-uninstall trick! It's a matter of using all your tricks at once :)

Oh yes, that's right, my bad!

Yep, that fixed the error!

Can chocolatey install IE9? What about install Windows? ;)