Forum member

kalebpederson

25 posts

Posts by kalebpederson

  1. Hyperlinks in test failures point to NCrunch copy of the file

    When I disable instrumentation of the test assemblies the hyperlinks generated on a test error result in a link to NCrunch's version of the file: [code=plain]System.Exception : An error occurred in Method: The given key was not present in the dictionary. at MyTest.TestMethod() in c:\users\kpe…

  2. NCrunch erroneously detecting project build failure

    After actually looking at the stack trace I decided to disable instrumentation for that project and now my solution builds, which is plenty good for now. Thanks for the help. --Kaleb

  3. NCrunch erroneously detecting project build failure

    You're right, the Processing Queue window contains more information: [code=plain][13:56:10.9226-BuildTask-50] ERROR (Compilation): My.Interop.Project: (0): System.ArgumentException: Value does not fall within the expected range. at Mono.Cecil.ModuleWriter.WriteModuleTo(ModuleDefinition modul…

  4. NCrunch erroneously detecting project build failure

    I have a VC++ project that I'm building with CLI/CLR support. It builds successfully but NC seems to think it failed. If I go to the directory where NCrunch placed everything I can see the output assembly and/or compile the project on the commandline successfully. How can I debug this? Thanks.…

  5. Can't examine symbols while using NCrunch to debug

    I just used the "Break into the first covering test at this line" menu to try to debug an issue, but I can't examine most of the in-scope symbols for some reason though they're all present and everything works as expected when I use R#'s test runner. The variables don't show up in the "Locals" view …