Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Intention] Remove dependence on System.Drawing #158

Closed
atruskie opened this issue Mar 23, 2018 · 1 comment
Closed

[Intention] Remove dependence on System.Drawing #158

atruskie opened this issue Mar 23, 2018 · 1 comment

Comments

@atruskie
Copy link
Member

atruskie commented Mar 23, 2018

Expected behaviour

Image rendering should be properly supported on all platforms, and A generic GDI+ error has occurred should be an error message we never see again.

Actual behaviour

Image rendering relies on a Mono shim of System.Drawing, and we regularly see generic GDI+ errors which hamstring the way we render large images. System.Drawing is also innately unparallelizable.

Any other details

The ImageSharp project looks like a good replacement.

This is an extremely low priority issue that will involve a ton of work.

http://photosauce.net/blog/post/5-reasons-you-should-stop-using-systemdrawing-from-aspnet

@atruskie atruskie added this to the Move to dotnet core milestone Mar 23, 2018
atruskie added a commit that referenced this issue Feb 17, 2020
And also migrating to using ImageSharp as drawing library.

Work done for #159 and #158
atruskie added a commit that referenced this issue Feb 17, 2020
Finished fixing build errors for dotnet core conversion

Also addressed some code style issues

Work done for #158 and #159
atruskie added a commit that referenced this issue Feb 17, 2020
Removed some code not needed now we're on dotnet core.

Also added more tests to ensure expected resources and build tasks work as expected.

Still need to fix assembly versioning.

Work done for #158 and #159
atruskie added a commit that referenced this issue Feb 17, 2020
Known bugs:
- short file name bug (se main entry)
- #289
- #288
- ImageSharp has bugs that crash with versions greater than  1.0.0-unstable0598
- ImageSharp has bug in parallel implementation so you'll find Drawing.NoParallelConfiguration sprinkled everywhere
- And another ImageSharp bug prevents us from writing text on concatenated images

All up though, the majority of things work. Yay!

Work done for #158 and #159
atruskie added a commit that referenced this issue Feb 17, 2020
And also migrating to using ImageSharp as drawing library.

Work done for #159 and #158
atruskie added a commit that referenced this issue Feb 17, 2020
Finished fixing build errors for dotnet core conversion

Also addressed some code style issues

Work done for #158 and #159
atruskie added a commit that referenced this issue Feb 17, 2020
Removed some code not needed now we're on dotnet core.

Also added more tests to ensure expected resources and build tasks work as expected.

Still need to fix assembly versioning.

Work done for #158 and #159
atruskie added a commit that referenced this issue Feb 17, 2020
Known bugs:
- short file name bug (se main entry)
- #289
- #288
- ImageSharp has bugs that crash with versions greater than  1.0.0-unstable0598
- ImageSharp has bug in parallel implementation so you'll find Drawing.NoParallelConfiguration sprinkled everywhere
- And another ImageSharp bug prevents us from writing text on concatenated images

All up though, the majority of things work. Yay!

Work done for #158 and #159
@atruskie
Copy link
Member Author

atruskie commented Apr 7, 2020

Closed (completed)

@atruskie atruskie closed this as completed Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant