I have installed all of the development tools for Silverlight 5 and retargeted my Silverlight 4 project to Silverlight 5.

I am having problems getting the solution to compile and I am guessing that they are because of conflicting references. I notice that the NuGet package for Caliburn.Micro includes - and adds references to - the following assemblies.

System.Windows.Controls (File Version: 4.0.50826)

System.Windows.Interactivity (File Version: 2.0.20520.0)

After installing Silverlight 5 on my machine, the following assemblies are the ones with the highest file versions.

System.Windows.Controls (File Version: 5.0.61118)

System.Windows.Interactivity (File Version: 2.0.20520.0)

Note that the version of the Interactivity DLL matches however the Controls DLL is higher. I am wondering if this is the cause of my problems.

Does Caliburn.Micro support the newer Controls assembly? Are there plans to do so?

The compilation errors are in my solution - there are hundreds so I am not sure which is the core and which are just knockon effects.

I made a little progress after making the post above. It looks as though one of my RIA Services DomainServices is not generating code on the client - still not sure why though. The web application that hosts it compiles fine.

Would you recommend that I leave the reference to System.Windows.Controls in my Silverlight application that came with Caliburn.Micro or replace it with 5.0.61118? Note that I am still not sure that this is actually causing my problems
- this is just something that looked a bit suspicious.

I would definitely try to update the Controls dll. I'll try to get an official SL5 build happening soon. Maybe I can do it next week. No promises. I've got a lot on my plate right now, but I'll do my best.

I rolled back to the pre Silverlight 5 version of my project and tried the upgrade again. I left the System.Windows.Controls reference alone (it is referencing the one in version 4.0.50826 in the Caliburn.Micro folder.

I am half expecting to have issues trying to use Silverlight 5 features in future but at least the solution compiles and runs.

I would be interested to hear about any plans you have to include version 5.0.61118.