.NET Framework 1.1 required for deployment?

[todd.thompson]

I have recently found out that a managed code Infopath form requires .NET
framework 1.1 or better (this makes obvious sense). Luckily I can migrate
all of the business logic to a web service to dumb down the frontend of the
form. I re-developed the form outside of VS2005 (without even any vbscript),
but for some reason my users are still getting the .NET 1.1 requirement
error. Is there any scenario where I can develop and publish an Infopath
form for other users that do not have .NET framework 1.1 or better? We do
not have an SMS server, so any .NET framework deployment would require
significant resources.

Thanks,

Todd

 

[Lanevictor]

I have recently found out that a managed code Infopath form requires .NET
framework 1.1 or better (this makes obvious sense). Luckily I can migrate
all of the business logic to a web service to dumb down the frontend of the
form. I re-developed the form outside of VS2005 (without even any vbscript),
but for some reason my users are still getting the .NET 1.1 requirement
error. Is there any scenario where I can develop and publish an Infopath
form for other users that do not have .NET framework 1.1 or better? We do
not have an SMS server, so any .NET framework deployment would require
significant resources.

Thanks,

Todd

Hi Todd,

it seems that your machine is missing Office Primary Interop assemblies
also which version of service pack is applied on the client machine it
should sp2 and the order of install on the client machine should be

Office 2003 SP2
..net framework
Office Primary interop assemblies (PIAS). refer to
http://support.microsoft.com/kb/828087 for the more details in
pre-requisites of install.

this is the ideal configuration for the client machine and the error
which you are getting does not seem that it would be because of only
..net framework missing on the client machine it may be either of any
above mentioned components missing on the clients machine.

try installing the above configuration on the client machine and check
if the problem occurs and if you have developed a infopath solution
using VS2005 then you would certainly need .net framework 2.0 installed
on the client's machine.

so ideally you would need following configuration at clients machine

1) .net framework 1.1 (PIAS are dependent on it)
2) .net framework 2.0 our solution is developed using VS2005
3) Office 2003 SP2 (if not installed)
4) Install the PIAS

PS: path to download PIAS
http://www.microsoft.com/downloads/...3A-AC14-4125-8BA0-D36D67E0F4AD&displaylang=en


Cheers!!
Lane

 

[todd.thompson]

Thanks,

Todd

Hi Todd,

it seems that your machine is missing Office Primary Interop assemblies
also which version of service pack is applied on the client machine it
should sp2 and the order of install on the client machine should be

Office 2003 SP2
..net framework
Office Primary interop assemblies (PIAS). refer to
http://support.microsoft.com/kb/828087 for the more details in
pre-requisites of install.

this is the ideal configuration for the client machine and the error
which you are getting does not seem that it would be because of only
..net framework missing on the client machine it may be either of any
above mentioned components missing on the clients machine.

try installing the above configuration on the client machine and check
if the problem occurs and if you have developed a infopath solution
using VS2005 then you would certainly need .net framework 2.0 installed
on the client's machine.

so ideally you would need following configuration at clients machine

1) .net framework 1.1 (PIAS are dependent on it)
2) .net framework 2.0 our solution is developed using VS2005
3) Office 2003 SP2 (if not installed)
4) Install the PIAS

PS: path to download PIAS
http://www.microsoft.com/downloads/...3A-AC14-4125-8BA0-D36D67E0F4AD&displaylang=en


Cheers!!
Lane