And another BizTalk discovery

Having spent the day dealing with this, I found that I got a vision of the guts of BizTalk.

Obviously not being able to identify where these mysterious schemas were going I decided there was stop mucking around and dig into the tables of the managementDB

Having found what looked like a likely suspect hanging around in the BizTalk.Service application I decided to work out how to dispose of this unwanted scumbag of a dll that was causing me grief!

This led to me finding this blog and after significant checking came up with the following snippet that seems to work on 2006

Give it a shot, it worked for me, but do not come crying if BizTalk no worky...

use BiztalkMgmtDB
go
declare @iAssemblyID int
select @iAssemblyID=nID from bts_assembly where nvcName = 'INSERT DLL NAME HERE'
select @iAssemblyID
delete from bt_mapspec where assemblyid = @iAssemblyID
delete from bt_documentspec where assemblyid = @iAssemblyID
delete from bts_item where assemblyid = @iAssemblyID
delete from bt_properties where nassemblyid = @iAssemblyID
delete from bt_sensitiveproperties where assemblyid = @iAssemblyID
delete from bts_libreference where idlib = @iAssemblyID
delete from bts_assembly where nID = @iAssemblyID

Ah what a day, half a day chasing an illussive schema around BizTalk

Problem
We have a BizTalk 2006 project that uses a mixture of schemas and .net serializble objects based on these schemas. Trying to be clever we decided to create port types and messages that were based on the .net type rather than the schema. Circumstances arose where we needed to mix the two up methods (using schemas and .net classes) within one orchestration\project. I kept getting the old message about there benig more than one schema for the inbound message, and I could not find out where this apparant other schema was.

Reason
If you use ports that consume messages that are based on a serializable .net type rather that a schema, biztalk automatically creates a schema for this .net type under the Biztalk.System application, try it, you will see a schema for your .net type appear.

This type is (obviously) based on a serialized version of the .net type.

Once inside the orchestration, it seems you can use this message as if it were of the type when passing out to helper classes.

New PDA

So I have a new love in my techno life. My new PDA. It is the nuts, it is an HTC P3350 running on T-Mobile.


A whole new chunk of technology for me to get my teeth into and blog about.


Discoveries so far....


T Mobile have chosen to lock the wifi functionality for reasons unknown. I guess it stops me installing a skype client and stopping use their air time, along with forcing me to use their soo slow gprs!

Soooo. why is this phone the daddy. Well it has built in GPS which means I can begin to look into location specific functionality without having to use the cell triangulation which most providers do not allow easy access to...

More to come soon

The blog is up

Finally got around to creating a blog.

Been contemplating it for a while and finally figured I would give it a bit of my time. Hope it is worth while to somebody out there. Will divide it up into a couple of areas, but will try to write as often as possible! lets hope I can maintain the enthusiasm

Better late than never is