BizTalk Development Series (24) BizTalk project framework suggestions

For more information, see the BizTalk hands-on experiment series directory.

BizTalk Development Series

Asp. NET has an MVC Framework, and most of the development is based on MVC. BizTalk is message-oriented development and cannot fully adopt a hierarchical development mode. Microsoft only provides the basic policies for BizTalk project development by analyzing related Complex projects. You can also participate in some BizTalk projects. I sorted out the suggestions for the BizTalk project framework.

Basic Principles

• Establish an overall solution for the system.
• Use VSTS or VSS to manage the solution (The following describes how to create a solution in a VSTS environment ).
• Unify the local project directory structure of developers.
• Split a large project into several smaller projects (the size of a separate DLL cannot exceed 10 MB ).
• Use unified test data.

Folder and Project Planning

Divide the overall solution into different areas based on the architecture design, such as BizTalk Applications, Components, Public, Web Applications, and WinForm Applications. When creating a solution folder, you must create the same folder on the physical folder of the solution ).

1. BizTalk Applications subfolders 

• Pipelines and Pipeline are not closely related to other projects. We strongly recommend that you column them as a folder. Use your own defined Pipeline first. If the built-in Pipeline already has this function, we recommend that you use your own Pipeline for future modification convenience (new or delete functions.

• Orchestrations

• Maps

• Schemas

• Exception (if any Exception solution is provided)

2. Components subfolders

• Utility is used to create public methods or operations
• Entity is used to create Entity classes
• BusinessProcess for specific business needs

3. Public subfolders

• Keys is used to store the Key of the solution. It is best to use only one Key.
• TestData/Msgs is used to store Schema-generated instances and test data.
• Config is used to store configuration files or bind files.

Project Initialization Configuration

• Use LOCALHOST or "." (point number) to configure and install the server ). The node number is faster than LOCALHOST.
• Use the relative path When configuring the key.

• Set the corresponding Application Name
• Select All configurations from the configuration options menu.

 

The custom Assembly called by BizTalk needs to be installed in GAC during deployment. In this case, you 'd better run the command to install the custom component to the GAC through the generated event.

"C: \ Program Files \ Microsoft Visual Studio 8 \ SDK \ v2.0 \ Bin \ gacutil.exe"/I "$ (TargetPath)"/F

Note: if an error is prompted during Automatic deployment, make sure all the Assembly has been signed.

[Update]

The following code is applicable to Visual Studio 2010:

CALL "% VS100COMNTOOLS % vsvars32.bat"
Gacutil/uf $ (TargetName)
Gacutil/if $ (TargetName)

Or

"C: \ Program Files (x86) \ Microsoft SDKs \ Windows \ v7.0A \ Bin \ NETFX 4.0 Tools \ gacutil.exe"/I "$ (TargetPath)"/F

 

[2009.5.5 update]

The following code is applicable to Visual Studio 2008:

CALL "% VS90COMNTOOLS % vsvars32.bat"
Gacutil/uf $ (TargetName)
Gacutil/if $ (TargetPath)

[2008.12.12 update]

Alternatively, use the following code to install the DLL to GAC.

CALL "% VS80COMNTOOLS % vsvars32.bat"
Gacutil/uf $ (TargetName)
Gacutil/if "$ (TargetPath)

 

 

Solution directory:

System Folder directory