Paul Knopf

With Yocto, the .NET publishing should touch any native libs. You should build/package the libQmlNet.so into the Yocto distribution like any other recipe. As for adding dotnet into the Yocto...

Exit code 139 is a segfault. Can you grab the core dump, and get me a stack trace?

See [this](https://github.com/qmlnet/qmlnet/pull/115#issuecomment-483024188) comment about adding support for ARM. @ed10vi, sorry for the delay, back that segfault looks unrelated to Qml.Net.

We don't support Qt 5.9, but I suspect that we could easily support it if you remove the ```JsNetArray``` support. It should be easy to carve that out in the...

Looks like ```qWaitFor``` isn't supported in 5.9. See [here](https://doc.qt.io/qt-5/qtest.html#qWaitFor). There may be more things that aren't present, you'll have to just refer to the docs.

That isn't currently supported. How would it look? Something like this? ```csharp [ClassInfo("Prop", "Value")] public class NetClass { } ```

You are declaring the ```NotifySignal```, but you aren't activating it when the value changes. See this: https://github.com/qmlnet/qmlnet/blob/develop/src/net/Qml.Net/Signals.cs

Can you give me a minimal repo, maybe a repository somewhere I can clone?

Hey guys, circling back to clean up issues. First, I would avoid activating properties in background tasks. It should only be done in the GUI/Main thread. Second, it's unclear if...

Ya, I think we should add a check to ```DiscoverOrDownloadSuitableQtRuntime``` to ensure the proper VC++ lib is installed. Using MinGW would be ideal, because we can then ensure our Qt...