.Net Native release build issue

[Neno12]

Hi,

I am trying to use RTMPClient in a Universal Windows App for Windows 10 and I have problem with building on .Net Native.

The problem is when I try to build an app which used this library in release, it would fail because currently .Net Native have some issues dealing with IKeyValuePair<K,V> type.

I have contacted .Net Native team and asked fro help on this issue and I received the following response from them:

We are having trouble with the Mntone.Data.Amf.AmfPair type. This type implements Windows.Foundation.Collections.IKeyValuePair<IAmfValue, IAmfValue> which is a special Windows Runtime type for us as we always convert instances of this type to the more familiar .NET type of System.Collections.Generic.KeyValuePair.

We expect that IKeyValuePair<K,V> shows up only as a parameter type or return type and don’t handle the case where a Windows Runtime class like AmfPair declares that it implements IKeyValuePair<K,V> and this makes the Key and Value properties inaccessible from C# even without .NET Native when building debug.

We will investigate what we can do here to make the .NET Native toolchain not crash when we encounter types like AmfPair.

Is it possible for you to update the AmfPair type to stop implementing IKeyValuePair to work around this bug?

Do you have any workaround for this ?

Thanks in advanced!

[mntone]

Please wait a few days. I will inspect and solve the problem.

Thanks for using this library.

[Neno12]

Thanks for your support and your generosity to share such a great library.

[mntone]

Update library!

https://www.nuget.org/packages/ActionMessageFormat/ https://www.nuget.org/packages/RtmpClient/

[Neno12]

Wow! Awesome!

Thanks a lot for such a quick fix.

BTW, Nuget packages fails when trying to reference them in a Windows 10 (Universal app).

For now I just referenced to the Mntone.Rtmp.Windows project from my Universal Windows app and it worked.

Thanks again for your help.