InfoPath Dev

Hello,

I'm having a hard time tailoring some of my managed code Infopath forms. I want to produce some with VS 2005 and deploy on .NET 2.0 and others with VS 2003 and deploy on .NET 1.1. I'm having no problem deploying with 2.0, but I'm having trouble creating MSI's targeting 1.1 Here's what I'm trying:
1. I create a solution within VS 03 and get all the dll's and the xsn.
2. I find the 03 version of regform (the one from 9/2004
3. I copy this and place it in the folder with the managed code dlls and xsn.
4. I create a command line in XP and navigate to the directory with my dll's and xsn
5. I try running the regform tool (again, it's the one from '03 toolkit)

Then I get the error that the regform utility can't run because it "does not support Microsoft visual studio version 8."

Is there a way to set up the command line utility or the regform to target .NET 1.1 instead of 2.0? If I have both VS '03 AND '05 installed MUST I use only the newest form of the regform utility? An earlier post in the forum mentioned that someone had to uninstall both '05 and '03; is there a simpler (and more efficient) solution? I need to be able to deploy for both environments at this time.

Thanks so much for your help!!!!

skully

Hello,

I´m not sure if the following can help you but I know from one of the "Tips & Tricks" from this site that you have to direct a program specifically targeting the .Net 1.1 or .Net 2.0 framework.
This can be done using a so called "*.exe.config" file. This file is an XML file and has the following content for .Net 1.1:

<configuration>
<startup>
<requiredRuntime imageVersion="v1.1.4322" version="v1.1.4322" />
<supportedRuntime version="v1.1.4322" />
</startup>
</configuration>

In your case this file must have the name: "regform.exe.config" and you have to store it in the same directory like your "regform.exe"

HTH

Karsten,

You solved my dilemma!
The .config file approach works in two respects; one, for letting me specify how the regform utility's working and, two, how the client's machine is configured as well. Problem solved. Thanks so much for your help and very prompt reply.

Skully

Karsten, Skully,

I cannot get this to work unfortunately. I am trying to create an MSI and am still getting the 'won't support V8' message. Good thing I still have a machine with only VS 2003 on, but not exactly convenient!

If you have any ideas...

Clive