PowerShell provider 1.2.0.1 released

25 February 2011

A short post to let the users of the PowerShell provider for BizTalk know we have released a new version.

In the previous versions in some circumstances the provider (and PowerShell runtime) crashed when adding a new resource using the new-item cmdlet. This, among some other things, has now been fixed in release (v 1.2.0.1).

You can download the new version from here.

Thanks to Maxime for helping me fix this bug.


BizTalk Server MVP 2011

1 January 2011

Great start of 2011 for me. Today I received an e-mail from Microsoft telling me that I’ve been re-awarded the MVP title.

This is the second time for me. The first year has been an awesome experience. The title gave me the opportunity to do great things and meet inspiring and very skilled people.

I would like to thank:
- my MVP leads William Jansen and Gaby Lieuw 
- Ed Hickey and all other Microsoft employees involved
- people at Aviva Solutions
- and finally many thanks to Ivanka for her support and patience

I’m looking forward to another great year!

Happy new year everyone!


Visual 2010 BizTalk project woes

18 November 2010

I sometimes find myself in a situation where I need to make direct modifications to the XML code of an orchestration, map or pipeline. In Visual Studio you can do this easily by opening the file with the non default editor (right click orchestration file, ‘Open With…’ and ‘XML (Text) Editor’).

I encounter very strange behavior for the different file types (orchestrations, maps, pipelines) after I opened them in the Visual Studio 2010 XML editor. For schema files the behavior is as expected. For the other file types it looks like the default editor binding is missing after opening the file in the XML editor.

Orchestrations:

Steps to reproduce:
- right click orchestration (.odx) file in solution explorer
- choose ‘Open With…’
- choose ‘XML (Text) Editor’
- close the orchestration (save is not necessary)
- open the orchestration with the default editor (double click)

Results:
The orchestration opens but displays a very strange screen. It looks like a mix between the orchestration and the code behind:

image

Besides this there are the context menu for the specific orchestration has changed. Two options are added:

image

Maps:

Steps to reproduce:
- right click map (.btm) file in solution explorer
- choose ‘Open With…’
- choose ‘XML (Text) Editor’
- close the map (save is not necessary)
- open the map with the default editor (double click)

Results:
In this case the map opens with the correct mapper editor but there are also two extra options added to the context menu as is the case with orchestrations.

Pipelines:

Steps to reproduce:
- right click pipeline (.btp) file in solution explorer
- choose ‘Open With…’
- choose ‘XML (Text) Editor’
- close the pipeline (save is not necessary)
- open the pipeline with the default editor (double click)

Results:
For pipelines Visual Studio opens the XML representation when double clicking. It seems as if the default editor has changed.

image

This is very annoying. Is it just me? Do you have this too at your development box?

Workaround:
The workarounds I found are:
- Choose ‘Open with…’ and pick the default editor from the list.
- Open the BizTalk project (.btproj) with notepad and remove the ‘<subType>’  xml nodes for every file. After open the project again in Visual Studio it is fixed (until you open the file with the XML editor again).

I’m using BizTalk 2010 RTM (developer edition), Visual Studio 2010 Ultimate. Do you have this too?

I raised this issue on the Microsoft connect site.


BTUG meeting 2 december: BizTalk 2010

15 November 2010

nederlandse-vlag

Op 2 december a.s. geef ik samen met Steef-Jan Wiggers een presentatie over BizTalk Server 2010.

Wil je weten wat er allemaal nieuw is in BizTalk 2010 kom dan naar de BTUG meeting op 2 december.

Naast onze presenatie zijn er nog twee andere presentaties:

- BizTalk 2010 en Trading Partner Management  (Richard Sargeant)
- Extended and Scalable integration through the cloud (Gijsbert in ’t Veld)

Note to international readers of my blog:
The above post is aimed at the Dutch community and therefor only published in Dutch language. Unless you want to learn Dutch you can safely ignore it (I realize that is probably true for all my posts). Smile


Review: Applied Architecture Patterns on the Microsoft Platform

15 November 2010

 

Recently the book ‘Applied Architecture Patterns on the Microsoft Platform’ was released. The book is written by Richard Seroter, Stephen Thomas, Ewan Fairweather, Mike Sexton and Rama Ramani. Yossi Dahan is the technical reviewer. The book is published by Packt Publishing.

Shortly before the book was released, an event was held in Stockholm, Sweden. I was lucky enough to be able to attend. Three of the authors (Richard, Stephen and Ewan) did two long days of presentations. In the humorous and spirited presentations the chapters in the book were discussed accompanied by nice live demos.

I was already interested in this book because these authors are respected and known worldwide as BizTalk and Microsoft experts. After attending the event I was even more interested in reading the book.

A couple of weeks after the event I was contacted by the publisher. They asked me to read the book and write a review on my blog site. Below is my review:

During the last few years the Microsoft platform has evolved in two directions. Extension and enhancement of existing technologies and products has of course continued. A couple of new technologies and products including Windows AppFabric, Windows Azure AppFabric, and StreamInsight have been added to the stack. Architects have the important task of picking the right technology for their specific problem at hand from the broad landscape of technologies and products. Picking the right technology for a new project can be very challenging due to the number of architectural decisions that must be made. Wrong choices in this area can lead to big problems and high costs for companies.

How to pick the right technology or product from the Microsoft stack is exactly what this book is about. It must be said that the book does not try to be the ultimate reference guide with the right pointer for each possible scenario. Instead it equips the reader with the knowledge to decide which technical architecture is most appropriate.

The book can be roughly divided into three parts. The first part (chapter 1) creates an architectural decision framework. The decision framework is one of the tools used in the process of translating requirements into technical solutions.

The second part (chapters 2 through chapter 6) compromises the technology primers. The primers are an introduction to technologies and products used in the book. For each primer, typical use cases are described. There is also a sample solution included for each primer.

The third and final part (chapter 7 to chapter 19) contains the elaboration of a couple of fictitious cases. First, a company with a specific IT problem is introduced. Next, the decision framework from the first chapter is used to determine the best fitting architecture for the IT problem. Finally, the case is implemented in a downloadable sample solution.

In my view, books about architecture tend to be boring and hard to read. This book is absolutely not the case; I really enjoyed reading it. This book fills a gap in the Microsoft architecture guidance.

My favorite things about the book are:

· It provides a broad overview of the Microsoft product and technology stack. Newer technologies like Windows AppFabric and StreamInsight are included.

· The decision framework provides a useful tool for real world scenarios and helps in the design process of translating requirements into software.

· The extensive set of cases (12 chapters) is the main part of the book. It provides architectural information and reusable code that can be used as a starting point for real world scenarios.

This book is a must have for every Microsoft architect and developer.


Follow

Get every new post delivered to your Inbox.