Forum member

Vincent

7 posts

Posts by Vincent

  1. nCrunch fails building code containing languageext's newtype

    [quote=Remco;15830]Hi, thanks for sharing this issue. There's been a number of fixes in this area over previous years. The exceptions thrown here before the latest version of the product are from issues that have already been resolved. I haven't seen this before on v4.11 however. [/quote] …

  2. nCrunch fails building code containing languageext's newtype

    With version 4.0.0.2, the error is slightly different: NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues System.ArgumentOutOfRangeException: L'argument spécifié n'était pas dans les…

  3. nCrunch fails building code containing languageext's newtype

    Using Visual Studio 2019 and Ncrunch 4.11.0.2, I have the same issue (not sure it's the same cause): [PID:21844 15:45:30.7343 LocalBuildTask-56] ERROR (Internal): System.IndexOutOfRangeException: L'index se trouve en dehors des limites du tableau. à nCrunch.Compiler.Cil.Types.CilNestedClassTa…

  4. Setting Console output and error report

    I found a workaround: wrapping the assert in a try catch, writing the exception to the Console.Error output stream and rethrowing it: [code=csharp]try { StreamWriter standardOutput = new StreamWriter(Console.OpenStandardOutput()); standardOutput.AutoFlush = true; Console.SetOut(st…

  5. Setting Console output and error report

    I have the following NUnit test: [Test] public void Test() { StreamWriter standardOutput = new StreamWriter(Console.OpenStandardOutput()); standardOutput.AutoFlush = true; Console.SetOut(standardOutput); Assert.That(1, Is.EqualTo(2)); } The NCrunch Tests window reports t…

  6. OneTimeSetUp is called more than once per assembly

    Thanks for the answer. I read the page you quoted, but wasn't sure it would apply in my case. Maybe the page could be update to refer to the OneTimeSetUp attribute? I'll use a static field to indicate that the setup has already done. Another option you didn't mention is to add a OneTimeTearDow…

  7. OneTimeSetUp is called more than once per assembly

    Per definition: "This attribute is to identify methods that are called once prior to executing any of the tests in a fixture. It may appear on methods of a TestFixture or a SetUpFixture." (https://github.com/nunit/docs/wiki/OneTimeSetUp-Attribute) My solution contains two assemblies: one for my …