[rabbitmq-discuss] Would like to start merging .NET client for WinRT (Windows 8 Store App) with mainline code
mklishin at gopivotal.com
Mon Jun 9 23:18:50 BST 2014
On 10 June 2014 at 01:48:41, Nathan Brown (nathan at nkbrown.us) wrote:
> > > Good question. If WinRT is an incompatible target, does it
> > there should be 2 packages, X and X-winrt, for example?
> Different platform DLLs go in a named folders inside of the NuGet
> package. Everything is delivered together and Visual Studio
> links to the correct DLL. If it was possible to build the NuGet
> package as part of the CI process, that would be the best. Currently
> the NuGet creation lives elsewhere and is manually populated
> with the release binaries.
I'll ask our NuGet package maintainer to chime in. I suspect it's time to
open source the code used for NuGet packaging ;)
> > Is it technically possible to run the current NUnit test suite
> > on WinRT? Protocol configuration is removed in default and
> 3.4 will only
> > support one protocol (0-9-1). Do we still need to worry about
> using MSTest
> > then?
> NUnit was able to test it without the configuration part. I can
> remove that and remove all the MSTest changes. The test runner
> then works as a desktop process (on Windows 8/Server 2012).
> > If your branch is in Mercurial or Git somewhere, we can work on
> it until it's
> > mostly done, then create a bug and pull it into the mainline.
> Anyone can pull it from Bitbucket(https://bitbucket.org/nathanbrown/rabbitmq-dotnet-client)
> right now. I can continue to work there.
Lets do that. A public Mercurial repo is all we care about when it's time
Software Engineer, Pivotal/RabbitMQ
More information about the rabbitmq-discuss