When you use intellisense in the editor you will only see your ports, messages, and namespaces from Microsoft and System. You will not see your own defined namespaces. When you enter the first part and the dot, then you will see the rest of the namespace.
Why isn’t this changed in BizTalk Server 2009? (or is it because of the Beta)
Note: always be aware of the ‘Copy local’ function from a referenced assembly!
With BizTalk Server 2009 Beta you can tick the box ‘XML documentation file’ and enter an output file, just like C# projects.
But it is a pity no documentation is generated from the schemas or orchestration. Those artifacts have some possibilities to enter a description or comments.
The output after a build:
Note: you will see warnings when you don’t place comments on publicly visible members:
Maybe it will be in the RTM version, or perhaps an idea for the next release.
I’m working with Microsoft products for a long time, but all the abbreviations Microsoft uses, gives a lot of confusion. But I’m glad not only Microsoft uses a lot of abbreviations, but also my company and all the customers I worked for. I worked for 1 customer where they had a simple Word document from 1.5 MB about abbreviations.
Back to BPI. What is the meaning of BPI according to the sites from Microsoft:
The second one is at the moment the most important, because it fits in the Microsoft Optimization strategy. Application Platform also fits within this Optimization strategy, where SOA and Business Processes are examples of some capabilities.
But, for this blog I’ll focus on Business Process Integration. This BPI is part of the Application Platform Optimization. In this I’m following Microsoft on BPI: “automate and optimize business processes both within their organization and across their customers, partners, and supply chains”. Central in this is the customer for who we are working for. They are in the lead. If they want an ESB, that is fine. If they want VB code for their integration, then we can talk about it. As long as their business runs smoothly, then I am a satisfied person.
Hi,
my name is Gerben and from now on you will find articles about Business Process Integration (BPI) on this blog. In the past I wrote some articles on http://adaict.wordpress.com. Some of them are transferred to this page. My colleagues will continue on that blog for their articles.
Why Business Process Integration? I’m a huge fan of BizTalk Server and work with this great tool since BizTalk Server 2002. But as you can see in the last line: it is a ‘tool’. The last years I worked with some smaller and larger companies and they have all the same problem: “how to connect all our applications and keep the benefits of these applications without buying a whole new backend system. And how can we integrate and optimize our processes to support our business, vendors, resellers and customers”. So, this blog is not all about techniques, but also about the problems the market is struggling with, and of course where I’m struggling with.
This year I’ll also spend some articles on BizTalk in the Healthcare (HL7) and BizTalk RFID (difficult market in the Netherlands).
If you have any ideas or comments, then feel free to contact me.
I hope you enjoy the posts.
Yesterday and today at the Microsoft Application Platform conference in the Netherlands Microsoft announced that BizTalk Server 2009 will become RTM at the end of this month: March. The DVD will be available at the begin of May.
Look for the latest scoop at: http://bloggingabout.net/blogs/wellink/archive/2009/03/13/biztalk-2009-will-include-esb-scoop.aspx 
Yesterday there was a nice discussion about deprecated features. Today I ran into this site: http://biztalkstepbystep.blogspot.com/2009/02/whats-new-in-biztalk-2009.html. This site gives an overview with also some nice screenshots and an explanation. You can also have a look at the roadmap from Microsoft.
With BizTalk Server 2009 it is possible to debug a BizTalk map within Visual Studio. This is very cool. But, at the moment not all mappings are supported. When you use functoids which references an external assembly then you can’t debug.
So, how does this work? Consider the next mapping:
Next, right click on the map and click debug:
Some messages appear. Just click yes, or overwrite or whatever appears 
Finally next screen is shown:
Press F11. On the right screen you can see the generated input file:
You can also debug the functoids:
And see the value of the properties:
In the right pane you can see how the Xsl is building your output Xml:
Another screen example:
As you can see, Microsoft did a good job. When you have large mappings with multiple pages with functoids, lines, xslt etc this can be very handy.
Content © Business Process Integration. Proudly powered by WordPress. To bookmark this site, press Control+D.
"Black Hat" theme by Nicki Faulk. For best results, please view with Firefox. [ Log in ]