What would you recommend instead of System.Drawing in a web app?
Any of the ones listed in the article?
Re:.NET Core Image Processing
by jsingleton on Friday January 20, 2017 @09:45AM
(#13444098)
Unless you have a good reason to then I would recommend against rolling your own (with any library). Use an existing cloud service that specializes in it.
Re:.NET Core Image Processing
by gjjrfcbugxbhf on Friday January 20, 2017 @02:57PM
(#13446537)
Most b2b saas products have a specific reason to not use a third party for everything - their customers don't want their data sprayed everywhere. Add to that anyone with a government contact.
Re:.NET Core Image Processing
by statictype on Friday January 20, 2017 @09:56AM
(#13444193)
Nice list. Any idea on the status of IronPython?
Is there any road map on getting it into Core?
[OT] I didn't know about this repo. Its so amazing! Thanks so much for maintaining it :)
Re:.NET Core Image Processing
by jsingleton on Friday January 20, 2017 @04:42AM
(#13442614)
You're welcome. I'm glad it's useful. It's a community effort so feel free to submit a PR or an issue.
P.S. There used to be a separate website but since GH broke how pages work the domain now just redirects to the repo.
NB: You shouldn't use System.Drawing in a web app. It can lead to memory leaks and lots of pain. Even the newer WPF equivalents are not safe for use on a web server.