This project is read-only.

Why depending on NuGet.PackageNPublish

May 17, 2013 at 8:03 PM
Why Bootstrapper depends on NuGet.PackageNPublish?
Is that really necessary?
May 17, 2013 at 8:09 PM
I use it to automate the creation of the nuget package in my build. It is definitely not needed for runtime.
I'll see if I can remove it from the package.
Thanks for calling my attention to this.
May 17, 2013 at 8:15 PM
Please, remove it from the package.
Jun 2, 2013 at 5:27 PM
Edited Jun 2, 2013 at 5:47 PM
Yeah, this is one of the dependencies that was cluttering our project also. I'm not sure it needs to be in your deployment references. Either way, it would be nice to see it go away but isn't "breaking" anything.

I did poke around the code for a very small amount of time and it looks like you may simply be able to remove the reference to NuGet.PackageNPublish from the nupkg file that gets created. Now how this happens as an automated process i'm not sure but manually removing that should work fine, since non of the distributed dlls actually have a dependency on that package.
Jun 26, 2013 at 2:51 PM
I was finally able to remove the dependency from the automated process. But I'm waiting until I have another feature to publish it. Stay tuned.....