One of the major challenges in Real World SOA enterprise applications is the lack of semantic information associated with Service Contracts. For a while now the W3C folks have been working in different efforts for relating semantic web Standards (RDF,…(read more)
After my last post on this topic Alan Smith left a comment on my blog.
His comment was a good point and is worthy republishing here, to round out the topic.
Here it is verbatim:
“I’d agree with you there that quite a few .net ppl will try to solve problems with C#, rather than learning the correct way to solve things in BizTalk. I spent my first few weeks thinking “I can do this in 2 hours in C#, why does it take me 2 days in BIzTalk?”. As you get your head aroud how BizTalk works, you do things in BizTalk in 2 hours that would take 2 days (or 2 weeks) to do in C#.
But there’s also a catch 22 here, if I was hiring a BIzTak guy, i’d pick someone who was a good .net (or java) developer. Even though you don’t ‘usually’ write much code, there are situations when you need to, and you need to have good programming skills to do so. Custom pipeline components, custom functoids, and C# utilities to call from orchestrations are usually required (ok, maybe not functoids) on most BizTalk projects, and the code for these component needs to be solid.
Along with the dangers of having .net ppl solving everyting with C#, you also have the danger of ppl who are scared of programming jumping into BizTalk development because thay think it’s easy, and think they can build apps by drawing things.”
It never occurred to me that a non developer would look at BizTalk as a way to dev work with out code. Thats never gonna work. BizTalk is well and truly a developer technology.
A few people have asked for the BizTalk 2004 version of this BizTalk SqlBulkInsert 2006 Adapter
Follow the below instructions to install on BizTalk 2004:
1) Download the zip file at the end of this blog entry.
2) When unzipping, unzip it a different folder such as: C:\temp
3) Copy the unzipped contents -> C:\Temp\BTSBulkLoad\SqlBulkInsertAdapter directory
to the C:\BTSBulkLoad\ directory that was created by the BizTalk 2006 zip file that you can find here:
(Look at the bottom of the above referenced blog entry for the download and Readme instructions).
Just replace the VS2005 C:\BTSBulkLoad\SqlBulkInsertAdapter folder contents with the VS2003 SqlBulkInsertAdapter directory contents.
4) Follow the below installation instructions for the BizTalk 2006 adapter to install the BTS 2004 adapter
Remember that this is just a prototype, so you will have to fix the code to get it to work properly. Peter (see comments from this blog entry) has stated that he has a BizTalk 2004 version of the adapter working.
Download the BizTalk 2004 adapter (Zip file) here
There’s a new BizTalk newsletter/website on the web: BizTalkHotRod (found
through Richard
Seroter), created by some Microsoft Technology Specialist and other members of
the community. The first issue can be found here.
I find the layout and overall design of the website and newsletter to be pretty awful
(my opinion), but suffering through that is well worth it to get to the actual
content. Lots of great stuff on the first issue guys, so keep’em coming!
Recently I had to insert a record using a stored procedure and the SQL Adapter in BizTalk 2006. There are lots of examples on both how to insert records and how to select a number of record using this adapter. However I had problems finding how to insert a record and receiving the new id of the […]
Earlier this week I received an email from Anil Sanagavarapu who
firstly is crazy about Cricket and the World Cup.
He mentioned that his company Iris
Software is embarking on a cool RFID Services project…..
So we got chatting and I’ve just seen what they’re doing around RFID using Microsoft
RFID Services, was fantastic.
Specifically their solution implements:
The guys are looking to bring out some Video Content around their solution and project
based on their experiences. They will provide a Walk through of Microsoft RFID Services,
how to develop and implement solutions.
Looking fwd to that – great work guys! 
Cheers,
Mick.
A new online BizTalk maghas come out, a more pleasent read than most whitepapers, especially if you’re a motor heador a fan of that Ministry song ding a ding dang my dang a long ling long.
I just noticed that in GeeksWithBlogs move to SubText some of my old screen shots have been lost, I’ll fix these as soon as I get time.
We are developing BizTalk applications with Visual Studio Team Edition and every now and then for some reason the Orchestration Designer is removed from the “Open With” dialog, thus when one double clicks on an orchestration it is opened with the Xml Editor. Although I’m not sure why this happens, I suspected the items in this dialog were configured in the Windows Registry … and so they were, so to fix:
1) Open RegEdit
2) Go to HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\8.0\Editors and find the BizTalk Orchestration Designer for us it was under Guid {679b7fd6-2104-42b2-8d87-86dd575fc269}
3) Get the package key Guid, for us this was {2f926337-2bfb-46ab-bbc4-a955ce25ff6f}
4) Go to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Packages\{Package Key Guid}\SkipLoading
5) Set the SkipLoading key to 0
6) Restart Visual Studio and the Orchestration Designer should show up in the “Open With” list
Does anyone know why the SkipLoading key is mysterouslyturned onfor the Orchestration Designer?
Marty and Scott have an article in this month’s MSDN Magazine, “8 Tips and Tricks For Better BizTalk Programming”. Each tip (I am not giving any away) is reinforced with useful details and examples. The article also includes a short list of resources…(read more)