My typemock and nunit test code works and runs fine in SharpDevelop.
I'm trying to build the project now from NAnt which also calls out the MSBuild for individual projects.
There are multiple project and solutions to build in this script and some of the projects target 3.5 but most target the 2.0 framework.
However, after much experimentation with <typemockstart>
It forces the MSBuild to only use 2.0. Therefore my Isolator code with lambda syntax won't compile.
If I change it to mention the higher framework:
<typemockstart>
Then NUnit pops up a box saying that I must install the 3.5 .NET framework---but it is already installed.
It seems like typemockstart assumes all the projects will be the same framework and somehow forces MSBuild to use only that one framework.
Here's the strange thing. After experimenting with moving typemockstart around in the script, it turns out that:
1. If typemockstart is before the compile, it fails on the first project that uses 3.5 c# features.
2. If typemockstart is moved after some of the projects, they compile fine and then the ones later which also use 3.5 fail.
3. If you comment out the typemockstart entirely (and comment out the NUnit test run) then the whole script builds fine.
What does typemockstart actually do?
It seems like it has kind of black magic that's really hurting my builds. Or maybe this is all user error.
Please help.
Wayne
