How does InfoPath recognised its XML - InfoPath Dev
in

InfoPath Dev

How does InfoPath recognised its XML

Last post 03-04-2006 01:03 PM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 03-02-2006 04:30 PM

    • qwer
    • Top 500 Contributor
    • Joined on 10-04-2005
    • Posts 49

    How does InfoPath recognised its XML

    My question is simple. Can somebody tell me how InfoPath recognises it's own XMLs. I know for a fact that InfoPath generated XMLs have a tag that looks like this:

    <?mso application=”Infopath.Document”>

    But how does the InfoPath application know how to interpret this tag. Is this sitting in the computer registry somewhere?
  • 03-04-2006 01:03 PM In reply to

    Re: How does InfoPath recognised its XML

    Hi Qwer,

    Great question. There are two mechanisms - Windows Shell and Internet Explorer.

    When I was working at Microsoft, a developer on my team wrote the code to launch InfoPath. When clicking on an XML file on a web page, The XML document type is handled by the text/xml key under the CLASSES_ROOT\PROTOCOLS\Filters\ path in the registry. You can turn off the launch of InfoPath by changing the "text/xml" key to ".text/xml". Don't forget to change it back though. :)

    If you install Office, the key will have a CLSID value that points to an InprocServer called MSOXMLMF.DLL. Office registers a handler for URLMON that launches InfoPath based on the mso-application PI in the XML. The actual code that launches InfoPath is in InLaunch.dll, which you can find under your installation for Office (e.g. C:\Program Files\Microsoft Office\OFFICE11). Keep in mind that Office requires Internet Explorer 6.0.

    For the Windows Shell, InfoPath.Document points to a shell handler that launches InfoPath directly from Windows. Look under CLASSES_ROOT\InfoPath.Document.1 for various keys that the handler uses.

    Hope that helps a little.
    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.