Debugging .Net assemblies can be tricky in BizTalk 2004. When working with Orchestrations you need to make sure that the version of the Orchestration dll and .Net assembly corresponded. There are two way in which to do this and be able to debug successfully.

1. If your Orchestration project and .Net assembly project are in the same solution. Build/Rebuild solution that contains the Orchestration project and your .Net assembly project. Make sure your .Net assembly project is in debug mode. This can be configured in the 'Configuration Manager". Then, Delete their dll from GAC and install the new ones. Now you can debug by attaching to the process "BTSNTSvc.exe".

2. If your Orchestration project and .Net assembly project are in different solutions then you will need to change the versioning from the default VS configuration. To change this, open your projects "AssemblyInfo.cs" file and change [assembly: AssemblyVersion("X.X.X.*")] to a hard coded value such as[assembly: AssemblyVersion("1.0.0.1")]. Make sure your .Net assembly project is in debug mode. This can be configured in the 'Configuration Manager". Then, Delete their dll from GAC and install the new ones. Now you can debug by attaching to the process "BTSNTSvc.exe".

Ed K.

Tired of installing dll's to the GAC via command prompt or drag and drop to assembly folder?

Well have I got a solution for you. Follow these steps:

1. Create a command file with this information

@echo off

@echo *****************************************************************

@echo ** Add to register

@echo *****************************************************************

:Again

@if .%1.==.. goto Xit

@dir %1 /b

@C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\gacutil /i %1

@Shift

@goto Again

:Xit

@echo *****************************************************************

@Pause

2. Click start - run and type in "sendto"

3. Drag and drop the command file to that location

4. BANG! Now you can simple right click a file and select "Send To" -- "InstallToGac.cmd"

BizTalk guys should really appreciate this one :)

Enjoy,

Ed K.

If you have a computer that you want to join a domain and the computer is connected via VPN you need to do the following steps. Hopefully this will helps someone, unlike me, I had to figure this out myself after search google high and low with no help.

1. Connect your site to site VPN.
2. Configure your VPN appliance to use the targeted domains IP as the DNS
3. Join the domain form the computer properties the usual way except, instead of using the pre-2000 domain name ie "Network", you need to use the fully qualified name ie "MyNetwork.com"

Now if newly joined PC is on a different subnet than you Domain Controller you will need to do this in order to access internal servers/PCs via a remote connection by name:

Go to <root system Dir>\System32\Drivers\etc\    Look for the file name "hosts". In that file you will need to map your Servers/PCs name and IP address.

Keep in mind if you join your PC to a domain while at the domain site and not thru VPN, then take it offsite, you will not need to do these steps. This is only for joining a PC connected via VPN that has never been joined before.

Ed K.

Don't you just hate it when your programming partner works on a segment of code that
you depend on and he goes and makes a typo and checks it in, then it takes you 2
days to figure out the problem. This ones for you Ed B.

Well, we finally got the domian name we wanted, after waiting till some squater forgot to renew it :). So, our blog is up and we will be posting day to day stuff...sometimes it will be code, daily thoughts, ramblings and even crap that we want to be able to google later on.

Ed K