Forum member

richardmoss

12 posts

Posts by richardmoss

  1. Issue building project using tools NuGet package

    Hello, I forgot to get back you, but this works - thanks. Regards; Richard Moss

  2. Issue building project using tools NuGet package

    Hello, I am currently using the [url=https://github.com/brutaldev/StrongNameSigner/]StrongNameSigner[/url] tool, a NuGet package which doesn't add any references, but injects a tool into the build process which automatically applies a strong name signature to any assemblies without one, given tha…

  3. Framework 4.6.2 project failing to build using optimised instrumentation mode

    Hello, Try installing the preview 4.2 builds from [url=https://forum.ncrunch.net/yaf_postsm14051_NCrunch-4---Instrumentation-Mode---Optimized---Project-fails-to-build.aspx#post14051]this post[/url], that fixed it for my full-fat Framework solutions that exhibited the same error. Regards; Rich…

  4. NCrunch 4 - Instrumentation Mode - Optimized - Project fails to build

    Hello, Can also confirm that the 4.2 build linked above seems to have resolved the "1 project failed to build" issue I was having with multiple classic .NET Framework solutions. Thanks!

  5. SpecFlow Tests

    Hello, Thanks for the response. I did have the correct packages installed based on the specflow docs that I'd followed (first time using this framework, normally a nunit guy!), but on a whim I commented out the specrun.specflow packagereference and replaced it with specflow.mstest instead and imm…

  6. SpecFlow Tests

    Hello, I'm busy working my way through a book which presents a bunch of test cases in Gherkin, so I've been using SpecFlow to implement them and then using Visual Studio's test runner to run them. Except VS's test runner still sucks and I wondered if NCrunch supported SpecFlow. Apparently it does…

  7. Incorrect Coverage Metrics for single-line if-statements

    [quote=Remco;8774]Hi Richard, I'm sorry, but there has been no change in the way this is handled by NCrunch. If I can find a feasible way to implement more detailed resolution of coverage in the tool in future, it will be implemented.[/quote] Ah well, no worries. Thanks anyway! Regards; R…

  8. Incorrect Coverage Metrics for single-line if-statements

    Apologies for resurrecting such an old thread, but I have encountered the same issue with regards to multiple branches on the same line not being picked up by NCrunch (mostly null coalescing or the null conditional in newer code or the odd if bool || bool), followed by MSTest hell over the missing b…

  9. v2 filename format

    Thought that might be the case... oh well, I'm not planning on going back to v1 so I might as well get everything converted and blatted sooner rather than later! Thanks for the prompt response! Regards; Richard Moss

  10. v2 filename format

    Is the file name format of the v2 settings files permanent? I've temporarily excluded the new v2 files from version control in order to avoid having two sets of setting files in my SVN and GitHub repo's during beta. Ideally it would be nice if v2 used the same setting files as v1, and have v1 jus…

  11. UI suggestions

    Hello, Couple of suggestions based on working with a solution containing just over 2000 ignored tests and around 500 non-ignored where I'm selectively un-ignoring new tests and some legacy tests. I normally do not like having a single test ignored, but this 5 year old testing library is not suite…

  12. 1.41b: 'Additional files to include' not working?

    Hello, Just to add my own comments to this thread, I was having a similar issue, including not being able to resolve it by simply changing other NCrunch properties. However, in my case the problem was resolved by disabling all .NET Demon options then reloading the solution. Not sure if that was a…