Exception thrown: Samme assembly/ressource but different versions


An exception is thrown in BizTalkInstallation.LoadConfig if you have more than one assembly with the same name but different versions - eg, and
The code is working perfect on my development box, but I'am unable to use it on my production box
Thanks in advance /Peter


plykkegaard wrote Feb 28, 2010 at 10:33 AM

I have retrieved the current codebase for BiztalkOM as used int the BizTalk Documenter and added a try/catch block in the BizTalkBaseObjectCollection.Add method
I can run the program but I will loose track of which version is in use - eg which outboundmap is used in a send port

An idea could to store the version number (taken from BtsAssembly.Version) in a local variable/property on BizTalkBaseObject
Add a readonly property called Key and the key/index for the hashtable in BizTalkBaseObjectCollection

Obviously this will break almost everything (eg no maps retreived for ports) and one need to go through the whole application to replace the use of name property with the key property when retreiving data from the BizTalkBaseObjectCollection .... - hmmm any other ideas?


plykkegaard wrote Feb 28, 2010 at 8:30 PM

Hmm there's a similar problem in Schema.Load due to duplicate schema names (different versions)


nbusy wrote Mar 19, 2010 at 5:22 AM

Issue with a map deployed in two versions of an assembly. The Documenter fails working.

wrote Feb 13, 2013 at 12:19 AM