You work in an international company which is named TXTWIN. And you’re in charge of the company network and use Microsoft BizTalk Server 2006 R2.
Now you’re developing a solution which uses the following:
1. A receive port
2. An orchestration
3. A custom Microsoft .NET Framework assembly.
You create an MSI package by running the Export MSI File Wizard. The MSI package is imported on your test server. You successfully create the orchestration and the receive port. But the referenced custom .NET assembly is not deployed to the global assembly cache (GAC). So what should you do to make sure that importing the MSI package will automatically deploy the custom .NET assembly to the GAC?
A.
On the computer where you created the MSI package, you install the custom .NET assembly in the GAC.
Run the Export MSI File Wizard again.
B.
In the Microsoft Visual Studio project that contains the orchestration, you should reference the custom .NET assembly.
Set the Copy Local property on the referenced assembly to True.
Run the Export MSI File Wizard again.
C.
First, you should open the Add Resources dialog box by using the BizTalk administration console.
Second, you add a reference to the custom .NET assembly, and select the Add to the global assembly cache on MSI file import (gacutil) check box.
Third, you run the Export MSI File Wizard again, and select the custom .NET assembly on the Resources page.
D.
You run the Export MSI File Wizard again, and select the custom .NET assembly on the Resources page.
Before you perform this, first, you should open the Add Resources dialog box by using the BizTalk administration console.
Second, you add a reference to the custom .NET assembly, and select the Add to the global assembly cache on add resource (gacutil) check box.
Explanation:
BURGOS: mnemo: “MSI package … GAC” = “Add Resources …add a reference … Export MSI File Wizard again”