[rabbitmq-discuss] Would like to start merging .NET client for WinRT (Windows 8 Store App) with mainline code

[Nathan Brown]

Mike,


>> How is the NuGet package going to be updated?

> Good question. If WinRT is an incompatible target, does it mean
> 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.

> 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.

Thanks,
Nathan Brown


On Mon, Jun 9, 2014 at 1:54 PM, Michael Klishin <mklishin at gopivotal.com>
wrote:

> On 10 June 2014 at 00:41:18, Nathan Brown (nathan at nkbrown.us) wrote:
>
> Nathan,
>
> First of all, thank you for working on this. It would be great to have
> WinRT support in the .NET client!
>
> > > There are a couple issues that still need to be worked through:
> > Can the CI build be on a Windows 8/Server 2012 machine? Or is the
> > build going to have to be ran separately just for this DLL?
>
> Windows CI currently uses Windows XP. We'll see if adding more
> Windows versions is easy enough, and in particular Windows 8.
>
> > How is the NuGet package going to be updated?
>
> Good question. If WinRT is an incompatible target, does it mean
> there should be 2 packages, X and X-winrt, for example?
>
> > I haven't tested SSL.
>
> This needs to happen.
>
> > The unit tests are currently partially ported to MSTest, but
> > this is primarily because of reading WinRT configuration data
> > doesn't work on the desktop, I think I should drop that entirely
> > (Protocols.FromConfiguration(string)).
>
> 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?
>
> I don't have a bug number to give but we also don't need one.
> 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.
> --
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140609/21147939/attachment.html>