Strong Naming InfoPath Managed Assemblies

[JohnD]

Hi there

I'm developing a .NET (C#) codebehind for an InfoPath form, using InfoPath
2003 SP1 and Visual Studio 2003 EntArch.

Due to various reasons (mostly because I'm wanting to use Isolated Storage -
long story!) I need to add a strong name to the DLL file assembly that Visual
Studio generates. I'm just using the AssemblyKeyFile attribute in
AssemblyInfo.cs. This, however, doesn't seem to be liked by InfoPath, which
throws an error saying:



InfoPath cannot open the selected form because of an error in the form's code.
Request failed.



whenever I load the form in preview mode.

I suspect I need to update the manifest.xsf file inside the published XSN to
point to the right assembly version, but I'm not sure whether this is
correct, and if so, how to do this.

Has anyone else managed to strong name a managed InfoPath assembly?

Thanks!

- John

 

[JohnD]

Hi

We managed to resolve the issue - it's a pretty simple one actually. Adding
the assembly attribute System.Security.AllowPartiallyTrustedCallersAttribute
made it work fine.

Hope this helps someone else out there.

- John