Max Katz
Max Katz
This feature definitely needs more attention, as it is making it unreasonable difficult to work on multi-target libraries and applications. Note, this issue and my comment is not about having...
@dsplaisted we now have a target framework for Browser platform, which I am glad to see. It is now possible to at least dedicate a plain "net8.0" target (without any...
@dsplaisted thank you for sharing this spec. Looks promissing. The latest use case I found where we need "net8.0-linux", is MAUI Essentials project, Which has compile-time implementations for different essential...
This one is relatively big bug, as OneWayToSource is commonly used on read-only properties
@mattleibow hi! IIRC there was a document that tracks all breaking changes between 2.88 and 3.0 but can't find it now. Do you still have it?
If anybody want/can test these packages in your apps with updated SkiaSharp to 3.0 previews, I would appreciate help with testing. Before agreeing on this approach with reusing the same...
We don't need that reflection after we use builds with this PR included https://github.com/mono/SkiaSharp/pull/2756 ~I still don't know what's wrong with antialiasing in 3.0. FilterQuality is obsolete, but as I...
That's a normal .NET library with Avalonia reference. To add extra platforms, you either keep everything the same and PInvoke native APIs, or add a native platform target, like "net6.0-android"....
@mattleibow I went through breaking changes page, and these changes were the low hanging fruits of what can be backported from 3.0 to 2.x. Which is also enough for Avalonia...