You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree. Now that WinUI 2.8 is compiled with Hybrid CRT, I will follow for WinUIEdit.Uwp. WinUIEdit (for WinUI 3) is already compiled with Hybrid CRT. I will enable the same on UWP in the next update.
Just a question: having changed some sources (see pull request #14 ) I had a hard time as a C# WinUI3 user to get my head around whats going on there.
Looks for me like there are at least two different worlds which can't interoperate on the source level as a developer would like to use it (winrt:: class definitions and the "other" stuff).
Is this the result of targeting UWP? Means: could be the source much "cleaner" if UWP would be dropped as a target?
PS: as you've might guessed - I only care about the future which should be WinUI3 ;-)
Using Hybrid CRT would allow this awesome control to be used both in UWP and XAML Islands v1, without the need of VCRTForwarders.
The text was updated successfully, but these errors were encountered: