UWP Crashes at Startup when built in Release mode when using some Icon Packs about mahapps.metro.iconpacks

[punker76]

@timunie Generating the path data directly is not possible, because of the different source of the icons. That’s why I didn’t publish my converter.

@MarkIvanDev I will try and look if the resx can help here.

[punker76]

@MarkIvanDev Idk exactly why this happens. I can see that the XamlTypeInfo for Debug is different to Release but Idk why...

[punker76]

@MarkIvanDev If I disable "Compile with .NET Native tool chain" the app runs fine. That's the reason why I'm hate UWP!

[MarkIvanDev]

Yes. It only runs when not compiling with .NET Native toolchain. I have also checked what is different with the icons with bugs from the ones that work correctly, and nothing stands out that might cause the problem. Although, I have read somewhere that there is a limit to the length of a string in a library. Maybe it is having problems with the massive icon data for those icon packs?

[punker76]

@MarkIvanDev

Although, I have read somewhere that there is a limit to the length of a string in a library. Maybe it is having problems with the massive icon data for those icon packs?

But it's working on WPF. You can see it in action with the IconPacks browser.

[MarkIvanDev]

@punker76

But it's working on WPF. You can see it in action with the IconPacks browser.

Yes. Maybe the string limitation is only enforced in .NET Native? Or .NET Native has a problem with a large number of static strings? I have tried creating a new package for UWP with the problematic icon packs using the same path data, but it still triggers the error stated above. But when I put the data inside a sqlite database and read from that, the error does not show and it compiles and runs successfully when using .NET Native.

[timunie]

Interesting finding. Do you think source generators may be helpful in that case?

[MarkIvanDev]

Interesting finding. Do you think source generators may be helpful in that case?

If the source generators will only generate the same classes with the same static strings as data, I don't think it will make a difference. But I think if the path data will be put in resource files (.resx), I think we can work around the static string length limitation

[timunie]

No, the idea was to generate the PathGeometry directly.

[MarkIvanDev]

@MarkIvanDev I will try and look if the resx can help here.

If there is anything I can help with, I'd love to.