Like a lot of folks, I've been investigating InfoPath since Beta 2 became available to MSDN Universal subscribers earlier this week. I've been able to get a few things to work, though the lack of documentation has made things difficult. I don't have a sense yet of the range of things I should be able to do, and unlike many of the folks who have been talking it up lately, I don't have anyone more knowledgeable about it to show me things.
Anyway, here's one thing I discovered that has made my investigation a little easier. I read in a faq that the files that are contained in the xsn file (which is really a CAB file) could also be separate files in a folder. I generated a simple xsn file, used WinZip to extract all of the files into a directory, and tried to open manifest.xsf. InfoPath complained that I wasn't opening it through the xsn file. Then I edited manifest.xsf and removed the publishUrl attribute from the document element (xsf:xDocumentClass), tried to open it again, and everything worked. This setup made it a lot easier to experiment with changing the xml, xsd and xsl files that InfoPath uses.
11:15:45 AM 
|
|
