Friday, October 03, 2008

SOA & Business Process Conference, January 27-30, 2009

A question was brought up in the Indy BizTalk user group meeting a couple a weeks ago about this years SOA Conference. The SOA Conference IS taking place this year, well technically next year. It will be at the Microsoft Conference Center in Redmond.

There will be two tracks:

Track 1: SOA & BPM Best Practices

This track will focus on case studies and appling SOA strategies to organizations.

Track 2: Technology Offerings

This track will focus on the technology that can be used attain a SOA approach.

I will not be attending as the airlines will not let me on the planes at that point - well not without my doctor basically sitting next to me :). I will be sure to get the DVDs when they come out. I've gone to this conference a few times and it is the best conference if you are interested in SOA and Microsoft technologies.

Thursday, October 02, 2008

"Dublin" and the next version of WCF/WF announced

At PDC this year, the CTP will be released for .NET Framework 4.0, the next version of WCF/WF, and a host to run WCF/WF code named "Dublin".

Personally, I'm excited to see the changes for the WF rules engine.

Links to the announcement:
http://blogs.msdn.com/stevemar/default.aspx
http://www.microsoft.com/net/dublin.aspx

Also, I realize I need to change the title of the blog to include Biztalk 2009.

Thursday, January 17, 2008

Invalid Pipeline Component Load - Debugging

Today while working with a custom pipeline component I got the error 'You have selected an invalid pipeline component assembly. Please check security settings if you are loading it from an UNC path'. The error was creating when I was trying to add the pipeline component to the toolbox. While I saw many suggestions on the web, none solved my problem. The problem was that I had added a different resource file to the component, and the name I gave when creating the ResourceManager was wrong. But, more importantly, I discovered that by putting a System.Diagnostics.Debugger.Launch(); in the get of the Name property I was able to debug the pipeline component when loaded into the Toolbox editor.