-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Supersede System.Printing
#7259
Comments
I don't see any actionable justification. You say the current API is "very legacy and very limited". Can you be a bit more specific and list some problems or features you are missing? With WPF not being cross-platform, rewriting printing to be cross-platform sounds like out of scope for WPF. |
It is. In general, on the one hand the implementation is done in C++/CLI and is still based on many things, which probably wouldn't be done that way nowadays (I don't want to say that COM is bad).
There are many things that are not guaranteed in the current library, which I mentioned in my feature request above, such as support for IPP. So a direct implementation that is not strictly based on the Windows APIs.
Of course, WPF is windows-only. However, I think we should find a unified consensus between Winforms, WPF, MAUI and other application areas (such as cross-platform desktop frameworks like Avalonia or UNO). |
Please first fix this printing bug: #3546 next #4000 after that #6296 It would help if the team actually fixes (xps/printing) bugs which are open for YEARS already instead of starting new projects and stops halfway. |
@wstaelens This issue describes a completely new API, which has nothing to do with the current |
WPF uses the library
System.Printing
, which is WPF Only, but also contains C++/CLI code.That we should replace C++/CLI code is generally known. However, my suggestion is to create a new general purpose API for printing. For this I have already created a feature request in dotnet/runtime (see dotnet/runtime#75628).
I would like to get feedback on this API and its use case in WPF.
The text was updated successfully, but these errors were encountered: