Forum member

MatthewSteeples

147 posts

Posts by MatthewSteeples

  1. ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019

    File is [url=https://ledgerscope-my.sharepoint.com/:u:/p/matthew/EWpHtsS93adOun0aQFHavhoBEpE8NkWKnETA8IPn925nFA?e=Fm6iFe]here[/url] For reference, my VS is installed in the standard place (C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE) and I'm on 16.0.2 This is now…

  2. ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019

    I don't know if it helps at all, but it appears to be trying to use the following folder to "install" into: C:\Program Files (x86)\FirstInstall\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2019\ Looking in ProcessMonitor it looks to have found devenv at some point but it's t…

  3. ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019

    Possibly in a similar vein to this, we're having issues deploying the MSI out through InTune (Microsoft's management portal). The devs appear to be able to run the MSI locally, but installing (for the user) through the management utility fails with the following message in the event log: [code=pl…

  4. Support for VS 2019?

    [quote=Remco;13293]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.[/…

  5. Support for VS 2019?

    [quote=michaelkroes;13239]Hi Matthew, I had some issues replicating the High DPI issue. Would you mind enabling the setting/option again and submitting a bug report from the NCrunch menu? This might help me debug the issue. Thanks![/quote] Just submitted 2 bug reports. One with the DPI cha…

  6. Support for VS 2019?

    Just discovered it was [url=https://forum.ncrunch.net/yaf_postst2678_Visual-Studio-2019-optimized-DPI-rendering.aspx]this issue[/url]. I occasionally remote desktop into this device from a different one which has a different DPI. Disabling the option mentioned in that thread makes my windows render …

  7. Support for VS 2019?

    [quote=michaelkroes;13232]Would you mind submitting a bug report from the NCrunch menu? Maybe that will give us some insight [/quote] Done. Good luck! :)

  8. Support for VS 2019?

    [quote=MatthewSteeples;13211]We're seeing an issue too, using the Dark Theme: https://1drv.ms/f/s!At3esDCvFltcgaCPFmdOX8N9DFcFWFE EDIT: Same results on 3.25.0.1[/quote] I'm still seeing this problem but still only on one device. I've uninstalled NCrunch, VS2019 preview and VS2017, and have re-…

  9. Support for VS 2019?

    We're seeing an issue too, using the Dark Theme: https://1drv.ms/f/s!At3esDCvFltcgaCPFmdOX8N9DFcFWFE EDIT: Same results on 3.25.0.1

  10. Exclude tests based on wildcard

    That's exactly what I'm after. Better than my workaround of using a RequiresCapability for a capability that nothing provided. Thanks

  11. Exclude tests based on wildcard

    We've got a complex suite of integration tests that run in NCrunch on grid nodes that are based off 1 base class. The details (if relevant) are that we have 5 methods on the base class, and then each of our test files is a class that inherits from this class, which equates to (for example) 500 tests…

  12. Support for VS 2019?

    [quote=MatthewSteeples;13093][quote=Remco;13092]I'm aware that they've announced a launch date on April 2nd. I wasn't aware that P3 was expected to be the last version before the release ... is there any chance you can share your source on this?[/quote] Sure, it's nothing secretive or protected,…

  13. Support for VS 2019?

    [quote=Remco;13092]I'm aware that they've announced a launch date on April 2nd. I wasn't aware that P3 was expected to be the last version before the release ... is there any chance you can share your source on this?[/quote] Sure, it's nothing secretive or protected, but I've been seeing the wor…

  14. Support for VS 2019?

    I'm sure you'll be hearing this too, but I'm hearing rumours that Preview 3 will be the last big release before the final version coming in April. Could potentially be the case as there's 6 weeks to go and they've been releasing previews every 4-8 weeks so far My team are being very patient becau…

  15. Support for VS 2019?

    I'm only posting this here to save anyone else attempting the same. I attempted to manually install NCrunch into VS2019 (following the instructions). It installs without errors but doesn't really function. It also complains about the extension synchronously loading, so there's definitely going to be…

  16. System.Runtime 4.1.2.0

    It might be worth noting that VS 15.9 and onwards fixes a problem with binding redirects and System.Runtime, so it may be worth upgrading to that (if possible) and removing the binding redirect from your config altogether

  17. Grid Node - AccessViolationException - Protected Memory Issue

    Actually, now you mention it there's one more difference. This server is running [url=https://github.com/StackExchange/StackExchange.Precompilation]StackExchange.Precompilation[/url] to precompile our views. The summary of that project is that it turns the cshtml files into cs files at compile time …

  18. Grid Node - AccessViolationException - Protected Memory Issue

    [quote]System.TypeInitializationException: The type initializer for 'MVC' threw an exception. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at nCrunch.TestRuntime.SharedMemoryExecutionDataRecorder.Mark…

  19. Docker Image

    Just in case anyone else is considering running an NCrunch Grid Node _within_ a container, the sample that we're using is currently [url=https://hub.docker.com/r/matthewsteeples/ncrunch/]publicly available[/url]. This is not a supported or officially sanctioned deployment method, and the image it…

  20. Could not load file or assembly 'System.Runtime, Version=4.1.1.0...'

    Solved it! That was our only VS Test Project that didn't have a reference to the NuGet package System.Runtime. I think our migration to VSTest v2 might have caused this issue, and NuGet/Microsoft have started doing weird stuff where you need to have references to stuff that is already built into …