NuGet OpenWrap support?

[Marijn]

Hi there,

Is anybody planning to create NuGet or OpenWrap packages for Spring.NET?

Regards,

~Marijn

[Steve Bohlen]

NuGet is something that we are presently working on and expect to have ready quite soon. As you can see from this commit (https://fisheye.springsource.org/changelog/spring-net?cs=1194), most of the work is complete and we need to just hook it into our build-execution scripts to get it working.

OpenWrap is something that we are investigating and considering. As I understand it, OW will (does?) support NuGet packages and so once we have those established we would get OW support of Spring.NET 'for free'. Do you have a specific OW use-case in mind for which we would need to construct a Spring.NET Wrap or do you think that OW implicit support of Spring.NET via its upcoming NuGet package would be sufficient?

Would be interested in your thoughts on this.

-Steve B.

[Marijn]

My primary use case at the moment is for NuGet. We could really use a good package manager in the OS .net world. At this stage I feel that NuGet is doing the right things to get many .net developers on board, mainly by the integration with VS and the combination of their presence in the .net OS ecosystem and relation to Microsoft.

That being said, I like some of the design goals of OpenWrap better, especially that it doesn't depend on PowerShell/VS and that it does a best effort to support NuGet (https://github.com/openrasta/openwrap/wiki/Nuget). Paradoxically, the latter is the main reason for me to go with NuGet at this stage. But I'll definitely keep an eye on OpenWrap.

In short, for me the upcoming NuGet packages will suffice, I'm very happy that you've added NuGet support and I'm looking forward to my first
PM> install-package Spring.Core

Regards,


~Marijn

[Marijn]

On a side note: it's a good thing that you guys have been focusing on some technical features that will flatten the learning curve for new users. NuGet helps. Codeconfig helps. VS support helps.