Geeks With Blogs
Molnar Tibor blog

If during the installation of a workflow feature using InfoPath forms you receive a warning message in the form 'The assembly assmbl1.dll from form template templ1.xsn(urn:....) conflicts with a same named assembly in form template templ2.xsn(urn:....). ' the reason is that one of the Info Path forms being deployed contains in the .xsn file an assembly which has the same fully qualified name as one of the already deployed assemblies. One reason could be that the assembly version property of the code behind project of an InfoPath form is hardcoded and not dynamically generated and you install the second version of the form.

Posted on Monday, February 18, 2008 9:43 AM SharePoint 2007 | Back to top


Comments on this post: Assembly form a template conflicts with a same named assembly form another template during MOSS workflow deployment

# re: Assembly form a template conflicts with a same named assembly form another template during MOSS workflow deployment
Requesting Gravatar...
Open InfoPath forms with a zip software and check conflict dlls. If both xsn files includes same dll, open visual studio projects and remove conflict dll references. Put your dll into GAC and Framework folders under windows directory and reference dll from assembly folder in your projects. After publish successful, open your xsn files with zip editor and make sure not contain conflict dll. Then upload form templates, no conflict occurs.
Left by Ergin BULUT on Nov 23, 2008 9:37 PM

# re: Assembly form a template conflicts with a same named assembly form another template during MOSS workflow deployment
Requesting Gravatar...
Here is what the solution for it.

http://praveenbattula.blogspot.com/2010/09/assembly-from-form-template-conflicts.html
Left by Praveen on Oct 09, 2010 4:40 AM

Your comment:
 (will show your gravatar)


Copyright © Molnar Tibor | Powered by: GeeksWithBlogs.net