How to manually produce XSN - InfoPath Dev
in

InfoPath Dev

How to manually produce XSN

Last post 05-31-2007 08:34 AM by abdelghafour. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 05-27-2007 02:12 AM

    How to manually produce XSN

    I'm trying to automate the creation of XSN file and MSI file from Visual Studio sources with BATCH file.

    the XSN file is generated (through MakeCab) but is smaller than the file generated with Infopath itself from the same sources (205 kb against 208 kb).

    Extracting the XSN files gives the same result.

    the generated file (with MakeCab) brings an error when trying to create MSI through RegForm but not the file generated with infopath.

    For MakeCab, I use ddf-file with the syntax :

    .OPTION EXPLICIT

    .Set CabinetNameTemplate=myfile.xsn    

    .Set CompressionType=MSZIP

    .Set UniqueFiles=Off

    .Set Cabinet=On

    .Set Compress=on

    .Set DiskDirectory1=mydirectory

     any idea?

     thanks

     

    Infopath 2003 SP1

    visual studio 2003 - framework 1.1

    Infopath 2003 SP1; Framework 1.1; Visual Studio 2003; Vb.net
  • 05-29-2007 01:36 PM In reply to

    Re: How to manually produce XSN

    Hi abdelghafour,

    Don't work about the size  being different - we unpack and repack XSNs all the time, and I guess Microsoft is just using an old version of the cab compression when they make their XSNs, we always notice the size difference, too.

    I'm not sure about your other problem tho.  Does the XSN that you create open in InfoPath correctly?  If so, then I don't see why you would have any problem with the RegForm not working.  You might try upgrading to .NET 2.0 and see if that helps anything.

    Matt Faus / Microsoft InfoPath MVP
    Qdabra® Software / Streamline data gathering to turn process into knowledge
  • 05-31-2007 08:34 AM In reply to

    Re: How to manually produce XSN

    Hola,

    it wouldn't matter for me that files are differnt sizes if Regform was not bringing errors.

    Regform can't process the XSN file unless I open it in design-modus and save it again.

    I can't upgrade to NET 2.0.

    Infopath 2003 SP1; Framework 1.1; Visual Studio 2003; Vb.net
Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.