Luke 37095 Posted March 29, 2023 Share Posted March 29, 2023 For those doing image processing, ImageProcessor.ImageEncoder has now been changed to ImageEncoders (plural), because with the introduction of libvips, there can be multiple encoders available. Currently at startup I believe you make decisions when choosing skia or imagemagick, you should update that code to look like the following: var serverImageEncoders = ImageProcessor.ImageEncoders; if (serverImageEncoders.Any(i => i.Name.IndexOf("skia", StringComparison.OrdinalIgnoreCase) != -1)) { // init skia support here } else if (serverImageEncoders.Any(i => i.Name.IndexOf("magick", StringComparison.OrdinalIgnoreCase) != -1)) { // init image magick support here } @roaku @chef @pünktchen 3 Link to comment Share on other sites More sharing options...
chef 3746 Posted March 31, 2023 Share Posted March 31, 2023 (edited) @Luke is this only in the beta? When I load .27-beta, "ImageEncoders" does exist in ImageProcessor. It is still the singular "ImageEncoder" Edited March 31, 2023 by chef Link to comment Share on other sites More sharing options...
Luke 37095 Posted March 31, 2023 Author Share Posted March 31, 2023 11 minutes ago, chef said: @Luke is this only in the beta? When I load .27-beta, "ImageEncoders" does exist in ImageProcessor. It is still the singular "ImageEncoder" Yes you need the updated nuget package. Link to comment Share on other sites More sharing options...
chef 3746 Posted March 31, 2023 Share Posted March 31, 2023 @Luke Right sorry about that, I swapped my projects over to my new laptop and Nuget was apparently broken. It seems to have updated properly now. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now