Yossi Dahan [BizTalk]


Wednesday, April 28, 2010

Calling .net 3.5 assemblies from BizTalk 2006

This is one of those - “you don’t know for sure until you try” – things….

Couldn’t think of any reason why this would not work, but had to try to be sure.

BizTalk 2006 uses VS 2005 and .net framework 2.0 (so does BizTalk 2006 R2) and so every c# (ok, or VB) project you wish to reference from your, say, orchestration, is limited to these.

The main downside of this for me these days is the lack of support for LINQ, which I’ve grown to love.

Fortunately – as the CLR targeted by .net 3.0 and 3.5 hasn’t changed (unlike .net 4.0!) BizTalk would quite happily, it turns out, execute code built on VS 2008 targeting .net framework 3.5 if you lazy load it (Activator.CreateInstance).

Don’t think I’d want to lazy load any reference used from now on (and haven’t yet checked the impact of this on, for example assembly caching (or the lack thereof), but I have a bit of code that requires lazy loading anyway coming up, and given that – I’m definitely using VS2008 for that!


Post a Comment

<< Home