make "First Time Crunch" Dialog for each new solution optional.
I, and I'm sure others as well, use a similar, if not identical, NCrunch configuration for each solution. So I would suggest making the "First Time Crunch" dialog optional for new solutions. If disabled, a default configuration could be applied to each new solution.
There are some conflicting views about how this wizard should be improved. I’ve tried to tackle the underlying design issue with the new V3 release. I hope this should get rid of the frustration everyone is experiencing here.
toby carter commented
or just default to:
* run my tests alongside each other,
* run automatically when changes are detected,
* run them all - i'll ignore as i need.
does anyone else use anything different? that seems like the setup you'd want for TDDing ;)
Ryan Lundy commented
I find myself clicking through to set the same several settings over and over again. For instance, if I'm going through a Pluralsight course and typing along, I might create ten or twenty different VS projects along the way. I want to use NCrunch with them to quickly catch problems, but I want NCrunch to remember my usual settings.
Perhaps instead of the several-step wizard, the first page could have two buttons, e.g.: "Use my standard settings" and "Configure NCrunch for this solution".
Or better yet, next to "Enable NCrunch" in the menu, have an "Enable NCrunch with my usual settings" menu item that would skip the wizard altogether.