BizTalk Challenge add namespace to message

Today I faced a new challenge with BizTalk Server, where I needed to add a namespace to an incoming message. Through Google I found an excellent post by Richard Seroter. If you had installed the BizTalk Adapters for Enterprise Applications, you’d find a Visual Studio.NET project located at:

C:Program FilesMicrosoft BizTalk Adapters for Enterprise ApplicationsPipeline Component.

For me this is interesting since I am working with BizTalk Server 2006 on 64-bits and currently integrating with Oracle eBusiness Suite (see previous posts).
Pipeline component is called SetNSForMsg.

You can open solution, build project. One can encounter an error stating the Designer.cs is not present or is visual but with an exclamation mark (delete it). Change code in SetNSForMsg.cs class in IComponent
IBaseMessage Execute. Rest you can find in Richard Seroter post. Change if necessary the delayed signing into singing of the component and copy it to C:Program FilesMicrosoft BizTalk Server 2006Pipeline Components. In VS2005 you can add pipeline through choose items in toolbox (see picture below).

Technorati: BizTalk Pipeline Component Richard Seroter

Author: Steef-Jan Wiggers

Steef-Jan Wiggers is all in on Microsoft Azure, Integration, and Data Science. He has over 15 years’ experience in a wide variety of scenarios such as custom .NET solution development, overseeing large enterprise integrations, building web services, managing projects, designing web services, experimenting with data, SQL Server database administration, and consulting. Steef-Jan loves challenges in the Microsoft playing field combining it with his domain knowledge in energy, utility, banking, insurance, healthcare, agriculture, (local) government, bio-sciences, retail, travel, and logistics. He is very active in the community as a blogger, TechNet Wiki author, book author, and global public speaker. For these efforts, Microsoft has recognized him a Microsoft MVP for the past 8 years. View all posts by Steef-Jan Wiggers