Nov 9, 2011 at 11:30 AM
Edited Nov 9, 2011 at 1:22 PM
We tried to reproduce the error that you are describing by updating various QuickStarts included in the Prism guidance to the
Unity 2.1.505.0 version using the NuGet manager, but we couldn’t reproduce your problem (all the QuickStarts worked properly). We tried this using both
.NET Framework 4 and .NET Framework 4 Client Profile in the QuickStarts' projects when applicable, but it worked appropriately as well.
Also, we updated the Prism library to the Unity 2.1.505.0 version, ran its tests and found that they all pass. It seems that your problem might be caused by a missing reference.
You can find a version of the Modularity QuickStart with Unity using the
Unity 2.1.505.0 version in this
SkyDrive account (under the name ModularityWithUnity2-1-5.zip). This sample might be useful for you to compare your solution to it, so as to find possible differences that might be causing the exception you mentioned.
If this does not help you solve your problem, it would be helpful if you could provide us with a repro sample application, so we can help you troubleshoot it.
I hope you find this helpful.
Guido Leandro Maliandi