Code

Re: custom .dll error

skully — Sun, 12 Mar 2006 16:38:14 GMT

Hello Anders.

Sorry for the tardy reply.

I created all of the MSIs via Regform.exe, not directly in VS.NET. Also, I'm certain that I'm using the correct version of Regform -- the one that deals with 2.0 managed code, not 1.1. At this point, I've tested the MSIs on a couple of machines and am getting mixed results. It all works on one machine that has .NET 1.1 and 2.0, Infopath SP2, etc. installed. Another machine with the same setup won't let it work.

Is it possible that Infopath is configured to "prefer" one .NET installation over another? That is, if it's configured to use 1.1 managed code, then I would get errors when it tried calling 2.0 code, right? But I'm not certain that that's how Infopath interacts with .NET managed code. At this point, I might try uninstalling Office and .NET 2.0, then reinstall. I would rather not have to do that, especially on my clients' machines. Do you have suggestions for what I might try?

Take care and thanks for your help! I'll make sure to post if I find a work-around.

Re: custom .dll error

AndersR — Fri, 10 Mar 2006 22:01:44 GMT

Hi,

how exactly do you create this MSI?

You need to use Regform.exe and not a setup project in VS.NET

hth

custom .dll error

skully — Thu, 09 Mar 2006 16:24:30 GMT

Hi,

I'm having a problem deploying a fully trusted form with managed code via an msi package. Here's the scenario. I've created a custom .dll in vs 2005 to hold code common to all of my managed code infopath forms. In the form code specific to the infopath projects, I reference this custom .dll, making sure to include "local copy" in the specs. Now, I create msi packages and install. Everything works great when I install on the same machine that I developed all this on, but when I try to install on another machine, I get an error where infopath can't create a blank form. It says the custom .dll I included in the project is invalid and that the format of the file is incorrect.

I'm wringing my hair at this point. Both my development machine and the target machine are running Infopath SP2, .NET framework 1.1 and .NET framework 2.0. The custom .dll was created in 2.0, but uses a wrapper around COM .dll "wininet.dll," which is present on both machines.

Is there something simple that I'm missing here?

Thanks so much for your help!