Trying to run my solution with the console tool and currently I always get build failure due to our Wix setup projects cannot load.
1) We have, in vstudio's configuration manager, disabled build for the setup project except for "Setup" build configuraiton. Should NCrunch really try to build it anyhow or is the error occurring even before NCrunch has the chance of determining if it should be built or not?
2) The project errors are from *.wixproj files. Is it a but or do I need to do something for them to play nice with NCrunch?
System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> nCrunch.Common.UserException: Errors occurred while trying to load the project file:
The target "ResolveKeySource" does not exist in the project.
at nCrunch.Compiler.RemoteBuildRunner.(FilePath ,   , String , String , DirectoryPath , String )
WiX projects aren't really supported by NCrunch. They use a different set of build targets and generally aren't needed in a test environment. The best plan would be to make sure the project is ignored by NCrunch using the 'Ignore this project completely' configuration setting. As long as the .ncrunchproject file is checked into the VCS, the console tool will read the ignore flag and avoid trying to load the project.
NCrunch doesn't use the VS build manager to determine which projects to build. Everything depends upon the 'Ignore this project completely' flag.
The project type GUID for the above project is FAE04EC0-301F-11D3-BF4B-00C04F79EFBC
With this information, I can instruct NCrunch to automatically ignore the project without needing additional configuration. Some project types are implicitly ignored by NCrunch's IDE integration, which isn't fully aligned with the loading logic in the console tool. Coding in this project type will bring us one step closer in aligning the two :)