Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Console Tool Not Building .Net Standard Library

    Thanks for your patience here. Something that I think would be worth trying on your machine is to create a small sample .NET Standard project with a .NET Core test project, then try running NCrunch over it and seeing if it fails. This will help to determine whether the problem is triggered by …

  2. Exclusively uses attribute per fixture type (NUnit) not working ?

    Without implementing your own Mutex, ExclusivelyUsesAttribute is the only way to create this kind of restriction inside the engine. Something you could try is splitting the TestFixture class into two derived classes each with their own attribute declaration. We do have SerialAttribute to determi…

  3. Console Tool Not Building .Net Standard Library

    Hi, thanks for sharing these problems. .NET Core/Standard has a very different build model to .NET Framework in that it is heavily dependent on Nuget and associated tooling. Bindings to packages must be directed through the Nuget system as we cannot guarantee that a package is actually present o…

  4. Exclusively uses attribute per fixture type (NUnit) not working ?

    Thanks for sharing this. The behaviour here is as designed, though it isn't intuitive. In this situation, it's the best we can do because of the design of the CLR. As far as CIL is concerned, attributes declared in the following manner have the same physical result in the assembly: [MyAttrib…

  5. Ncrunch is not observing the XUnit FactAttribute's Skip property

    NCrunch will usually build in debug mode, so I guess it will never skip this :)

  6. Why is not NCrunch aborting build/analysis on pending grid nodes when no work remains?

    Ok, although I can agree that the experience here is certainly suboptimal, I think there is an argument for saying that this is probably behaviour as designed. TC is reporting this build as likely hung, because in a manner of speaking, it probably is. NCrunch is stuck on a restricted resource on…

  7. Ncrunch is not observing the XUnit FactAttribute's Skip property

    Hi, thanks for sharing this issue. I hope you're ok with me asking a few questions about your environment. This seems to be working correctly at my end, so there must be a variable here somewhere. - Which version of .NET are you using? (i.e. .NET Framework, .NET Core, etc) - Which version of…

  8. No way to navigate to stacktrace without mouse in exception details window

    Thanks for sharing this. We'll take a look at it and see what we can do :)

  9. Codesmith Task Failure

    [quote=pglaspey;13250] This is going to Dev Ops and other developers, so I cannot rely on this being in the gac. We have 4 developers using ncrunch and right now this is preventing us from using it, well we are using it but our unit testing productivity is nil until this is fixed. [/quote] S…

  10. Codesmith Task Failure

    Thanks for your patience on this. I've set up a trial license with CodeSmith and in doing so I've managed to reproduce this problem. To properly fix this, we'll need to make a code change to NCrunch to give it more generous search logic when resolve build-time references. To get you working, th…

  11. Codesmith Task Failure

    Can you confirm whether the version of System.Collections.Immutable you've found is v1.2.3.0? When I look in my CodeSmith.Generator.Task.8.0.0 package, it looks like the bundled version is v1.2.1.0. I think there is a redirection happening somewhere in your NCrunch build system that is trying to…

  12. Why is not NCrunch aborting build/analysis on pending grid nodes when no work remains?

    [quote=GreenMoose;13237] So maybe there are some places missing "TC progress report" by NCrunch Console, causing TC to think build is hanging on when slow grid nodes are in use. [/quote] Was there any other activity during the hang-up that NCrunch was reporting internally but was not being repo…

  13. Build Fails in NCrunch for depencies but not in VS

    Hi, thanks for posting. When NCrunch processes your project, it will shadow copy it into a background workspace and redirect most references in this project to an _ncrunchreferences directory inside that workspace. So the path above doesn't necessarily look wrong, but it's concerning that the fi…

  14. Codesmith Task Failure

    This looks like a binding redirection issue. Could you see if you could find the System.Collections.Immutable (v1.2.3.0) on your machine (probably it's in your local nuget package cache or .NET Standard installation directory), then copy this to your '\packages\CodeSmith.Generator.Task.8.0.0\buil…

  15. Codesmith Task Failure

    This looks like a versioning issue of some kind. In the Nuget package I've downloaded for CodeSmith.Generator.Task.8.0.0, the CodeSmith.Engine DLL is v8.0.0.0. I assume it's the same in your Nuget package. Are you using different versions of CodeSmith inside the same solution? Could you try …

  16. Codesmith Task Failure

    Could you try turning on fusion logging? Maybe this can tell us why the search paths aren't lining up with the file locations.

  17. Codesmith Task Failure

    Hi, thanks for sharing this issue. If you inspect the contents of the NCrunch workspace generated for this project (i.e. C:\Users\Patrick Glaspey\AppData\Local\NCrunch\8232\47\src\packages\CodeSmith.Generator.Task.8.0.0\build\..\tools) as accessible from the 'Advanced->Browse to workspace' contex…

  18. Educational License

    Hi, thanks for posting. Sorry, as we're only a very small business, we simply don't have the scale to administer or support a separate licensing tier for educational purposes. So I'm afraid not.

  19. VS 2019 support

    The biggest problem with VS2019 is that it now forces extensions to integrate their bootstrap sequence asynchronously. This creates a wide scope for inconsistencies when dealing with tool windows. It will be difficult for us to troubleshoot these sorts of problems as they are likely to be very…

  20. 4 Version of Visual Studio?

    How the times have changed! This was a good catch, thanks for letting me know. I've fixed this now.