Custom Printing: .NET and Word

TheFletch

Working on a solution to intercept printing to provide a custom dialog. This was created in .NET Framework 2.0 and using the Interops with Word. When the BeforePrint is intercepted, the dialog successfully displays. However, when the dialog is dismissed (OK, Cancel) the Interwoven Print dialog displays.

Built VB6 COM dll with a reference to iManO2K.iManageExtensibility. Added DocumentBeforePrint event in order to get/set the Cancel parameter. Event is not fired. Added BeforePrintDialog event and was able to get that event to fire. Any help on this would be greatly appreciated.

Thanks

guido1

This is something I have tackled in the past for a product, and without giving away IP I can tell you for free it's not going to be as straightforward as you'd hoped if all you are relying on is Word and WorkSite events.

Regarding your observation about the WorkSite and Word print events, here is some clarification on the behaviour:



Profiled Documents[indent]FilePrint (e.g. selecting File..Print menu, or Ctrl+P shortcut, which both display the print dialog) fires:

• WorkSite BeforePrintDialog
  
• WorkSite DocumentBeforePrint
  
• Word DocumentBeforePrint
  

FilePrintDefault action (e.g. clicking the Print button on the toolbar) fires:

• WorkSite DocumentBeforePrint
  
• Word DocumentBeforePrint
  

[/indent]Local (unprofiled) Documents[indent]FilePrint (e.g. selecting File..Print menu, or Ctrl+P shortcut, which both display the print dialog) fires:


[/indent]

• WorkSite BeforePrintDialog
  
• Word DocumentBeforePrint
  

[indent]FilePrintDefault action (e.g. clicking the Print button on the toolbar) fires:


[/indent]

• Word DocumentBeforePrint
  

Depending on what you're trying to achieve you'll have to cater for all the above combinations in your integrated environment. Note that in any case the Word object model will not give you a handle on the print dialog itself.


And even then, if you want to consider other applications (Excel, PowerPoint) you're looking at slightly different behaviour again. Also, have you considered what you might do about printing from one of the WorkSite clients (DeskSite, FileSite, etc)

Best of luck!