We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.

mnivet • 8 years ago

Great idea! And wonderful hint about the Get-Project cmdlet.

This helps me to write unit tests using Pester and a small extension that I've write to use it easily inside the Package Manager Console:
https://www.nuget.org/packa...

Lawson • 9 years ago

This is money, helped me quickly get to my issue, thanks for sharing!

Alex • 10 years ago

Saved lots of my time, thanks!

MichaelD! • 10 years ago

Thank you for making this!!! Exactly what I was looking for.

Andrey • 10 years ago

Thanks a lot for your Get-Project hint!

Terje • 10 years ago

Note, I meant the NuGetDebugTools, not this article

Roman • 11 years ago

For debugging NuGet specific scripts in the Visual Studio NuGet console (init.ps1, install.ps1, uninstall.ps1, etc.) this simple script debugger may be useful:
https://www.nuget.org/packa...

Terje • 10 years ago

I tried to find usage information on this, but failed. How is this package meant to be used ?

rob • 11 years ago

Nice!

Michael • 12 years ago

Have you checked out Pester?
https://github.com/pester/P...

rob • 12 years ago

Haven't used it, but I do know of it :)

While it's handy, it's less useful in this case because (I imagine) constructing a DTE object and getting the right values for the other input parameters is a pain - using real NuGet install pipeline as a test harness is the easiest way and the technique I've shown here streamlines it so it's not too painful (I think).