Undeploying assembly

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Undeploying assembly

Viewing 1 reply thread
  • Author
    Posts
    • July 12, 2006 at 4:13 PM #14003
      community-content

        Not sure, I guess I have never looked.

        I know in 2006 if you remove it using the Admin tool it does not un Gac the code. I would guess 2004 is the same.

        The key is all the configuration information is removed from the BizTalk database.

      • July 12, 2006 at 9:00 PM #14004
        community-content

          Yes, it does. Here’s a problem I used to have.

          I was on my machine, then I would deploy to remote MachineX.
          Then I would undeploy. But later I would try to run some orch’s on my machine and they would fail for missing load modules.

          So they point is, that the Deploy/Undeploy does GAC/Un-GAC, but only on your machine. If you are doing a remove deploy/undeploy, be careful, especially of the undeploy. To deploy, you must manually GAC the .DLLs.

          Currently, I’m using some NANT scripts to deploy to my remote MachineX. The basically copy the .DLLs, GAC, and restart Biztalk, all with the click of a single button. However, I typically just move the .DLLs, and don’t do a full deploy/undeploy, which usually works as long as we don’t change the schema layouts. It can cause issues in the HAT Orch debugger (shapes missing), but it’s so much easier!

          Neal

          • July 12, 2006 at 10:23 AM #14005
            community-content

              Hi

              Within Visual Studio, if you use the \”undeploy\” option for an assembly in the BizTalk Configuration Database, does it also remove it from the GAC?

              Cheers

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