Repackage files? - InfoPath Dev
in

InfoPath Dev

Repackage files?

Last post 01-26-2007 09:45 PM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 01-26-2007 05:49 AM

    Repackage files?

    I am trying to convert a template to a fully trusted form using the help file associated with InfoPath 2003 SDK, ipsdk.chm. I did a search for regform.exe and am reading the "Understanding Fully Trusted Forms" and am going through the step by step process of "Manually Creating a Fully Trusted Form". I've done all the steps but I'm hung up on #9 which states:
    quote:
    Repackage the files into the .xsn CAB format with a tool such as makecab.exe.
    Note Although InfoPath design mode supports repackaging the form files into an .xsn file, doing so will revert the form to a URL-based form. For this reason, you must repackage the files manually to avoid overwriting your changes to the form files.


    I downloaded Microsoft's Cabinet Software Development Kit but have no clue how to proceed or if this is really what I need to be doing in the first place. I'm trying to avoid the ADO Security Warning:This website is using your identity to access a data source. If you trust this website, click OK to continue, otherwise click Cancel.

    If I was the one using this form I would know that the data source is safe and I would just click OK. But I'm sending this form out to many users in my company that tend to freak out at Error messages.

    So my question is, am I on the right track and if so, how the heck do I use the Cabinet Software Development Kit? :-)
  • 01-26-2007 09:45 PM In reply to

    Hi JLProgrammer,

    Why are you re-cabbing the file? Why not just use regform with the /F Full Trust switch? That's what we use. Makecab is really only needed for repackaging for instance if you have a build process or some other thing that needs to recreate XSNs programmatically. In practice, we never use makecab.exe except in our build process and we build a lot of forms.

    Keep in mind that the main downside of Full Trust via regform MSIs is that you will lose the auto-update feature and that means you may periodically have to send out refreshes.

    As for the ADO security warning, I'd like to understand what the scenario is again. The form is trying to access a database? Does the form have any code?
    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.