Now that the Portable Library Tools are RTW...
I think there would be tremendous benefits in supporting this in Caliburn.Micro. In my case, we are using CM in a Silverlight app. The ViewModels are pretty light but there is sufficient code in there that I feel bad about not having ANY tests for them.
Existing Silverlight testing solutions are pretty rank (e.g. frequently require running the tests inside a browser, or require using an infrequently maintained fork of NUnit), compared to just testing a regular class library.
Ideally I would extract my ViewModels into a separate assembly/project from my Views and Bootstrapper, and the ViewModel assembly would be a Portable Class Library targeting both Silverlight 4 and .Net 4. Then I can easily write a .Net 4 unit testing project
that references the ViewModel assembly via a project reference.
The missing piece for this is for Caliburn.Micro Silverlight 4 version to expose PropertyChangedBase, Screen, IEventAggregator, IHandle, IViewAware (and probably quite a few others!) in a way that they can be consumed by a PCL assembly. I agree this is probably
I might have a look at this myself and see just how ugly it is to split things apart (if possible at all).