Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. "Error 1316. The specified account already exists." when installing for VS2019 with Chocolatey

    [quote=LucasT;13352]That's a custom chocolatey script though, so I don't expect you to maintain it. I just shared the issue in case it would ring a bell.[/quote] Sorry no ideas here :( Working with MSIs tends to be a bit of a minefield of problems like this.

  2. "Error 1316. The specified account already exists." when installing for VS2019 with Chocolatey

    Thanks for sharing this issue. Unfortunately this problem is outside the boundaries of what we are able to provide support for. We ourselves don't maintain support for chocolatey installers for NCrunch, so to troubleshoot a problem like this we would need to introduce and maintain an entirely ne…

  3. "Goto next failing test" not working for cached failure after vstudio restart?

    Thanks for sharing this issue. The problem does appear to be consistently reproducible in the way you've described. I'm not sure yet why this is happening, but we'll look into it :)

  4. Make "Check for updates" menu

    [quote=InfrastructureGjensidige;13343]All of modern tools have possibility to check for updates in menu (or about page). I know that it is not trivial, but is it possible to implement? Thank you. P.S. (Why Feature Suggestions is Locked?) [/quote] Thanks for posting. Yes, this is possible, and …

  5. Upgrading license after company merger

    Hi, thanks for posting. The short answer is Yes. When purchasing an upgrade, the new licence is issued under the name of the purchasing company and not under the name attached to the previous licence.

  6. Problem with Fakes

    Thanks for sharing this issue. As VS2019 is still very new, we haven't yet had a chance to integrate with MSFakes in it. We hope to implement this very soon. For now I recommend sticking with VS2017 if you need MSFakes with NCrunch.

  7. NCrunch Test Window shows tests still running

    Nice work narrowing this down. Would you like to try the build below to see if this resolves the problem? [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_3.26.0.3.msi]NCrunch_Console_3.26.0.3.msi[/url] [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_3.26.…

  8. Console Tool Not Building .Net Standard Library

    Thanks for the feedback. I think there's a chance that the Win32Exception is downstream from the other one. Let me know if you can get a log of it happening without the other exception involved.

  9. NCrunch Test Window shows tests still running

    Thanks for submitting the report. At least one of the MSTest tests in this solution contains some strange parameter data in an array. This is probably using a custom DataRow. Are you able to narrow down which test is responsible? If you can get me the declaration of the test (with its attribut…

  10. NCrunch Test Window shows tests still running

    Hi, thanks for sharing this issue. Is this happening for you consistently? Would you be able to submit a bug report after it's happened in your session?

  11. Console Tool Not Building .Net Standard Library

    Thanks for sending through the log. I've identified the source of this problem. The NCrunch console tool is not correctly considering the installation state of the supported VS versions, so it's just using the highest version of VS that we've implemented, regardless of whether it is actually ins…

  12. Unstable Test Generation - NUnit TestCaseSource - Any alternatives

    The error you are encountering actually originates from NCrunch rather than NUnit. It's being caused by your generation returning a different set of results even though your test project has seen no changes. Previously, this would cause your test results to become skewed and unpredictable due to…

  13. Console Tool Not Building .Net Standard Library

    Looking at the log, the tool wasn't able to reach the point in its processing where the failure was able to occur. Could you perhaps try with '-LogVerbosity Medium' instead?

  14. Does not work with Fody

    Hi Mike, Thanks for the extra details. To help with this further, I really need a sample that I can use to produce the problem in my own environment. Let me know if you manage to isolate it.

  15. Support for VS 2019?

    We've just released [url=https://www.ncrunch.net/download]v3.25[/url] including a number of VS2019 fixes. The DPI scaling issues are quite widespread are we're working to resolve them. It will be a little while before we're able to publish a build with these issues resolved.

  16. Codesmith Task Failure

    v3.25 [url=https://www.ncrunch.net/download]has just been released[/url] including a fix for this issue.

  17. Console Tool Not Building .Net Standard Library

    Would you be able to obtain for me a detailed log of the console tool's execution run up to the point where it fails? You can do this by running the tool with the '-LogVerbosity Detailed' parameter and piping the result to a file. You can ZIP the file up and [url=https://www.ncrunch.net/support/…

  18. Does not work with Fody

    Hi Mike, Are you able to build a sample solution that can reproduce this problem?

  19. Does not work with Fody

    Hi, thanks for posting. To clarify, is your build giving the same error as at the top of this thread? If so, can you check that the Fody files correctly arranged in the NCrunch workspace? To view the workspace, right click the failed build in the Tests Window and go to Advanced->Browse to wor…

  20. Console Tool Not Building .Net Standard Library

    [quote=Christian Moritz;13278] Why couldn't it be easy to analyse a problem like that just once? [/quote] We've had .NET Core and .NET Standard support in NCrunch for about two years now. This means that if there's a problem that's simple to analyse and/or is impacting many people, we're certa…