the title says it all: it would be great to have a nuget package for the library part of Sho. I am using Sho right now in a C# project (or rather, I am evaluating its use) and one of the major barriers right now is that other team members that work on the source code as well would have to go through the manuel process of installing Sho. It would be much easier if they could get the necessary stuff onto their machine via nuget.
For most other libraries we use we ended up just putting the dlls into a folder in source control, but given Sho's dependencies on MLK and also the fact that it simply is quite a lot, that doesn't seem very feasble.
Hi David --
We actually use the Sho libraries quite a bit in projects under source control. It turns out you don't have to install Sho on each machine that will use the libraries - you just need to check in the "bin" directory (and all of its subdirectories) into your source tree. Since the other machines syncing with this code won't have the registry keys telling Sho where to find the MKL dependencies, you'll have to set an environment variable programmatically within your code. Our Sho External API Guide explains the details on how to do this.
Ah, thanks, I guess that would work.
Still, a NuGet package that would just handle all of this automatically would be great, really seems to be the way to go.
Finally got around to do this. It is way too complicated. I ended up doing this:
1) I added whole Sho bin directory to my TFS folder
2) I made all my projects ref the dlls in that TFS folder
Now my projects build on our build server without having to install Sho there
3) I added a post-build script that copies all binaries into the Bin\Release (or Debug) folder
Now I can just run stuff.
I really think a nuget package would be the answer for this. Have a look at the sqlservercompact package, they automate all of this, including the addition of the necessary post-build copy code etc.