Added Aspose.Drawing as an alternative to System.Drawing

[Sergey-Vlasov]

Summary

Added Aspose.Drawing as an alternative to System.Drawing. (Also reordered ImageSharp link and added license type to match the docs repository.)

[ghost]

Tagging subscribers to this area: @dotnet/area-system-drawing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Summary

Added Aspose.Drawing as an alternative to System.Drawing. (Also reordered ImageSharp link and added license type to match the docs repository.)

Author:	Sergey-Vlasov
Assignees:	-
Labels:	area-System.Drawing, community-contribution
Milestone:	-

[learn-build-service-prod]

Learn Build status updates of commit 32ef544:

✅ Validation status: passed

File	Status	Preview URL	Details
includes/drawing.md	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[MSDN-WhiteKnight]

Was this discussed with any maintainers? I don't like that API docs host ever-growing catalog of graphics libraries, including commercial ones. The disadvantage is that if this list becomes longer, it becomes harder for reader to choose which library to use, as we are not providing any sort of details for which scenario which library is better. I think this list should either include only a reasonably short list of most commonly used libraries, or link into some external resource that lists more libraries and provides some details that help reader to choose between them.

[Sergey-Vlasov]

@MSDN-WhiteKnight

It was approved by Bill Wagner and Genevieve Warren:
dotnet/docs#37651

Of all alternatives, Aspose.Drawing most fully implements System.Drawing functionality and uniquely provides direct migration without rewriting existing code.

[gewarren]

Just to clarify, I didn't technically approve dotnet/docs#37651.
@BillWagner Who should we consult on this from the product team?

[BillWagner]

Just to clarify, I didn't technically approve dotnet/docs#37651. @BillWagner Who should we consult on this from the product team?

Let's start with @richlander