Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch 3.7 causes VS 2017 to crash if you edit a .NET Core csproj file

    I hope to have a fix out for this in the coming week. Sorry for the time it's taken here, this is a very complex area of the product.

    20 May 2017 23:06 UTC

  2. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    [quote=alastairs;10428] Something I'm not clear on, probably my misunderstanding, is the project vs. assembly reference behaviour you mentioned. We have project references defined between our test and production projects, so presumably the production project appears in the tests' deps file and Test…

    20 May 2017 11:26 UTC

  3. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    Hi Alastair, Thanks for sharing this problem with the code sample to reproduce it. This one took some serious head scratching and digging around to figure out. Unfortunately it's not a simple one to solve :( The TestHost package uses the data within the .NET Core .deps file to identify proje…

    20 May 2017 01:03 UTC

  4. Error occurred while analysing project

    Hi, thanks for sharing this problem. When NCrunch builds a .NET Core task environment, this environment has a dependency on a range of common Nuget packages. These packages are usually automatically downloaded by NCrunch when it first encounters a .NET Core project. It looks like this just wasn…

    19 May 2017 23:20 UTC

  5. System.Xml.ReaderWriter not found when running ASP.NET Core projects in NCrunch

    [quote=alastairs;10419]I think I've found it - another project in the solution is explicitly referencing System.Xml.ReaderWriter at a lower version than the one expected by the ASP.NET Core project above. Thanks for being my rubber duck :)[/quote] Great find! Thanks for letting me know :)

    19 May 2017 23:06 UTC

  6. Fixture is marked red X only due to ignored failing tests

    Hi, thanks for sharing this issue. I have seen edge cases before where the fixture is marked as failing while child tests are all green. I think where I've seen this it's usually been because the engine was set not to execute tests automatically, and I deleted a failing child test. I guess it m…

    19 May 2017 23:06 UTC

  7. NCrunch tries to build Docker Project

    Hi, Thanks for sharing this. I wasn't aware of this project type. I'll add it to the auto exclusion list.

    19 May 2017 22:57 UTC

  8. System.Xml.ReaderWriter not found when running ASP.NET Core projects in NCrunch

    Thanks. Unfortunately I don't see it really being possible to troubleshoot this problem without a buildable project/solution that can reproduce it. I don't think this will be a simple problem to pin down, and the .deps file is only a small piece of the puzzle here. It's my experience that other t…

    19 May 2017 12:18 UTC

  9. Multiple markers when renaming class with ReSharper

    [quote=alastairs;10412]Yes, it's reproducible consistently :)[/quote] Thanks for confirming! I'll take a look :)

    19 May 2017 12:10 UTC

  10. NCrunch gets stuck on outdated code

    Thanks Tim. A few more questions: - Are you using shared projects? - Has this issue ever given you a build error? Or does it only seem like the test results are out of date? - Are you using .NET Core/NetStandard?

    19 May 2017 05:15 UTC

  11. NCrunch gets stuck on outdated code

    Hi Tim, From what you've described, this is primarily not an impact detection issue. That isn't to say you aren't also suffering from an impact detection issue, but I don't think this is where we should be focusing if re-running the test does not produce an expected result. It's concerning th…

    19 May 2017 03:26 UTC

  12. TargetInvocationException

    Hi, thanks for sharing this. v3.7 did include a fix for this problem, so I'd hoped we'd seen the last of it. It hasn't been showing up anymore in my tests .. but I guess it's still there :( I'll try something else. Thanks again for letting me know about this.

    18 May 2017 22:03 UTC

  13. NCrunch gets stuck on outdated code

    Hi, thanks for sharing this problem. Are you using the 'Run impacted tests only' engine mode? If so, then this is probably caused by holes in the impact detection. Does using the 'Run all tests automatically' mode solve this for you?

    18 May 2017 22:01 UTC

  14. TestCaseSources enumerated unnecessarily

    [quote=bartj;10404] Now that I've updated my configuration and tried this feature, I potentially have a solution to the problem. I am, however, left wondering why it's under the "Advanced" menu... are there some gotchas or risks involved in using this?[/quote] No risks at all. It was placed und…

    18 May 2017 22:00 UTC

  15. Local variables unavailable when debugging

    NCrunch ships with xunit v2.1, which is usually found at C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2017\Modules\XUnit2. There are plans to upgrade it to xunit v2.2, which will involve some integration changes to …

    18 May 2017 07:31 UTC

  16. TestCaseSources enumerated unnecessarily

    Hi, thanks for sharing this issue. The code you have here is being executed inside the TestCaseSource code block, which means that NUnit will invoke it every time it needs to build an in-memory model of the test suite. NUnit will build the test suite every time it is initialised for a particular…

    18 May 2017 02:55 UTC

  17. NCrunch starts building tests before solution is completely loaded

    Hi Thomas, This is by design, because of changes MS made to the solution handling in VS2017. Under VS2017 lightweight solution mode, it's normal that most projects won't be loaded when the solution is first opened. Instead, VS will load them on demand. Because VS also loads projects asynchro…

    17 May 2017 22:30 UTC

  18. System.Xml.ReaderWriter not found when running ASP.NET Core projects in NCrunch

    References of this sort are usually resolved implicitly by the Core CLR using the .deps file. My first thought is that perhaps this is trying to resolve the wrong version of this assembly for some reason. Are you able to build a sample project that can reproduce this issue and you can share with…

    17 May 2017 10:20 UTC

  19. Multiple markers when renaming class with ReSharper

    Hi, thanks for sharing this problem. Can you confirm whether you can reproduce this consistently using ReSharper rename? Does it ever work correctly when you do this?

    17 May 2017 09:59 UTC

  20. Impact detection does not detect added constructor required by Moq

    Hi, thanks for sharing this problem. This is definitely a hard one. The critical dependency here sits on the result of a reflection call inside an uninstrumented library, so without instrumenting Moq or hacking the CLR, I'm not sure yet of a way to handle such a complex case. I'll have a think …

    16 May 2017 22:19 UTC