Silverlight 5

Diversion

Okay so this post was supposed to be the next part in the trilogy regarding the FormViewModel class hierarchy however as with all good plans, this one ran into an unexpected event – the release of Silverlight v5 – not only that but the Async CTP was also updated to remain compatible too – that meant the composition framework could be updated and that is why the next stage in the trilogy has been usurped by this post!

Abstract

To build the new version of the composition framework lead to some interesting issues – first off I needed to recompile the common service locator, unity and the rest of the enterprise library (v5) to target the latest v5 bits (otherwise you end up with a mix of CLR versions) not difficult but that lead to changes in the version of assemblies used in downstream projects which was a real pain (one solution in particular has over 100 project files around half of which needed modifying)

However all that was done in a serious session – the next task is taking advantage of the new v5 features – this is a much more subtle undertaking.

Thankfully this is more of an issue with applications using the composition framework rather than the composition framework itself although the DataContextChanged event is one which will need to be taken up in the refactoring – the current code makes use of attached properties via a binding shim to achieve the same…

Update

The codeplex update will arrive in due course – I am still validating the current build – only last week I found a weird bug in the FormViewModel/Form code – interesting since I was only just blogging about that – so that needs to be investigated properly…