Forum member

distilled

22 posts

Posts by distilled

  1. Unable to pin or unpin tests in bulk

    I ended up reformatting my workstation a few days after posting this and everything works as expected now. If it happens again (or if I run into any other issues) I'll submit a bug report. Thanks for the quick follow-up and sorry for not being as quick with mine!

  2. Unable to pin or unpin tests in bulk

    I have the option to automatically pin newly discovered tests enabled. With the latest NCrunch build (4.18.0.3) and VS 17.8.0 Preview 1 I'm unable to use the bulk unpin button to remove pins. Removing them individually seems hit-or-miss (to the point that it's easier to just ignore the pins than it …

  3. v4.12.0.4 not available in VS 2022 Preview instance

    Never mind, user error. [img]https://c.tenor.com/OtjbBfwQHeIAAAAC/fizzer1k-5597.gif[/img]

  4. v4.12.0.4 not available in VS 2022 Preview instance

    I downloaded the MSI for new release this afternoon (v4.12.0.4). After running it NCrunch is installed to my Enterprise copy of VS2022 but not the preview instance (v17.3.0 Preview 1). I didn't receive a prompt asking which installations NCrunch should be added to, which (I think?) I've been present…

  5. Unused engine hosts?

    Not really an issue, just a question. I noticed that in NCrunch's extension directory there are several flavors of nCrunch.EngineHost. One flavor for each full .NET framework version and architecture combination. How does NCrunch determine which of these to use? I've only ever seen nCrunch.Engine…

  6. NCrunch is fantastic, thank you

    Here here! NCrunch is the one extension I absolutely must have installed in order to be productive. Thanks for the awesome product, I can't wait to see what's next for it!

  7. Automatically run impacted tests without automatically running all tests

    I'll give customizing the engine a shot. Thanks!

  8. Automatically run impacted tests without automatically running all tests

    [quote]So I guess what I'm saying is that if things are working properly, then this is the sort of behaviour you should already be seeing.[/quote] Yep, I can confirm that that's what I'm seeing. I guess in my experience the file hash very rarely matches what NCrunch has cached, and most of the ti…

  9. Ignore test projects based on target frameworks

    That sounds reasonable, I'll take that approach. Thanks!

  10. Ignore test projects based on target frameworks

    I use NCrunch in solutions with .NET Standard projects. When I create test projects for them, I multi-target the runtimes that I expect my .NET Standard libraries to run on (so if Foo.csproj targets NETStandard2.0, FooTests.csproj probably targets net46, netcoreapp3.1, etc.). NCrunch treats each tar…

  11. Automatically run impacted tests without automatically running all tests

    I use NCrunch in a solution with a large number of tests (~20k). I prefer to leave NCrunch in the "Automatically run impacted tests" mode. However, when I select this mode NCrunch automatically runs all unignored tests right away, before only running tests that are impacted by my changes. Is there a…

  12. Allow Code Analysis option does not apply to Roslyn analyzers

    Not sure if this is the right place for this feedback, or if a feature request would be more appropriate. Roslyn analyzers provided by NuGet packages can significantly increase the time it takes to build a project. NCrunch has a configuration setting to disable code analysis on build. However, th…

  13. SecurityException thrown when NCrunch tries to runs a ASP.NET Core 2.0 integration test

    Thanks! However, I still receive the message "NCrunch was unable to retrieve a meaningful result from this test due to an unexpected error - was the execution process terminated?" when NCrunch tries to automatically run the test. The test still passes when run manually, and I was able to debug it th…

  14. SecurityException thrown when NCrunch tries to runs a ASP.NET Core 2.0 integration test

    I have an Xunit test that uses the classes from the [url=https://www.nuget.org/packages/Microsoft.AspNetCore.TestHost/]Microsoft.AspNetCore.TestHost[/url] package to integration test an ASP.NET Core 2.0 project. The project uses a custom implementation of [url=https://docs.microsoft.com/en-us/dotnet…

  15. Support projects that use the PathMap compiler switch to opt-in to deterministic builds

    The updated build worked, thanks! And sorry for the delay!

  16. Support projects that use the PathMap compiler switch to opt-in to deterministic builds

    The PathMap compiler switch can be specified in a project file (or a Directory.Build.props) file to normalize directory names in the compiler-produced outputs (specifically PDBs and assemblies that utilize the CallerFileNameAttribute). See https://github.com/dotnet/roslyn/issues/949 for details. …

  17. InvalidCastException when building assembly containing xunit 2.2 tests for a ASP.NET Core 2.0

    I have a .NET Core 2.0 project (target .NET Framework 4.7) that contains xunit v2.2 tests for an ASP.NET Core 2.0 project in the same solution. When NCrunch tries to build the project an InvalidCastException gets thrown: [code] An error occurred while analysing this project after it was built: S…

  18. Build errors when referencing Shared Projects

    I'm currently working on a solution that contains a Shared Project (*.shproj). The shared project is referenced by two class library projects. NCrunch (v3.6.0.2) raises the following error if I don't tell it to ignore the shared project: [code=plain] NCrunch: If you are experiencing problems in …

  19. NCrunch fails to build solutions using Automatic Package Restore

    NuGet 2.7 included a new Automatic Package Restore feature to [url=http://nuget.codeplex.com/workitem/4019]replace[/url] the package restore process that depends on MSBuild integration. A comparison of how the two approaches differ is summarized [url=https://docs.nuget.org/docs/reference/package-res…

  20. Unit testing with classes from Roslyn.Services namespace results in a SecurityException

    Changing the .config file didn't fix the problem, unfortunately.