Hi folks, welcome to Monday…so I thought.

Here I was registering a message inspector which should take 5 mins tops.

Find the right config, make sure the .NET full assembly name is cool and away we go.

I wanted to use this guy from my custom WCF Adapter within BizTalk – so I needed my new message inspector to be seen by BizTalk.

So I used:

<add name="wcfMsgPropPromoter" type="Breeze.WCF.Extensions.BreezeMessagePromoteBehaviour,Breeze.WCF.Extensions,Version=1.0.0.0,Culture=neutral,PublicKeyToken=c2c8c7e827e9dd6a"/>

and added this guy to the <behaviorExtensions> element in the Machine.Config for .NET 4.0 x64/.NET 4.0 (& .NET 2.0 for good measure)

As if a scene from SpongeBob,… 3 hours later….

I had triple check GACs, caches, full assembly names etc…Scotty popped his head around and said “Oh yeah I had this one ages ago you need to use this…”

<add name="wcfMsgPropPromoter" type="Breeze.WCF.Extensions.BreezeMessagePromoteBehaviour, Breeze.WCF.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8c7e827e9dd6a"/>

Can you spot the difference?

SPACES!!!!

Interestingly enough – this work is part of a .NET plugin I wrote for IIS 7.5 and to register the plugin you use “Breeze.WCF.Extensions.BreezeMessagePromoteBehaviour,Breeze.WCF.Extensions,Version=1.0.0.0,Culture=neutral,PublicKeyToken=c2c8c7e827e9dd6a"

NO SPACES!

My head hurts for a Monday…

Hopefully you reclaim the hours I’ve lost here.

Mick.

Hi folks, as you may/may not have been aware these are the core corner stone technologies of the MS Integration Stack.

The teams have been busily plugging away and coming up with the new versions – 4.5 corresponding to .NET 4.5 framework.

Here’s some links that describe what’s new from MS Santa & his elves:

1. What's New in Windows Communication Foundation 4.5

1. New Items I found of note are:

• New Service Transport Default values – keep an eye on these.
• Improvements from VS.NET 2011 – validation , better intellisence support.
• Streaming improved – true async (yay!)
• WebSocket support – through NetHttp(s)Binding
• Single WSDL file generation with ‘?singleWSDL’ (which is pretty handy)
• Self hosted + II hosted allow you to get to ServiceHost from code for dynamic configuration.
• Binary Encoder supports compression!! – this is generally gzip compression.
• My personal favourite – UDP support
  

1. New Items of note are:

• New Activites – NoPersistScope (possible previously but we needed to write code)
• WF Designer improvements – several here, but the ‘Outline view’ looks to be easier to work with.
• C# Expressions – where’s the F# ones ??
• Designer Annotations – add your own comments to keep control of the jungle that is built.
• WF Versioning – use WorkflowIdentity & DefinitionIdentity to define the version. WorkflowServiceHost supports multiple versions of the same WF. All pretty cool.
• WF Designers can still be rehosted – I’ve used that many a place.
• Contract First Development – ticks the boxes.
  

1. Will have to check out perf in this new land on these rules.
   

Async CTP – while this didn’t make the ‘whats new’ list, it certainly does deserve a mention here.
Over the last year I’ve built some pretty serious F# projects, and F# has the async support through and through the language. After over coming the challenge of learning it, the Async functionality is absolutely brilliant!!! F# does a great job in being able to turn a non-async chunk of code/method/class into an async one with by using the keyword async and a !. It’s straight forward from that aspect.

It’s great to see the C# & VB.NETs being able to use the same fundamentals (albeit not as slick IMO ). – see a previous POST - http://blogs.breezetraining.com.au/mickb/2011/04/26/EasierAsyncProgrammingComingToCVBSoon.aspx

As developers we sit here and say – what do I need this for? My code runs fine as it….and yes for the most part of what we do on our machine it does. This technology really comes into it’s own when you want consistent throughput from a solution with 1 person or 10000 concurrent people using it. That’s the difference.

To use it:

1. Get VSNET 2011 (as it requires a new compiler)
2. Use ASYNC CTP (refresh3) with VSNET2010 SP1