Although it could be masked by another problem, I doubt the exception is lying to you about the manifest mismatch issue. There's a good chance that finding what is at the root of this message will lead you to discover the source of your problem.
I would recommend using Reflector to examine the references inside of the assembly that you are deploying (preferably on the target sql2005 machine), and then examine the assemblies referenced by that assembly for their references, and so on. If you find a version or filename mismatch in the references (version 1.0 in the manifest but 1.1 on the file-system, a changed name, etc.), you'll likely have found your problem. I know you said you weren't using configuration files, but if you happen to find any... check them out for specific assembly references as well. --Paul Mehner -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Efran Cobisi Sent: Monday, May 28, 2007 8:23 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] TypeInitializationException while opening a contextual connection in a SqlServer 2005 deployed assembly No, unfortunately I didn't rename the assembly and I can reproduce the issue by deploying directly from the Visual Studio 2005 IDE to a fresh new database and then calling the udf on it. Thanks. -- Efran Cobisi http://www.cobisi.com Paul Mehner wrote: > Is it possible that you renamed the assembly when you deployed it? The key > exception that I see is "The located assembly's manifest definition does not > match the assembly reference." > > --Paul Mehner =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
