Hi,

I have a projec t that has user settings (i.e. in the Settings.Designer.cs), when NCrunch tries to run its unit tests it fails with the following,

SetUp : System.Configuration.ConfigurationErrorsException : Configuration system failed to initialize
----> System.Configuration.ConfigurationErrorsException : Unrecognized configuration section userSettings. (C:\...\AppData\Local\Remco_Software_Ltd\nCrunch.TestRunner.AppDom_Url_q2piuozo0uftcc2pz5zv15hpilzfpoqk\2.15.0.9\user.config line 3)
at System.Configuration.ConfigurationManager.PrepareConfigSystem()
at System.Configuration.ConfigurationManager.RefreshSection(String sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
at System.Configuration.SettingsBase.get_Item(String propertyName)
at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
...\Properties\Settings.Designer.cs:line 31

I've changed NCrunch to use the compatibility mode settings and I'm still getting the error.

Any ideas as to how to get NCrunch to use the project user settings? I'm using NCrunch v2.15 with Visual Studio 2013.
Thanks,
Chris.

In the solution explorer for a project there is a properties item which has a Setttings.settings item. You can add a setting by double clicking on the Settings.settings item. This brings up a settings window where you can view and add application settings. Visual Studio automatically generates a c# file containing your settings called Settings.Designer.cs.

In your code you can access the settings in your code with

var setting = Properties.Settings.Default.SettingName;

NCrunch is failing when it trys to access the setting with a ConfigurationErrorsException : Unrecognized configuration section userSettings.

Settings.Designer.cs is a file that the project knows about (since it generated it and shows it in the project), so I would guess that NCrunch would know about it for its workspace - although I could be wrong, I haven't used NCrunch that much.

Thanks,
Chris.

Hi,

I have got the app.config file that has the setting as follows,

<configuration>
<configSections>
<sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="....Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
</sectionGroup>
</configSections>
...
<userSettings>
<....Properties.Settings>
<setting name="LastScmLower" serializeAs="String">
<value>0</value>
</setting>
</....Properties.Settings>
</userSettings>
</configuration>

This file is included in the project. I've tried manually adding it to the NCrunch config for the project but it didn't make any difference.
Thanks,
Chris.

Hi, I've tried the compatibility mode and it didn't make any difference.
Chris.

Hi,

I looked at the user.config and it was for another project in another solution (that I also have configured with NCrunch). I deleted the file and ran the tests again and they are alll passing and the user.config looks sensible.

Thanks very much for all your help.
Chris.

Thanks Chris.

NCrunch itself does support multiple VS instances side-by-side. It can even work with multiple VS instances of the same solution. Care is taken to separate the workspaces between VS instances.

However, it's possible to run into problems where absolute file paths are involved. If you have two projects (in the same solution or different solutions) that both point to the same file on disk during their build or test run, then you'll likely have problems like the one you're experiencing with the user.config file.

The path 'C:\Users\...\AppData\Local\Remco_Software_Ltd\nCrunch.TestRunner.AppDom_Url_q2piuozo0uftcc2pz5zv15hpilzfpoqk\2.15.0.9\' isn't declared anywhere by NCrunch. It looks like this is some kind of shadow-copy directory being created by the runtime itself, using the nCrunch.TestRunner assembly name and version for the naming.

I'm afraid that I'm not sure which part of the runtime could be responsible for behaviour, but I recommend checking the config files involved to see if they have any settings regarding shadow copy or anything similar. The default setup for NCrunch itself is to avoid any kind of shadow-copying in the runtime, as NCrunch already does this with its workspacing. It is also possible that there might be something in your machine.config that is causing this.