Finally submitted my entry to the BizTalk Server contest. Curious?
I created a transactional .NET adapter. This adapter allows you to submit messages to any .NET component that implements a certain interface, in a transactional manner. This means that, for example, if you access SQL Server from within your component, every operation on SQL will be in the same transaction as all message box operations. This guarantees high reliability between the message box and any transactional backend. If the transaction fails, everything will be rollbacked (including all operations on the message box) and the message transmission will be retried.
So, instead of accessing your components using an expression shape inside an orchestration, you finally might think of doing things asynchronously now! By calling .NET component asynchronously using the BizTalk Server 2004 Transactional DOTNET Adapter you can leverage the retries, backup transport, tracking and BAM features as well.
What’s in the package?
- MSI installation package
- .chm documentation files
- couple of samples
- full documented source code
To show the adapter framework’s inner workings, I programmed directly against the adapter framework. (Not using the SDK adapter base classes.)
Now it’s up to you guys for using this: please provide me with comments, feedback. Tell me what’s good and what isn’t. Tell me what or how to improve… But first of all: enjoy it. It’s there, it’s free, it’s for you!
Have fun with the pet project I’ve spent couple of months with:
Special thanks to my girlfriend for all the patience she had!