During development installing your adapter into the GAC makes all the difference. If you don't you will find during your test and rebuild cycles, the assemblies will inevitably get hopelessly locked by either BTS, the Admin console or even Visual Studio. I had often killed all possible non-critical processes (an even some critical ones) and still have been unable to delete the adapter dll from the file system.

Enough of that, the solution is to install the assembly into the GAC, then you just need to restart your host instance for each rebuild. Simple simple simple -- wish I'd thought of it earlier.

There are two technical steps necessary:
1. Strong name your assemblies
2. Add a line to your adapter project such that the post-build event registers the resulting assembly in the GAC. "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin\gacutil.exe" -i $(TargetPath)
3. Change the following registry settings for the adapter to empty: InboundAssemblyPath, OutboundAssemblyPath, AdapterMgmtAssemblyPath
4. For the each of the type name (InboundTypeName, etc), you now need to specify the fully qualified strong name for the type, i.e.
"zouak.adapters.mynewadapter.adapters.Rx, MyNewAdapterAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1234567890123456"