Blog

View Blog

Preparing a BizTalk project to be built and deployed

Nov 1

Written by: Wilfried Mausz
01.11.2006 17:40

I am currently preparing samples for one of my BizTalk trainings in November. One thing which I always mention in my workshops but usually causes some trouble when afterwards doing the first steps with BizTalk is how a project should be prepared to be built and deployed in Visual Studio 2005.

After successfully creating some BizTalk artifacts the project should be built. So everything is compiled into an assembly. Then this assembly has to be deployed to BizTalk server. This means the assembly is registered in the internal BizTalk databases and, furthermore, registered in the Global Assembly Cache (GAC). For those who are not yet familiar with assemblies and GAC, take a look at http://en.wikipedia.org/wiki/.NET_assemblies and http://en.wikipedia.org/wiki/Global_Assembly_Cache.

Activate the "Deploy" checkbox

The first thing that happens after starting the deployment (in the Build menu) is … nothing. The “Deploy” option of a BizTalk project is disabled by default. So to get it working, open the Solution properties and activate the “Deploy” checkbox for the BizTalk project.

Now one can press “Build, Deploy Solution” and something happens. But then usually the following error message is displayed:

Set the key-file

All BizTalk assemblies need to be strong-named. Check the article about .NET assemblies from above and http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconworkingwithstrongly-namedassemblies.asp for more information on “strong-named assemblies”.

To make an assembly to a strong-named one, open the project properties of the BizTalk project choose “Assembly” and set the “Assembly key file” property to an appropriate key file.

If you do not have a key file, open the “Visual Studio Command Prompt” and create the file using

sn –k mykeyfile.snk

Now one can again try to build and deploy the solution and … you should get the “Deploy succeeded” – message.

Think about restarting the Host Instance

Usually there is a deployment warning that it may be necessary to restart the BizTalk Host Instance for changes to take effect. This would be needed if an assembly was changed and redeployed after an old version of it is already running on the server. But restarting the Host instance can be very useful too, after one has changed some messaging or Orchestration properties (like modifying Send Ports or Receive Locations and binding or enabling an Orchestration).

Trackback Print

Location: Blogs

Wilfried's Blog

Biztalk and Infopath

Tags:

74 comments so far...

Re: Preparing a BizTalk project to be built and deployed

I have never seen such a good and clear example.
Its like a crystal water.
Hats off:)

Gautam,
mech.gautam@gmail.com

By Anonymous on 07.03.2008 12:56

marcus evans

marcus evans company information
# marcus evans

By TrackBack on 02.08.2008 01:17

marcus evans

marcus evans holiday 2004
# marcus evans

By TrackBack on 05.08.2008 11:58

marcus evans

marcus evans alexa information
# marcus evans

By TrackBack on 19.08.2008 12:09

aceldiul

aceldiul
# aceldiul

By TrackBack on 30.01.2010 03:36

Re: Preparing a BizTalk project to be built and deployed

In my last 1z0-051 weblog about testing regular expressions I have written about KIKI which enables one to enter a demo text and test regular expressions against it. The tool shows you which matches were found in the text and how the expression was evaluated.220-601 But it was not able to create a new expression with this application. You just could test existing ones.

While searching infos for a new project I found a program called Expresso, which enables one to build and test .NET 220-602 regular expressions

By leeman2009 on 30.01.2010 11:23

januvia

januvia
# januvia