Problems with third party resource files while importing Msi

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Problems with third party resource files while importing Msi

Viewing 2 reply threads
  • Author
    Posts
    • #19879

      Hi,

      I have two different projects & am using Microsoft Enterprise Library in both the projects. I have created Msi for the same. Now If i deployed both the Msi on the same machine Import dialog fails while importing second Msi as dll’s (Microsoft Enterprise Library) used are already present in GAC. Import dialog is not able to overwirte those dll’s.

      Please tell me that if am using some third party dll’s in multiple projects & building Msi for the project, what should I do to deploy those projects successfully on the QA or Prod environment.

    • #19882

      I usually just run the Enterprise Library MSI separately from my BizTalk MSIs.  This is not ideal, but I don’t know of any good way to check for existence of DLLs in the GAC from a BizTalk MSI.  It wold be nice if we could just add a custom action like we would on a normal MSI, but that is not possible in BizTalk MSIs as far as I know.  If you really need to automate this, then you could leave the EntLib DLLs out of your MSI, and write a batch file that uses BTSTASK to import the MSI, and then uses GACUTIL to check for the EntLib DLLs and install them if they are not there.

      • #19892

        thx,

        In this case I have to create two seperate Msi one for the application & one for the shared library. I want to build only one Msi as client may deploy only one application on one machine.

        My problem is : Is there any way using which I can skip the installation of referenced dll’s if they are already present in another application in Biztalk Administration Console while importing Msi.

         

         

    • #19884

      Hi Rajendra,

      Can you put the enterprise dlls in a separate application and share them to both that need them?  This is what the Operations manual recommends.

      Deploy shared artifacts in a separate application

      If artifacts are going to be shared by two or more applications, deploy the shared artifacts into a separate application. For example, if two applications share a schema, place the schema in a separate application. We recommend this because only one artifact in a BizTalk group can have a single locally unique identifier (LUID). A LUID consists of the artifact name and optionally other attributes. If you include an artifact in one application, and then create a reference to it from another application, the referring application may not function correctly when you stop the application containing the artifact.

      This best practice applies to all artifact types except for files, such as Readme files and scripts, which are added to the application as a File type of artifact. This is because more than one file artifact with the same name can be deployed in a BizTalk group. Therefore, you can use a file having the same name in two or more applications. In this case, stopping one application will not impact the other application. For more information about adding file artifacts, see “How to Add a File to an Application” in BizTalk Server 2006 R2 Help at http://go.microsoft.com/fwlink/?LinkId=106818.

Viewing 2 reply threads
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.