Hi: I enjoyed playing with Pex and Moles ... now it's time to use it seriously to cover the legacy application as much as possible.
We started by converting to .NET 3.5 (the client cannot yet host in .NET 4.0)
We noticed that we are having problems getting Moles to work.
It seems that if the Test Project assembly is .NET 4.0, but when you convert the Unit Tests assembly structure back to .NET 3.5 (after installing Visual Studio 2010 SP1 to provide this feature), it stops working.
Saves complaints about "you can run tests only with the default host adapter from the test assembly for the .NET framework 3.5"
If the client wants everything to be in .NET 3.5 - including unit tests ... any ideas?
source share