Hi, thanks for posting!
NCrunch will use the default culture for any .NET application on your machine (whatever that may be). There isn't anything specific in NCrunch that tries to control the culture, and it can't be configured in the tool itself. If your tests are culture-specific, you can set the culture using a SetUpFixture (NUnit) or AssemblyInitialize (MSTest) block using the following code:
System.Threading.Thread.CurrentThread.CurrentCulture = new CultureInfo("en-GB");
Under NUnit, you can also use the
SetCultureAttribute.
Another possible situation that may cause this problem is if your project is making use of files in the resource manifest that are not included in the project file itself. NCrunch doesn't parse resource manifests, so it won't know about the resource files in order to copy them into
workspaces it sets up to build your project. There's a page in the documentation that describes ways in which you can handle
implicit file dependencies during project build. Although in theory the references to your resource files are declared explicitly rather than implicitly, NCrunch doesn't have enough knowledge of the workings of the resource compiler to understand the difference. You can either add the resource dependencies directly into your project file or use the 'additional files to include' configuration setting.
