Version control

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Version control

Viewing 1 reply thread
  • Author
    Posts
    • October 19, 2005 at 3:23 PM #12079
      community-content

        we have a orchestration, which will call a .net component. We deployed to production and works great. When the new version of the .net component come out, how can we make the orchectration point to the new version of component

      • October 19, 2005 at 5:48 PM #12080
        community-content

          thanks for the info

          • October 19, 2005 at 3:51 PM #12081
            community-content

              Yes, that is correct.

              When you build the Orchestration it will build to a specific version. This allows for multiple versions of the same assembly to be in the GAC (a.k.a. side by side versioning).

              Are you changing your version on purpose?

              If not, one simple thing to change is make the version of the .net component static. In the AssemblyInfo file, change the version from 1.0.* to 1.0.0.0. Then, when you build it you keep your same version number and do not need to rebuild the Orchestration. You just need to re-GAC the .net component and restart the hosts.

              Hope this helps.

        • Author
          Posts
        Viewing 1 reply thread
        • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.