Biztalk Naming Conventions

BizTalk 2004 Naming Conventions code is

2.

Scott Colestock / traceofthought.net

BizTalk Artifact Namespaces CompanyName.TechnologyName.Feature CompanyName.[FunctionalArea].[Project].BizTalk.[AssemblyType] containing BizTalk Assemblies MyCompany.MyProject.Orchestrations.dll MyCompany.MyProject.Schemas.dll MyCompany.MyProject.Pipelines.dll MyCompany.MyProject.Transforms.dll MyCompany.MyProject.PipelineComponents.dll

Scott Colestock / traceofthought.net

BizTalk Messaging Artifacts ensure that the .NET type name matches Artifact

Standard

Notes

Example

or

.

or or or or or

Orchestration Naming Conventions – Workflow Shapes group(Shape names should always follow Pascal casing after the prefix that is specified below.) Shape

Standard

Notes

Example

If-Branch Else-Branch which contains expression: X_LoanRequestToCreditRequest”

which contains transform shape:

and should include what should be done by the administrator before resuming the orchestration. Scott Colestock / traceofthought.net

or

or

Orchestration Naming Conventions – Orchestration Types Type

Standard

Notes

Example

Scott Colestock / traceofthought.net