Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Enable NCrunch Disabled / Expired Version?

    Hi, You can solve the expiry issue by downloading a later version. Most likely the version you've been running is quite old. NCrunch will usually pop up with messages to let you know when a new version is available. I'm sorry if the timing was bad for you. Cheers, Remco

  2. Coverage shows black when tests cover code

    Hi Kris, Make sure your test project is referencing the project under test through the use of a <ProjectReference> tag in the .proj file, and not using a <Reference> to the project's output DLL. This is called a 'lost reference' and it prevents NCrunch from knowing about the relationship between…

  3. Support Visual Studio 11 Test executable (VSTest)

    Hi Marc, Thanks for posting! Yes, NCrunch will need to support MSTest's async tests. This will be done with some additional work to bring NCrunch up to speed with VS11 in the long term. Likely this will be done without the 'vstest.console.exe' though - as NCrunch requires greater control over t…

  4. Test metrics

    I suspect the answer may involve a bit of both. I've had a few people noting the lack of support for MSTest's code coverage control attributes.

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

    Hi Kaleb - Yes - this makes sense. The instrumentation step is also responsible for rewriting the assembly so that the links will point back to the original source code. Thanks for reporting this issue.

  6. Very long initalization time

    Thanks for sharing this. None of this looks particularly unusual except for the large generated files. Do you notice much of a difference in the pausing/lockups if one of the large generated files is open? I have a feeling that keeping the 11k line document open while NCrunch is running may be th…

  7. NCrunch erroneously detecting project build failure

    Hi Kaleb - Right now VC++ isn't officially supported by NCrunch - there is still more testing and fixing to be performed before I feel confident saying that these projects will work without a hitch. However, there's a chance we can still get this to work for you. Most likely the error informati…

  8. Very long initalization time

    Hi Marqus, Checking through the log file, it looks like this could be a performance problem that is causing the engine to seize up. Can you tell me a bit more about the solution/situation you're working in? Particularly I'm interested in: - A rough number of files/documents you have open i…

  9. Build failure - no space before base class

    Hi John, Thanks for sharing the news! I have a fix pending that should further strengthen the error handling around workspace creation, so if this issue still exists, it won't be around for much longer. If NCrunch is fixing the build errors without you needing to prompt it, then most likely this…

  10. IL Injection

    Hi, This is due to the instrumentation that NCrunch introduces in order to analyse code coverage at runtime. You can turn off instrumentation in your NCrunch project configuration, but note that by doing this you will lose code coverage for the entire project. My suggestion would be to use an "…

  11. Source code

    Thanks for your interest, it's always great to hear from people that are interested in helping with NCrunch and contributing to the project, but right now NCrunch is currently free closed source software and there are no plans in motion to open source it. The best way to help right now is to cont…

  12. Source code

    Nope.

  13. feature suggestion: discover/recognise NUnit's TestCase attributes

    Hi MM - If you manage to recreate the issue, can you push through a bug report? I suspect this may be a more subtle issue than the analysis type for the framework. Cheers, Remco

  14. The very large catch

    Hi Dan - Nothing is confirmed yet. But if there is a price, you can be sure it will be a fair one (and not $10k). Cheers, Remco

  15. "Undo" isn't regarded as a change?

    Hi, thanks for posting! Undo operations are considered the same as any other change to a source file, so it's far more likely that the change you made landed in an area that the impact detection didn't properly detect. Right now impact detection will only work for tests that actually have coverage…

  16. Visual Studio Express

    Hi - This actually has little to do with NCrunch and more to do with Visual Studio Express. VS Express does not support 3rd party packages such as NCrunch. So I'm afraid there are no plans to support VS Express in future. Cheers, Remco

  17. MetricsExclusions saved as absolute paths

    Yes, this makes good sense. Thanks for letting me know about the merge issues ... I'll see what I can do.

  18. Interference with normal debug

    Hi Patrick, NCrunch doesn't really have any connection with the normal build operation within Visual Studio, so if this issue is NCrunch related than it's likely to be indirectly so (which makes it very hard to track down). So far I haven't heard any reports of similar behaviour - though this is…

  19. Local variables unavailable when debugging

    For anyone interested, Will helped me to reproduce this problem and I was able to confirm that it was related to the manner in which the C# compiler handles the 'yield' statement. I'm currently looking into ways in which this can be fixed. To reduce the scope of the problem, it's recommended you t…

  20. Compile Errors Hyperlinking.

    Thanks - this helps a great deal. Next round of questions: - If you move the horizontal scrollbar far to the right so that the code is no longer visible (add lots of spaces if you have to), then try to navigate to the test, does the horizontal scrollbar move in any way? - Can you submit a bug…