Paul Knopf

``` NetAbstractItemModelRoleNames.cpp ..\QmlNet\QmlNet\qml\NetAbstractItemModelRoleNames.cpp(3): error C7555: use of designated initializers requires at least '/std:c++latest' ..\QmlNet\QmlNet\qml\NetQModelIndex.cpp(7): error C7555: use of designated initializers requires at least '/std:c++latest' ..\QmlNet\QmlNet\qml\NetQModelIndex.cpp(12): error C7555: use of designated...

Merged.

It looks like we need to add ```QT += widgets``` into [this](https://github.com/qmlnet/qmlnet/blob/develop/src/native/QmlNet/QmlNet.pro) file. Do you have a minimal ```Main.qml``` to reproduce so that I can test it locally?

That would be an awesome add! I think its implementation should be straightforward as well. ``` public class QmlProperty { // PInvoke for QQmlProperty: http://doc.qt.io/qt-5/qqmlproperty.html } public interface IQmlPropertyValueSource {...

I'm marking this issue as "todo", as I will likely implement it at some point in the future. However, I'm open to pull requests. I think this would be perfect...

Note, this is for the internal interop only, not the classes defined in your implementation.

No, unfortunately. The properties/methods that are dynamically invokable must be made visible to the meta object system. This is only done via Q_PROPERTY and Q_INVOKABLE (or slots).

This would also theoretically improve the performance of the interop between C# and QML, since we wouldn't have to wrap everything with a QVariant, and we wouldn't have to dynamically...

This is AOT, but in the opposite direction. Basically, instead of dynamic ```QObject``` instances that dynamic methods/properties, we will generate C++ for typed ```QObject``` derivatives that can be instantiated in...

I'm not sure what you mean by "QML files". I'm only referring to generating the QObject equivalents for each .NET object you wish to generate AOT. Some .NET types could...