When configuring the adeaptr for BizTalk Server 2010 using .Net 4.0, I ran into some stuff that I would like to share:1) When trying to get the Null Dev adeaptr to work on BizTalk Server 2010 64-bit, make sure you use Regasm.exe for the .Net Framework 4 in the 32-bit framework directory. Else you will get the following error when trying to configure the adeaptr:Retrieving the COM class factory for component with CLSID xxx failed due to the following error: 80040154 Class not registered2) Also remember to register both ways' as indicated elsewhere on this blog. ()3) The adeaptr has been tested by me on a 64-bit platform. I found out that the adeaptr, when compiled MSIL, only runs in a 64-bit host. When using a 32-bit host I get different errors, depending on the scenario fresh send or resume. The errors are Unknown Error' and a message complaining about the assembly beinging compiled for a newer runtime than the currently loaded one. I have not investigated this any further.4) Make sure you have the path's to your DLL's configured correctly in the .reg file
Does the Adapter work with BizTalk 2009 32Bit edition?Here are the steps taken:1. Downloaded Source2. Compiled Source3. Merged .reg file with Registry4. Ran>>regasm Winterdom.BizTalk.Adapters.NullAdapter.dll5. Ran>> ilitanlutsl.exe Winterdom.BizTalk.Adapters.NullAdapter.dll6. Registered the adapter with BizTalk Server Administration Console7. Restarted Host Instance8. Shutdown Console (Additional Step)9. Restarted OS (Additional Step)10. Opened BTS Admin ConsoleEnvironment -BizTalk 2009 32BitOS: Windows 7 32BitHere's the error I get when attempting to configure on send port -Retrieving the COM class factory for component with CLSID{c6085098-b9f6-4214-be1c-b07ef5265e4d} failed due to the following error: 80070002. (mscorlib)