This might be caused by the assembly name and namespace needing to match issue that came with the VS 2012 Update #1. I had to fix our code the other day for this issue when I updated the VS 2012 Update #1. Look at the <xyz>.g.cs file generated from your xaml in the obj folder and you can see what it's looking for. We were getting XamlParseExceptions in our code that isn't using Caliburn. A previous issue from CP to RTM was having a period in the name that caused a XamlParseException. That was fixed by not using periods or using underscores and MS had a hotfix as well.
↧