David
David
Hey @modula2019, the workaround I provided was an evolution of my investigation to understand what was the issue. It has the advantage to not alter the code of your app...
This got mitigated by #192, but it's still not properly aligned with UWP.
This is causing some troubles again with this: ```xaml ``` If in the callback of the `DisplayTemplateProperty` you do something like `Template = DisplayTemplate`, then the `OnApplyTemplate` will be invoked...
/azp run
We should actually even give ability to read the full logs (which should probably always be stored on disk in a `.uno/logs` folder)
Suggestion from @Takoooooo : We agreed with @NVLudwig that this would be good for 6.5. However we need to investigate with @Jen-Uno the errors we are getting from telemetry and...
IMO We should distinguish 2 cases: 1. The API is in the same solution of the client, i.e. "local" 2. The API is a "external" # Local API In that...
Note: AN hypothesis would also be that MVUX's generator is executed **after** uno's type info generator.
> **All** Roslyn generators are given the same compilation. So there is no concept of order. No generator can see the output of another. Yes ... unfortunately > The safest...
@ajpinedam For now we should only validate that the issue is indeed because the bindable generator is not ran _after_ MVUX's VM generator (or more precisely is run _using the...