Paul Selormey

@FabioFerrettiMoodys Sorry for the delay. Please update your project for review.

`netcoreapp3.1` is supported, however support for `netcoreapp3.0` is not planned.

@pombredanne That is the implementation provided by the Google engineers, and the reason is well documented. See the comments: https://github.com/google/brotli/blob/master/csharp/org/brotli/dec/Dictionary.cs

@amine-aboufirass I will check and get back to you - for sometime now, I have not tested this sample.

@amine-aboufirass Are you trying the **WpfTestOtherSvg** sample? It seems it is the only sample using the **WebViews.Core** for the Edge Browser. Please avoid this sample, it is for comparing results...

Please provide more information. `new Rect(x, y, width, height)` does not mean much unless you explain how you created it, relative to the SVG image.

@dongzhaosheng73 Have you considered using threads? (see the `WpfTestThreadSafety` sample and other samples.) Also, the controls provide concurrency/asynchronous methods like ```cs public bool Load(Uri uriSource, bool useAsync = false) {}...

> Can asynchronous operations be done in xaml code? I do not know of any such possibility. > I think the biggest bottleneck is the caching problem There should be...

> I wonder if you can add a caching mechanism to svg controls, if the same resource exists in memory. What do we cache in this case? (SvgDocument, Drawing, DrawingVisual)

> Would MemoryStream be any better? I think the performance bottleneck is in the IO operation, > directly from the memory stream. Will not work well for all input types.,...