var printItem = new MenuItem { Header = "Print..." };printItem.Click += (sender, e) => {
var reportSection = new EmbeddedVisualReportSection(this); var report = new Report(); report.Sections.Add(reportSection); report.Export(OutputFormat.XPS, @"c:\test.xps"); // Exports fine the entire grid. report.Print(); //throws CrossThread exception
};gridMenu.Items.Add(printItem);
What could be the reason?
More information:
App is multithreaded.
report.Print(false, false) is printing. But printing without PrintDialog does not make sense for us.
Can you look into this issue please?
This link might help:
http://stackoverflow.com/questions/2972513/printdialog-in-multithreaded-wpf-window-thrown-targetinvocationexception
I would appreciate any feedback on that issue.
Thanks
Hello Dierk,
The grid can be on any thread. The framework does not allow property access across threads. In this case it is trying to access the Report object in another thread and that is currently not supported. You need to go back to the main thread.
Thanks,
Sam
Thanks.
Hmm .. you 're loosing me here. Could you please point out - may be on the code of my initial post - which lines should be executed in what thread?
Would be great...
The link that you provided accurately explains the problem; there is a bug in the WPF PrintDialog class where it attempts to use the MainWindow which in your case is on another thread. The Report class uses the WPF PrintDialog class when told to show the print dialog so I think the only available workaround until MS fixes the bug in the PrintDialog is to do something like what was marked as an answer in the stackoverflow link you provided. That is, you would show the print dialog using something like the code linked to from that post and then you would set properties on the ReportSettings such as the PrintQueue, PageRange and PageSize.
I see. I'll look deeper into and will get back to you in case.
As Andrew pointed out, the issue is related with Microsoft PrintDialog bug, and our Report class used it.
As I stated PrintingDialog issue has been resolved for now, but I described the different issue about how grid is printed or exported to XPS file. It is not related to printing since exporting to xps does the same thing. Please see couple posts above.