We're constantly seeing these errors when running ncrunch via commandline, however, when we configure via the configuration editor in VS2017 (and setup the solution again), the values get put back:
The setting 'SolutionConfigured' was not loaded from the NCrunch configuration file at 'E:\xxx\xxx.v3.ncrunchsolution' because this setting has been declared in a scope where it is not applicable. Due to limitations in the engine, not all settings can be applied at all levels in the configuration system. If you are attempting to define this setting manually in XML, please inspect the configuration UI to see where it can be applied.
The setting 'AdditionalFilesToIncludeForSolution' was not loaded from the NCrunch configuration file at 'E:\xxx.v3.ncrunchsolution' because this setting has been declared in a scope where it is not applicable. Due to limitations in the engine, not all settings can be applied at all levels in the configuration system. If you are attempting to define this setting manually in XML, please inspect the configuration UI to see where it can be applied
Is this a known issue, or a problem in how we've setup the ncrunch configuration?
Daily Usage Issues
Configuration errors in ncrunch solutions allowed by the UI
Started by Neilr on 3,906 views
Remco NCrunch Developer
#11985
29 Mar 2018 21:40 UTC
Hi, thanks for sharing this problem.
This looks like you have may a difference in version between your commandline NCrunch and the one you're using in VS. Are the version numbers in alignment?
Or is it possible you're attempting to load a solution configuration file using the '/C' command line option? This option won't work very well with the solution configuration files, which get loaded by the console tool anyway when it reads the solution file. The /C command line option should always be used with global configuration files like those found in C:\Users\USER\AppData\Roaming\NCrunch.
This looks like you have may a difference in version between your commandline NCrunch and the one you're using in VS. Are the version numbers in alignment?
Or is it possible you're attempting to load a solution configuration file using the '/C' command line option? This option won't work very well with the solution configuration files, which get loaded by the console tool anyway when it reads the solution file. The /C command line option should always be used with global configuration files like those found in C:\Users\USER\AppData\Roaming\NCrunch.
That's probably be it, right now we're running:
& "$ncrunchConsoleRunner" "$VisualStudioSolutionFile" /O "$TestResultsOutputDirectory" /C "$NCrunchSolutionFile"
It sounds like we should just be running:
& "$ncrunchConsoleRunner" "$VisualStudioSolutionFile" /O "$TestResultsOutputDirectory"
We use most of the defaults when running ncrunch anyway, so don't need to create a separate global config file.
& "$ncrunchConsoleRunner" "$VisualStudioSolutionFile" /O "$TestResultsOutputDirectory" /C "$NCrunchSolutionFile"
It sounds like we should just be running:
& "$ncrunchConsoleRunner" "$VisualStudioSolutionFile" /O "$TestResultsOutputDirectory"
We use most of the defaults when running ncrunch anyway, so don't need to create a separate global config file.
Edited 29 Mar 2018 22:09 UTC
Remco NCrunch Developer
#11987
30 Mar 2018 00:28 UTC
That will work :) You can also inject configuration settings individually via the command line if they need to be different to your defaults.
Post a reply
Log in to reply.