S
Schemer
Hello,
We have some test apps that print images to file using various printers.
The test app runs as expected under the (default) 1.1 Framework. When we
try to run with the 2.0 framework, we get "The handle is invalid" errors.
at
System.Drawing.Printing.StandardPrintController.OnStartPrint(PrintDocument
document, PrintEventArgs e)
at
System.Windows.Forms.PrintControllerWithStatusDialog.OnStartPrint(PrintDocument
document, PrintEventArgs e)
at System.Drawing.Printing.PrintController.Print(PrintDocument document)
at System.Drawing.Printing.PrintDocument.Print()
at MegaCorp.Printing.IcePrinting.PrintInBackground()
at MegaCorp.Printing.IcePrinting.Print()
at MegaCorpTest.Printing.IcePrintingMain.IcePrintingTests(TestCaseData
TestDataBase)
Adding a testapp.exe.config file with the section
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" />
</startup>
</configuration>
is the only change we make.
We are trying to print from a class derived from PrintDocument; our
PrintPage handler is never called when the test fails.
Is this a driver problem, or is there maybe something we can do to make this
work for our customers using the 2.0 framework?
Thanks for any advice...
We have some test apps that print images to file using various printers.
The test app runs as expected under the (default) 1.1 Framework. When we
try to run with the 2.0 framework, we get "The handle is invalid" errors.
at
System.Drawing.Printing.StandardPrintController.OnStartPrint(PrintDocument
document, PrintEventArgs e)
at
System.Windows.Forms.PrintControllerWithStatusDialog.OnStartPrint(PrintDocument
document, PrintEventArgs e)
at System.Drawing.Printing.PrintController.Print(PrintDocument document)
at System.Drawing.Printing.PrintDocument.Print()
at MegaCorp.Printing.IcePrinting.PrintInBackground()
at MegaCorp.Printing.IcePrinting.Print()
at MegaCorpTest.Printing.IcePrintingMain.IcePrintingTests(TestCaseData
TestDataBase)
Adding a testapp.exe.config file with the section
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" />
</startup>
</configuration>
is the only change we make.
We are trying to print from a class derived from PrintDocument; our
PrintPage handler is never called when the test fails.
Is this a driver problem, or is there maybe something we can do to make this
work for our customers using the 2.0 framework?
Thanks for any advice...