Using 1.32b, NCrunch does not appear to be using the current configuration and platform selection as set within the IDE for when it builds and tests code. It instead appears to be using only the default configuration and platform in the csproj files. Modifying each of our projects to include such defaults is certainly doable on a one-time basis but NCrunch would provide an easier out-of-the-box experience by respecting my in-IDE choices.

Is this a bug report or a change request? :)

Additionally, there may well be tests I need to run for both x86 and x64, and it would be very inconvenient to have to repeatedly edit all of the csproj files to change their default platform until such time as NCrunch picks up the current in-IDE choices. Luckily I do not need to do this quite yet but it came to mind while writing this post and would be quite a pain so I thought it best to mention.

Thanks for responding so quickly.

Unfortunately, any project or solution changes I am forced to make that are entirely specific to NCrunch will not pass review, so otherwise-unjustified additions to the list of build configurations and/or use of the NCrunch environment variable are out the window, I'm afraid.

I've been able to sell the AssemblyInfo file modifications from my other thread on the basis that those assembly attributes are essentially deprecated, and was able to twist some arms to get the project default configuration and platform settings pre-approved but that will only cover a single configuration (which will be our x86 one since we test that more often than x64.)

I won't be able to use NCrunch for x64, though, since I'm not inclined to editing dozens of project or NCrunch configuration files every time I need to switch, and would in any case still suggest that NCrunch pick up the IDE build configuration and platform either for release or not long thereafter.

To be clear, I still hope to use NCrunch as much as possible. I'll take care of the previously-noted changes as soon as I can and post back up once I've either found success or am next in need of assistance.

I'd need to see an example of what you have in mind to be sure, but with a few assumptions it should do the trick for my current needs. So long as these properties you intend to inject are to be set in NCrunch's configuration window for the whole solution, not once per project, that is.

All said, not respecting the IDE's current build configuration and platform still sounds like a feature gap to me. Some of the solution-level build configurations I'm faced with reference differing project-level build configurations and your build-property-injection idea almost surely wouldn't cover that. Not to mention that most users would expect NCrunch to follow the IDE build configuration and platform as they change them. I expect to buy NCrunch for my own use on the job but things like this may well affect my ability to sell the idea to the rest of the team.

I hear you loud and clear on the potential for issues running tests against any random configuration/platform combo whenever one happens to be selected in the IDE. It isn't so much of an issue here but I can definitely see how it could be elsewhere.

At an absolute minimum I can get away with debug x86 (which will already be addressed through the csproj changes I've been able to get pre-approved, as much as there could be nicer out-of-the-box ways to do it) and can use other tooling to manually run the test suite for other configurations and/or platforms.

One step up from there would give me a way to use NCrunch against the x64 output when I'm in the midst of a period of x64 development, without requiring an inordinate amount of effort to switch to that platform and back once I'm done.

Everything beyond that helps progressively round out the product, of course, and helps me sell it to the rest of the organization, but I can't say quite yet what the drop-dead requirements would be in order to get wider adoption here. All I can say for sure at the moment is that if I can get NCrunch running for debug x86 on my own workstation you'll have at least one sale, and pretty much regardless of price. :)