Forum member

robmen

27 posts

Posts by robmen

  1. NCrunch Tool Window UI in VS2026 invalid on 4K monitor

    1. No. All of them are wrong when opening the solution 2. Opening an NCrunch tool window does display correctly. If I close a broken NCrunch tool window and open it again, it also displays correctly 3. Dragging NCrunch tool windows across monitors works correctly 4. It does get broken again when …

    26 Feb 2026 23:24 UTC

  2. NCrunch Tool Window UI in VS2026 invalid on 4K monitor

    NCrunch does render its controls properly with that setting disabled. VS is also noticeably blurrier and hard to look at. After reenabling the setting (and restarting VS again), NCrunch controls rendered properly for a moment, then snapped to their broken sizes.

    25 Feb 2026 23:28 UTC

  3. NCrunch Tool Window UI in VS2026 invalid on 4K monitor

    Display 3840x2160@60Hz at 125% IDE VS2026 18.2.2 Multiple screens: Yes, three total, the other two are both: 2560x1440@60Hz at 100%

    25 Feb 2026 23:10 UTC

  4. NCrunch Tool Window UI in VS2026 invalid on 4K monitor

    I recently upgraded to a 4K monitor. NCrunch does not render its controls properly in its tool windows. Attached are pictures that demonstrate the issue better than I can describe. If I slightly resize the tool window, NCrunch will adjust its controls. If I debug (which doesn't have the NCrunch tool…

    25 Feb 2026 19:42 UTC

  5. Additional NCrunch Build Properties

    Very sorry, I forgot to follow up and let you know that these properties worked out perfectly for my scenario and made everything work. It's great. I'll stay on this private build and look forward to when a new official release comes out with these new properties. Thank you!

    27 Nov 2018 21:23 UTC

  6. Additional NCrunch Build Properties

    Thanks for responding so quickly. [quote=Remco;12761] It's possible now to see a list of all the properties NCrunch injects into your build system by setting your 'Log Verbosity' setting to 'Detailed', then examining one of your build tasks in the processing queue. Around all the other trace da…

    15 Oct 2018 23:43 UTC

  7. Additional NCrunch Build Properties

    The [url=http://www.ncrunch.net/documentation/V3/troubleshooting_ncrunch-build-properties]"NCrunch Build Properties" page[/url] lists the "NCrunchOriginalSolutionDir" and "NCrunchOriginalProjectDir" properties. NCrunch v3.18 added "ProjectName" and "ProjectFileName" (thank you, very much). Should th…

    15 Oct 2018 22:40 UTC

  8. .NET Core 2.0 Support with re-located build folder

    Thank you so much for the persistence. My (second) evaluation key had expired but I appreciate the effort you've done so much I upgraded our keys. Great news is that v3.19 does address my "prototypical project". I'm going to slowly adapt my other "real" (thus more complex) .NET Core projects to work…

    28 Aug 2018 05:09 UTC

  9. .NET Core 2.0 Support with re-located build folder

    Yes, I'm very excited to try to get NCrunch working with our projects. I've updated my "prototypical example project" (https://github.com/robmen/PrototypicalProject) with what I *think* is the correct way to use the new properties. The behavior is different but, unfortunately, still not working. …

    10 Aug 2018 07:21 UTC

  10. .NET Core 2.0 Support with re-located build folder

    I just saw the release notes for v3.18 and this item piqued my interest: > Adjusted the NCrunch project load system so that the ProjectName, AssemblyName and ProjectFileName properties will be set to the > correct name of the project rather than the NCrunch temp file. This should help to enable…

    09 Aug 2018 05:49 UTC

  11. .NET Core 2.0 Support with re-located build folder

    Understood. We're used to struggling with VS and MSBuild designs (particularly at their integration points). Would it work if there was an $(NCrunchOriginalMSBuildProjectName) that we could conditionally use in our Directories.Build.props file to cause the files in NCrunch to use the same interme…

    04 Jun 2018 16:49 UTC

  12. .NET Core 2.0 Support with re-located build folder

    We root all of the builds in a single folder in the root of the project for many reasons. For one, it co-locates the various build outputs (not all are .csproj) into a single folder that matches our deployment shape (so debugging is possible). Another example, it makes it very easy to ensure a build…

    04 Jun 2018 10:17 UTC

  13. .NET Core 2.0 Support with re-located build folder

    Thanks. I updated to v3.17.0.2 and I got a new failure. System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> nCrunch.Common.UserException: Errors occurred while trying to lo…

    04 Jun 2018 09:34 UTC

  14. .NET Core 2.0 Support with re-located build folder

    This year a lot of our work has transitioned to .NET Core (2.0 and very soon 2.1) from .NET Framework v4.5. We're finding NCrunch v3.12 does not handle our .NET Core projects. Our license expired end of last year so I've been unable to test if NCrunch's support for .NET Core has improved after versi…

    04 Jun 2018 09:11 UTC

  15. NCrunch without "workspaces"

    Is there any option to disable the "workspaces behavior" of NCrunch (the copying/building/testing of source code in isolated folders)? I understand the workspaces probably help with build/test performance but I struggle when csproj's has any interesting customization. These projects that fail in NCr…

    16 Oct 2017 23:45 UTC

  16. Quick second build losing code coverage?

    Just to close this thread. With v2.23.2 this issue seems to be resolved for me. Thanks for working on the fix.

    01 Jun 2016 17:03 UTC

  17. Quick second build losing code coverage?

    Very interesting results. [quote=Remco;8115]4. Wait for the test to run, and fail - Is the failure reported in the NCrunch Tests Window?[/quote] Yes, tests always passed/failed as one would expect. [quote=Remco;8115]6. Wait for the test to run, and pass - Is the passing result reported in…

    05 Dec 2015 01:01 UTC

  18. Quick second build losing code coverage?

    [quote=Remco;8107]- Are any of the assemblies built from your solution stored in the GAC at any time?[/quote] No. [quote=Remco;8107]- When the problem appears, does it continue to happen consistently when you try to re-run any of the tests involved?[/quote] Consistently. Can't get out of th…

    04 Dec 2015 06:17 UTC

  19. Quick second build losing code coverage?

    Sorry for the delay getting back to you on this. I had to make progress on the solution and when adding more projects, the problem didn't happen as often. Finally, I just caught it. [quote=Remco;8062]Are you using any of xUnit's parallelization or async features?[/quote] No. [quote=Remco;…

    03 Dec 2015 20:27 UTC

  20. Quick second build losing code coverage?

    [quote=Remco;8051]Sorry - I need to bombard you with a few questions here to fully understand what's happening:[/quote] Not a problem, that's why I'm here. I'd like to get to the bottom of this strange behavior and get to a point where I trust NCrunch just works. [quote=Remco;8051]- Do the tes…

    24 Nov 2015 13:14 UTC