Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Changing the dlls being referred by existing applications
- This topic has 2 replies, 1 voice, and was last updated 9 years, 2 months ago by
community-content.
-
AuthorPosts
-
-
January 22, 2007 at 3:20 AM #17348
Hi,
I am facing a situation where I have to change the dll which is being referenced by various projects.
I have a "Common schemas" project where I have a schema (schema1) [There are many other schemas] of version 1.0 .
I have many maps in my existing projects (many in number) references the schema1.In BizTalk Admin console I have my commmon schemas project as an application (that adds the dll to GAC in destination machine).
Then I deployed the various other projects which reference the schema1.Now after a while I am developing a new project there is a need to refer version 2.0 of schema1 (have a new schema file).
The new version has many nodes which were not present in the old version.I want to replace the version 1.0 schema1 y version 2.0 schema1 (another common schemas project).
I manually remove the Version 1.0 common schemas project dll from GAC and add the version 2.0 Common schemas project dll while i need to keep th existing applications running.
But this is not serving the purpose. I am getting errors, feel that the application is still referring the old schema (version 1.0).
I observe the schema nodes havent been changed in the "Common Schemas" Application in the BizTalk Admin console. But the dll in the GAC has been changed.
So which Assembly resource is the application referring to? ( I assumed it always was the GAC dll and not the resource dll in the application).
This is causing a confusion.
Please do let me know how could I make it work. The problem is I cant stop any of the running applications nor would want to delete them to accomodate the change.
The existing applications are compatible with the new version schema.
Thanks in Advance.
-
January 23, 2007 at 8:56 PM #17382
Version in BizTalk is very difficult. Basically, you need to treat the new version like a totally new schema – which it is. Side by side versioning is extremely hard.
You’ll need to make sure you change the versions on the maps, inside the Orchestrations (message variables and on the ports), and set your pipelines to use the correct schema version.
Inside BizTalk Admin, it might be sticky. If you have removed the older version and still see it. Not really sure there.
Best of luck.
-
January 24, 2007 at 8:04 AM #17389
The Original Poster may need to restart the host instance to pick up the changes.
– the one called "weak architect"
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.