InfoPath Dev

InfoPath 2010:

 How can I  create a button that publishes to PDF?

Instead of the user going to "File" --> "Info" --> "Publish as PDF or XPS", I just want them to hit a button on my view an it prints to PDF. 

 How do I invoke the "Publish as PDF" function in a button?

You'll have to write code, I'm afraid, and the form will need to be filler and full trust. Here's an MSDN page that has a code sample.

Beautiful!

The VB code is easy enough to follow what it is doing.  So I copy and paste into VSTA, but get a blue squiggly line under it and "Type 'ExportFormat' is not defined" message.

It has been years since i did any coding.  do I have to import any libraries or anything?  How was I supposed to define ExportFormat?

 ~Dustin.

Is your form set to be a Filler not a Browser form? From the MSDN doc:

This type or member can be accessed only from code running in forms opened in Microsoft InfoPath Filler.

My form type was set to 'InfoPath 2003 Filler Form' as I started this in InfoPath 2003, just recently got upgraded.  I selected 'InfoPath Filler Form.'

 Also per the MSDN doc, I ensured I had 'Full Trust' selected.

Still build errors when I preview the form.

MSDN doc says i should be working in the Namespace: 'Microsoft.Office.InfoPath.'  When I check, my code says:

<InfoPathNamespace("xmlns:my=""http://schemas.microsoft.com/office/infopath/2003/myXSD/2012-03-05T14:10:56"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:ns1=""http://schemas.microsoft.com/office/infopath/2003/myXSD/2012-03-09T13:26:16"" xmlns:xhtml=""http://www.w3.org/1999/xhtml"" xmlns:xd=""http://schemas.microsoft.com/office/infopath/2003""")> _

Just guessing this is a problem, as it references the 2003 schema.  Is there a way to 'upgrade' my namespace without losing everything?  i.e. if I copy and paste new namespace into here will it hose everything?

~Dustin.

I started this form in InfoPath 2003.  Rather than try to gut it and replace with 2010 functionality, I'm starting a blank project in 2010 to test this functionality.

I throw the code in my brand new blank form and get a vb error:

'MustOverride' cannot be specified on 'Public MustOverride Sub Export(fileLocation As String, format As <unrecognized type>)' because it is in a partial type that is declared 'NotInheritable' in another partial definition.

So after quadruple reading the MSDN doc, I suspect trusts to be a problem.  the new InfoPath doc is set ot Full Trust, I even give it a signed security certificate.  I try to open the form in Filler and get:

"The form template cannot be opened, because the system administrator has disabled opening form templates that require full trust."

Think this is associated with the previous "MustOverride" error?

 ~Dustin.

Ummm.... where are you putting your code, exactly? On a button? You opened the button properties and selected edit code and added the code to the button clicked event?

No.  I figured it was a Public Sub, so added under the default Public Class FormCode.  See below.

Screenshot: http://rookery9.aviary.com.s3.amazonaws.com/14254500/14254724_48db_625x625.jpg

Nothing under the Click event yet.

~Dustin.

See, all I was figuring was you'd add a click event and add this sample line from the MSDN page.... I don't know why you are overriding Export?

Me.CurrentView.Export("C:\MyView.pdf", ExportFormat.Pdf)

I was thinking I had to include all the code on the MSDN page.  Works now.  Thanks.

Works with the exception of the security issue; I now have to convince my sys admin to allow signed InfoPath forms to run in Full Trust.  Don't suppose you could help there (ha ha)?

~Dustin.

Oh, that will be fun for you, won't it? Glad you got the code working, though.

Hilary,

This solution works perfectly.  Is there a way to achieve this but have the save as box appear and allow the user to select where the pdf file saves to? 

 You can use a SaveFileDialog (built into .NET) to allow the user to select a file name, and then provide that value to the Export() method.

The code sample on the MSDN page shows how to open a stream for the selected file, but instead of doing that, you can access the .FileName property when ShowDialog() completes to get the path to use.