Closed zippy1981 closed 11 years ago
I'm open towards including it. The only concern I have is that OrcaMDF is currently in a rather non-stable development mode, with no stability on the immediate horizon. Would it still make sense for a rather volatile codebase to be available as a Nuget package?
I think anyone using this library in a nuget project would either be cautious about running a nuget update, or be eager to experience the breakages as they happen.
That might be true. If a package is to be created it should probably only contain the OrcaMDF.Core assembly. Adhoc is going away and Tests isn't really relevant for the Nuget package. OMS might be in certain scenarios, but generally you'd probably want to stick with the Core if you're wanting to reference OrcaMDF.
One of my main concerns in regards to people using OrcaMDF is for people to be able to trust the code fully - that last thing I want is for someone to get a rogue OrcaMDF package and have it cause havoc in production. As such, I'd prefer to create the package itself and do the pushing of new versions. If you want to help out by doing the groundwork of creating a build process capable of creating the nuspec & nupkg files, I'll gladly accept it and make sure it gets the last way onto Nuget as an official package.
Sounds like a plan. I will make the build process generate a nuget package.
As for, OMS there is something called Chocolatey, which is a wrapper around nuget for dealing with executables. I maintain a few chocolatey packages. Anyway, I can make the sln generate a nuget package for OrcaMDF.Core and a chocolatey package for OMS, and you can upload them.
That sounds excellent. I appreciate your effort :)
There is no nuget package for OrcaMDF. I'd like to generate one. I'd prefer if my efforts were included in the OrcaMDF git repo. Is that agreeable?