Port System.Printing to C#

System.Printing is currently a C++/CLI assembly. There would be advantages to rewriting it in C#, as detailed in this comment: https://github.com/dotnet/wpf/issues/5305#issuecomment-922067322 CC @ThomasGoulet73

I haven’t reviewed all the code in the project line-by-line. There is obviously some P/Invoke, some COM, and some native types in AsyncNotifyUnmanaged.cpp, which should make the port potentially complex, but not impossible.

Are there critical blocking issues that would make a port to C# impossible? What are the reference cycles related to System.Printing and would those still exist following a C# port?

Or is this primarily about the effort of rewriting thousands of lines of C++/CLI in C#?

[bgrainger]

FWIW, in my mind this would be a line-by-line port (by hand) of each file, preserving the existing comments and semantics exactly as they are in the C++/CLI. (Any deviation from the C++/CLI behaviour in the port would be considered a bug.) This would provide a base upon which bug fixes, optimisations, etc. could be made.

[kant2002]

Would be good if some test application/test was written or collected, because that rewrite should be tested not only manually, but also on working code. That will helps a lot with surpise issues later on.