How Deployment Works Describe the process of deploying a Microsoft BizTalk Server assembly. Deploying BizTalk Assemblies After you have used Microsoft Visual Studio® to compile your BizTalk project into an assembly, you can use Visual Studio to deploy the assembly as well. Deploying a BizTalk assembly involves two steps: Installing the assembly (a DLL) into the global assembly cache (GAC) Registering the assembly in the BizTalk Management database Any assemblies containing BizTalk artifacts must be registered in the BizTalk Management database, because BizTalk Server efficient access to the details each artifact at run time. When a purchase order message arrives at a receive location, for example, BizTalk needs to perform a look-up to determine which assembly holds the schema for the purchase order message type. Because BizTalk assemblies need to be deployed to the GAC, they will also need to be assigned a strong name. Assigning a strong name to an assembly will be covered in this module. Non-BizTalk Assemblies Any assemblies in the BizTalk solution that do not contain BizTalk artifacts need to be installed only in the GAC. A non-BizTalk assembly might contain items such as HTML files, XML files, forms, Microsoft .NET helper classes, or ASPX pages.
How Deployment Works Describe the process of deploying a Microsoft BizTalk Server assembly. Deploying BizTalk Assemblies After you have used Microsoft Visual Studio® to compile your BizTalk project into an assembly, you can use Visual Studio to deploy the assembly as well. Deploying a BizTalk assembly involves two steps: Installing the assembly (a DLL) into the global assembly cache (GAC) Registering the assembly in the BizTalk Management database Any assemblies containing BizTalk artifacts must be registered in the BizTalk Management database, because BizTalk Server efficient access to the details each artifact at run time. When a purchase order message arrives at a receive location, for example, BizTalk needs to perform a look-up to determine which assembly holds the schema for the purchase order message type. Because BizTalk assemblies need to be deployed to the GAC, they will also need to be assigned a strong name. Assigning a strong name to an assembly will be covered in this module. Non-BizTalk Assemblies Any assemblies in the BizTalk solution that do not contain BizTalk artifacts need to be installed only in the GAC. A non-BizTalk assembly might contain items such as HTML files, XML files, forms, Microsoft .NET helper classes, or ASPX pages.