I’ve just uploaded the source code for my old /dev/null
BizTalk Adapter sample on GitHub, which
is where I’m posting all my utilities, libraries and tools now.
The repository contains both the original version of the adapter, as well as the special
BizTalk 2006 R2
version I did that showed how to use create custom
configuration dialogs for adapters in R2.
The original version is in the ’master’
branch, while the R2 version is in the ’R2’
branch. Enjoy.
I've read, listened to and been in a few discussions lately about competency, or the rather the different kinds of developers – as in the diverse approach they have to their day job. I thought I'd give my view, compacted as it must be in a blog…(read more)
I have come across this a lot and finally was sick of it enough to write about it.
The situation is I have an input that has a bunch of optional fields, and the output is normally a fixed length record file. In my case it is normally an EDI file of some kind that I am mapping to a flat file layout. When I start testing the map, I get the following error produced by the flat file assembler:
Error details: Unable to read the stream produced by the pipeline. Details: Cannot find definition for the input: Address
The reason is that there was no Address in the source data, but the output required it to be there to conform to the flat file layout. If you look at this page from msdn on how to force the creation of elements that are optional. Yes, this is possible, but in my case, I would be creating a script for every element I am creating, which would amount to hundreds of scripting functiods.
Underlying logic: The mapper when dragging optional source items to a required destination item creates the following logic in XSLT:
<xsl:template match="/s0:File"> <ns0:File> <xsl:if test="@Name"> <Name> <xsl:value-of select="@Name" /> </Name> </xsl:if> <xsl:if test="@Address"> <Address> <xsl:value-of select="@Address" /> </Address> </xsl:if> <xsl:if test="@City"> <City> <xsl:value-of select="@City" /> </City> </xsl:if> <xsl:if test="@State"> <State> <xsl:value-of select="@State" /> </State> </xsl:if> <xsl:if test="@Zip"> <Zip> <xsl:value-of select="@Zip" /> </Zip> </xsl:if> <xsl:value-of select="./text()" /> </ns0:File> </xsl:template>
The easy solution, create a second map that maps the destination input to the destination output (and easy way to do this is by following these autolink directions). This creates the following XSLT:
<xsl:template match="/ns0:File"> <ns0:File> <Name> <xsl:value-of select="Name/text()" /> </Name> <Address> <xsl:value-of select="Address/text()" /> </Address> <City> <xsl:value-of select="City/text()" /> </City> <State> <xsl:value-of select="State/text()" /> </State> <Zip> <xsl:value-of select="Zip/text()" /> </Zip> <xsl:value-of select="./text()" /> </ns0:File> </xsl:template>
Notice that there are not any if tests.
You can chain the maps together in an orchestration, or you can place the map in the receive port and the straight thru map in the send port.
What would be nice is to have a map setting called Force Optional Creation Mapping set default to No to leave the behavior as currently is, but if set to Yes, the underlying logic would remove the xsl:if from the map an force the creation of the destination elements regardless of the presence of the input.
So my employeer is making a small organizational adjustment, to follow market trends and to adjust to the rest of the company, making the company more normalized in its organizational structure throughout. It happens once a year or so so you kinda get…(read more)
This evening we published the first public release candidate of Silverlight 2.
There are still a small handful of bugs fixes that we plan to make before we finally ship. We are releasing today’s build, though, so that developers can start to update their existing Silverlight Beta2 applications so that they’ll work the day the final release ships, as well as to enable developers to report any last minute showstopper issues that we haven’t found internally (please report any of these on the www.silverlight.net forums).
Important: We are releasing only the Silverlight Developer Runtime edition (as well as the VS and Blend tools to support it) today, and are not releasing the regular end-user edition of Silverlight. This is because we want to give existing developers a short amount of time to update their applications to work with the final Silverlight 2 APIs before sites are allowed to go live with it. There are some breaking changes between Beta2 and this RC, and we want to make sure that existing sites can update to the final release quickly once the final release is out. As such, you can only use the RC for development right now – you can’t go live with the new APIs until the final release is shipped (which will be soon though).
You can download today’s Silverlight Release Candidate and accompanying VS and Blend support for it here. Note that Expression Blend support for Silverlight 2 is now provided using Blend 2.0 SP1. You will need to install Blend 2.0 before applying the SP1 service pack that adds Silverlight 2 support. If you don’t already have Blend 2.0 installed you can download a free trial of it here.
Today’s release candidate includes a ton of bug fix and some significant performance optimization work.
Today’s release candidate also includes a number of final API tweaks designed to fix differences between Silverlight and the full .NET Framework. Most of these changes are relatively small (order of parameters, renames of methods/properties, movement of types across namespaces, etc) although there are a number of them. You can read this blog post and download this document to get a listing of the known API breaking changes made from the Beta2 release.
We have updated the styles of the controls shipped with Silverlight, and have also modified some of the state groups and control template names they use. When upgrading from Beta2 you might find it useful to temporarily remove any custom style templates you’ve defined, and get your application functionality working using the RC first – and then after that works add back in the styles one style definition at a time to catch any rename/behavior change issues with them.
If you find yourself stuck with an question/issue moving from Beta2 to the RC, please report it on the www.silverlight.net forums (Silverlight team members will be on there helping folks). If after a day or two you aren’t getting an answer please send me email (scottgu@microsoft.com) and I can help or connect you with someone who knows the answer.
Today’s release candidate includes a bunch of feature additions and tweaks across Silverlight 2, as well as in the VS and Blend tools targeting it. In general you’ll find a number of nice improvements across the controls, networking, data caching, layout, rendering, media stack, and other components and sub-systems.
Over the next few months we will be releasing a lot of new Silverlight 2 controls (more details on these soon). Today’s release candidate includes three new core controls – ComboBox, ProgressBar, and PasswordBox – that we are adding directly to the core Silverlight runtime download (which is still only 4.6MB in size, and only takes a few seconds to install):
At runtime these controls by default look like:
The ComboBox in Silverlight 2 supports standard DropDownList semantics. In addition to statically defining items like above, you can also use databinding with it. For example, we could define a "Person" class like below:
And the add a ComboBox to a page like so:
And then write the below code to databind a collection of Person objects to the ComboBox (by setting its ItemSource property):
At runtime our simple app will then display the data-bound Person names (note that we set the DisplayMemberPath property on the ComboBox above to display the "Name" value from our Person objects):
We could then implement a SelectionChanged event handler like below to run code when a person is selected from the ComboBox:
Notice above how we can retrieve a reference to the selected "Person" object from the databound ComboBox using the ComboBox’s "SelectedItem" property.
We can then call the MessageBox.Show() helper method (new in the RC) to display a modal dialog box that displays some details about our selected person:
The final release of Silverlight 2 will have a much more polished set of default control template skins than those that were in Beta1 and Beta2. Our goal with the default control templates is to have a look that is professional and attractive, can be used in the majority of applications as-is (without requiring you to author custom style templates), and which is also easily tweakable using Expression Blend.
Today’s RC build has skins that are close to the final look we plan to ship (there are a few final tweaks we are doing post RC on the focus color of controls, as well as to tighten up and tweak a few issues in some of the control templates). Below is the default look for the DataGrid, RadioButton, CheckBoxes, and the DatePicker controls with today’s RC build:
Note that the DatePicker control above allows users to type in a date (with a masked edit to ensure it is a valid date), or they can click the calendar icon to the right of the textbox and select the date using a popup Calendar control:
One of the most powerful features of Silverlight and WPF, of course, is the ability for designers and developers to completely customize the look and feel of any control. This goes beyond simple styling of colors and fonts – you can literally completely change the visual UI of a control, as well as customize its behavior (for example: add animation) without writing any code.
Within Expression Blend, simply right-click on any Silverlight control and choose the "Edit Control Parts" sub-menu to open and edit its control template:
When in control template editing mode, you can manipulate any sub-element of a control (for example: a checkbox’s inner content), as well as customize each "state" its in (notice the states pane circled in red below). This allows designers to customize what the control looks like in individual states (for example: checked, unchecked, mouseover, etc). Silverlight will then automatically handle animating the control from state to state depending on the user action:
You can learn more about how Silverlight’s Visual State Model works from my previous blog post here.
Previous releases of Silverlight often rendered graphics on sub-pixel locations – which could cause lines and shapes to sometimes appear "fuzzy". The RC of Silverlight has a new features called "layout rounding" that causes the layout system to round the final measure of a control to an integer ("pixel snapping"), which results in crisper lines and fewer rendering artifacts. This feature is now on by default, and helps make applications look nicer.
The final release of Silverlight is not that far off now. It has been a pretty amazing project that has come a long way in a pretty short amount of time.
If you have existing Beta2 applications, please start getting them ready for the final release – as once we release Silverlight 2, users that have existing beta releases installed will automatically be upgraded to use the final version. Testing your application out with the release candidate will ensure that you can easily update your applications and have them ready within hours of the final release.
Let us know if you find issues with today’s release candidate, and please make sure to post them on the forums on http://www.silverlight.net.
Hope this helps,
Scott
I’m a bit late because of my extended bout of 100% travel, much of it disconnected, but I thought I’d do a post about this anyhow because it is a very significant piece of news.
Microsoft has announced that what was previously being called BizTalk Server 2006R3 has been renamed to BizTalk Server 2009.
Why is this announcement important? Because, if you’ve been following my blog and others, you know that Oslo and a wave of other technologies is heading towards us, and that there will be a first-release of some of this at the PDC in October. Many people are probably wondering: what does this mean to existing BizTalk customers? Are their investments protected? Is there a migration path? Is migration something that needs to be done? The BizTalk Server 2009 announcement should go a long way to reassuring people that their investments are protected, and that there is a BizTalk future in Oslo-land.
In the announcement, Microsoft also reaffirmed their commitment to continuing to release new versions of BizTalk Server at 2 year intervals.
Key highlights of what will be in BizTalk Server 2009 are:
For more info:
Some teams use a Sprint 0 to prepare their product backlog, the infrastructure (development environment, CI server), … .Is this part of Scrum? Is it useful? http://www.infoq.com/news/2008/09/sprint_zero Subscribe in a reader Join my blog network on Read More……(read more)
Thanks to all the folks who attended to my presentation Taming Web Services Interoperability at Oracle Open World. I’ve really enjoyed presenting for an Oracle-centric audience and we got some great reception and feedback . I will make the demos available…(read more)
Me and Mikael are doing a technical usergroup talk around Business Activity Monitoring in Stockholm the 20th of october. Read more and signup here (in swedish)….(read more)
I recently encountered a bit of a “gotcha” when looking at how BizTalk receives WCF messages through its adapters. I expected my orchestration subscription for messages arriving from either the SOAP adapter or WCF adapter to behave similarly, but alas, they do not.
Let’s say I have two schemas. I’m building an RPC-style service that takes […]