Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Configuration errors in ncrunch solutions allowed by the UI
Options
Previous Topic Next Topic
Neilr
#1 Posted : Thursday, March 29, 2018 4:32:18 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/29/2018(UTC)
Posts: 2
Location: Ireland
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?
Back to top
Remco
#2 Posted : Thursday, March 29, 2018 9:40:46 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,161

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
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.
Back to top
Neilr
#3 Posted : Thursday, March 29, 2018 9:56:12 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/29/2018(UTC)
Posts: 2
Location: Ireland
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.
Back to top
 |  Edit by user
Remco
#4 Posted : Friday, March 30, 2018 12:28:15 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,161

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
That will work :) You can also inject configuration settings individually via the command line if they need to be different to your defaults.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.038 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download