Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Can't run tests with VS 2017 / XBehave 2.2.0-beta0003-build685 / XUnit 2.2

    Thanks Ant. I think it's best I just solve this problem properly by introducing proper support for xunit v2.2. This task has been pushed out a bit because it's quite complex. The original xunit integration wasn't designed properly and needs to change to work simultaneously with different versio…

    29 May 2017 05:19 UTC

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

    Ok, so that confirms that the problem you're experiencing in your real world solution isn't the same as the one we just found in the test project. Is there any chance you can reproduce the real world problem in code you can share with me?

    29 May 2017 01:32 UTC

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

    Thanks! It looks like this solution has no project reference between the test project and the web project, so NCrunch just couldn't find the dependency to merge the deps files. Interestingly, running the test outside of NCrunch also produced a failure :) Adding the project reference fixed eve…

    29 May 2017 00:11 UTC

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

    Thanks! It looks like the deps file hasn't included the project declaration for the web project, which was the critical thing that allowed this to work. Does your web project have a .deps file? I might need to get from you the sample project you're working on. It looks to me like there might…

    27 May 2017 23:38 UTC

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

    Ok, on the sample solution you shared with me, could you try the following? 1. Open the solution, run NCrunch over it so you see the failure 2. Right click on the failed test in the Tests Window, go to Advanced->Browse to workspace 3. Find the bin directory that contains the files for the test …

    26 May 2017 22:49 UTC

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

    Does NCrunch give you any warnings about the Microsoft.AspNet.TestHost package in the Tests Window?

    26 May 2017 12:09 UTC

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

    A fix for this is [url=https://www.ncrunch.net/download]now available with NCrunch v3.8[/url].

    26 May 2017 06:43 UTC

  8. Can't run tests with VS 2017 / XBehave 2.2.0-beta0003-build685 / XUnit 2.2

    Thanks Ant. Here are the errors from the report: An exception thrown while processing the module 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2017\Modules\XUnit2\nCrunch.Module.XUnit2.crunchmodule': System.IO.Fi…

    25 May 2017 23:03 UTC

  9. TargetInvocationException

    Thanks for letting me know how you solved this! Can you confirm which config file you needed to replace?

    25 May 2017 22:14 UTC

  10. Can't run tests with VS 2017 / XBehave 2.2.0-beta0003-build685 / XUnit 2.2

    Hi, thanks for getting back to me on the forum. My hope is that this isn't a version specific integration issue. Would you be able to submit a bug report after you've had the test discovery fail? There may be something in the report that can help inform us.

    25 May 2017 09:00 UTC

  11. Detecting Impacted tests

    Hi, thanks for posting. If you choose the 'Run impacted tests only, others manually' engine mode from the NCrunch->Select Engine Mode menu option, NCrunch will do exactly this :) You can also customise the engine modes if you have more specific needs, including the above one.

    24 May 2017 23:10 UTC

  12. Multiple markers when renaming class with ReSharper

    @b33rdy: It would be really great to know if you see anything in Alastair's setup that is similar in yours. In this way, maybe I can rule out needing to test integration with some products.

    24 May 2017 06:30 UTC

  13. nunit TestCase not working with ExpectedResult

    Thanks for confirming. This is the same one I also tested with :( Is there any chance you can put together a sample solution that can reproduce this issue? You can submit it through the [url=https://www.ncrunch.net/support/contact]contact form[/url].

    23 May 2017 12:27 UTC

  14. nunit TestCase not working with ExpectedResult

    Hi Henrry, I can't seem to recreate this problem when using the latest version of NUnit. Which version of NUnit are you using?

    23 May 2017 11:28 UTC

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

    Ok, here is a build with the fix! This build introduces a change to the grid protocol, so if you're running any grid nodes, you'll need to update them. [url=http://downloads.ncrunch.net/NCrunch_Console_3.8.0.2.msi]http://downloads.ncrunch.net/NCrunch_Console_3.8.0.2.msi[/url] [url=http://down…

    22 May 2017 06:13 UTC

  16. Error occurred while analysing project

    [quote=jonsequitur;10441]When you mentioned that package resolution is pointing to [user]\.dotnet\NuGetFallbackFolder, I tried copying files so that [user]\.dotnet\NuGetFallbackFolder and [user]\.nuget\packages had identical contents. It didn't resolve the issue. [/quote] Can you try also removin…

    22 May 2017 03:10 UTC

  17. Multiple markers when renaming class with ReSharper

    I'm still having trouble reproducing this issue. I'm wondering if it might be caused by a race condition or sequence related issue somewhere, or perhaps surfaced by some specific configuration. @b33rdy, you mentioned that you get this with a standard VS rename refactor, can you confirm whether y…

    22 May 2017 02:55 UTC

  18. Error occurred while analysing project

    NCrunch always considers the root of Nuget packages to be at [User]\.nuget\packages. In truth, I did not know it was possible to redirect this elsewhere. The log attached to the report you submitted indicates that MSBuild is resolving references to the [user]\.dotnet\NuGetFallbackFolder instead of…

    22 May 2017 02:50 UTC

  19. Error occurred while analysing project

    Thanks. Something seems different about your setup. I can see files resolving to [user]\.dotnet\NuGetFallbackFolder. Have you redirected your nuget packages directory somewhere else? If so, how has this been done?

    21 May 2017 23:30 UTC

  20. Error occurred while analysing project

    Would you be able to submit a bug report after you've had this blow up? The log may yield information on which dependency is missing.

    21 May 2017 23:17 UTC