Forum member

mattyboy

17 posts

Posts by mattyboy

  1. version 1.17.0 of Microsoft.Azure.Functions.Worker.Sdk makes ncrunch look for .net6

    I'm still seeing the same issue. With NCrunch 5.9.0.1 and Microsoft.Azure.Functions.Worker.Sdk > 1.16.4.

    01 Aug 2024 03:48 UTC

  2. .NET Core 3.1 - The FrameworkReference 'Microsoft.NETCore.App' was not recognized

    Hmm, so before I opened this thread I thought I'd try rebooting my laptop "just in case", but NCrunch still didn't work. But now, when I booted up my laptop again and opened the solution, NCrunch is happy and works. Not sure why. Happy to close this for now... maybe there is an issue when peop…

    13 Dec 2019 06:01 UTC

  3. .NET Core 3.1 - The FrameworkReference 'Microsoft.NETCore.App' was not recognized

    Hi Michael Yes, it is using that package. In fact, I am the author of that package! Is there something wrong with it? Matt

    13 Dec 2019 05:52 UTC

  4. .NET Core 3.1 - The FrameworkReference 'Microsoft.NETCore.App' was not recognized

    Today I upgraded my .NET Core 2.2 application to 3.1. My solution builds fine in Visual Studio but NCrunch fails to compile my application. ..\..\..\..\..\..\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets (283, 5): The Framew…

    13 Dec 2019 03:09 UTC

  5. NCrunch 4 - Instrumentation Mode - Optimized - "The name [x] does not exist in the current context"

    Thanks for the fix Remco - I can confirm it's working with my solution :-) What was the underlying cause? Was it something funky in my solution? Matt

    10 Dec 2019 03:42 UTC

  6. NCrunch 4 - Instrumentation Mode - Optimized - "The name [x] does not exist in the current context"

    Hi Remco. Hmm. I just spent about half an hour stripping out most of the functionality from my solution, so I was just left with one controller and a few test classes, so that I could upload it to you. Switched to Optimised mode = it now builds and runs. So then I switched back to my develo…

    29 Nov 2019 02:40 UTC

  7. NCrunch 4 - Instrumentation Mode - Optimized - "The name [x] does not exist in the current context"

    [quote=Remco;14155]Hi Matt, Could you submit a bug report for me after this happens? Something must be failing internally.[/quote] Sure. I just submitted one. Matt

    28 Nov 2019 03:19 UTC

  8. NCrunch 4 - Instrumentation Mode - Optimized - "The name [x] does not exist in the current context"

    Hi Remco I've downloaded the VS2019 version of NCrunch to try it out. However, my solution fails to build with Optimised mode enabled: [img]https://i.imgur.com/4QN5arC.jpg[/img] Annoyingly, I can't see why it's failing to build. Fortunately, Legacy mode still works fine. Matt

    28 Nov 2019 00:49 UTC

  9. NCrunch 4 - Instrumentation Mode - Optimized - "The name [x] does not exist in the current context"

    Hi When debugging my .NET Core 2.2 project (XUnit 2.4.1), if I have an exception in my test code, I can't hover over other variables in the method and see their values. If I try Quickwatch, it says "The name [blah] does not exist in the current context". Optimised mode: [img]https://i.imgu…

    11 Nov 2019 01:24 UTC

  10. .NET Core 3.0 preview and System.Runtime version=4.2.1.0

    Yes, that build works. Thank you.

    02 Jul 2019 21:19 UTC

  11. .NET Core 3.0 preview and System.Runtime version=4.2.1.0

    Hi, My test project fails to build in NCrunch (but builds fine in Visual Studio). The error message reads: [code=plain]Assembly 'Swashbuckle.AspNetCore.Filters' with identity 'Swashbuckle.AspNetCore.Filters, Version=5.0.0.0, Culture=neutral, PublicKeyToken=aa1e9c5053bfbe95' uses 'System.Runtime,…

    01 Jul 2019 22:40 UTC

  12. Use Roslyn build

    Hi again, Just to add to this, it did seem like the amount of time NCrunch took to analyze was a lot longer than the Sleep time in my attribute. E.g. the sleep time was set to 10 seconds, but NCrunch's build step would take around 60 seconds. So the attribute must be enumerated multiple times... …

    14 Mar 2018 10:56 UTC

  13. Use Roslyn build

    OK so I've spent a day in order to fix this. The problem is we use a custom Autofixture [AutoData] attribute on every test. Our attribute's constructor creates a TestServer for running the web tests against. https://docs.microsoft.com/en-us/aspnet/core/testing/integration-testing We then inje…

    27 Feb 2018 12:28 UTC

  14. Use Roslyn build

    Just a quick note to say that I'm already running 3.12, so I will continue the investigation into the underlying cause.

    24 Feb 2018 10:54 UTC

  15. Use Roslyn build

    Hi Remco, Your help is appreciated! Here's the results. csv results here: [url=https://www.dropbox.com/s/h59i6u47kldx2z3/ncrunch.csv?dl=0]https://www.dropbox.com/s/h59i6u47kldx2z3/ncrunch.csv?dl=0[/url] It seems to be the "\Discover tests\Augment test discovery results with NCrunch metad…

    23 Feb 2018 09:24 UTC

  16. Use Roslyn build

    Hi, I've been using NCrunch off and on for a few years. Have been using it happily for the last few months on a greenfield solution, which has grown as our team has added code. As of the couple of weeks or so, NCrunch has slowed right down. As an example, I just changed some code in one of my tes…

    22 Feb 2018 15:15 UTC

  17. Ncrunch Fody ContainsTypeChecker

    [quote=Jonh04;5990]I think I was able to deduce what the problem was. It seems one project has a dependency to a newer fody package, changing this to align with the other projects seems to have made it go away. A better message would be useful. Telling me that the version is incorrect, instead o…

    02 Jul 2015 08:38 UTC