Developer forum

Find it in Nuget: https://www.nuget.org/packages?q=dynamicweb+imaging

Then you can exchange the imageglue with the magicscaler version.

They both use the same implementation of webp though - which is highly recommended to use (&format=webp) which defaults back to jpeg if browser does not support it.

BR Nicolai

Hi Nicolai,

Thank you. I am reading my emails out of order. My goal is to try and see if this thread is solved by MagicScaler https://doc.dynamicweb.com/forum?PID=1605&ThreadID=72603

Additionally if we can stop having that license warning/error when submiting SVG files through GetImage.

Thanks,

Nuno Aguiar

Hi Nicolai,

Thanks. If I remember correctly, adopting MagicScaler is a stepping stone with the .Net Core migration. Are there any different expectations by using one vs another in terms of performance OR quality of the result?

Best Regards,

Nuno Aguiar

MagicScaler is a bit faster - but since images are cached, you will not note the difference. On very large jpegs you can see it on the first resize - but results are cached..

Quality in jpeg compression is better on magicscaler. But webp is the way forward, and both providers use the same webp engine so no difference.

Imageglue version supports a lot of formats where magigscaler is limited in primarily web formats (png, jpeg, gif, webp, bmp etc.).

And yes - magicscaler is .net core compatible - ImageGlue is not. But it has since been released in a .net core compatible version - we do not know yet if that will be adopted for DW10.

Thanks Nicolai