Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Cecil failure during test project build

    Hi, thanks for sharing this issue. This particular exception is being thrown because of a method variable that has an unexpected (invalid?) signature in the assembly's IL. It's possible that this is due to a method in your assembly having an unusual structure, or otherwise it could be a downstre…

    23 Sep 2016 23:58 UTC

  2. Haven't been able to upgrade since 2.23.2

    Hi Mike, I'm sorry to hear that there have been ongoing problems for you. Can you share any more details about why these tests are failing? Is there a file copy or workspace synchronisation issue of some kind?

    22 Sep 2016 23:22 UTC

  3. App.config not found

    Hi, This solution contains custom build steps to copy the app.config file from the references directory into the build output directory. You can solve this problem by adding "Reference\Vs2015\App.Config" to your solution-level 'Additional files to include' setting. The subsequent VsVim proj…

    21 Sep 2016 12:16 UTC

  4. NCrunch doesn't use the 4.6.2 engine host

    Great! Thanks for confirming!

    20 Sep 2016 10:54 UTC

  5. NCrunch doesn't use the 4.6.2 engine host

    Hi, thanks for sharing this issue. This problem seems to stem from a defect that is preventing NCrunch from correctly detecting .NET 4.6.2 on systems with Windows 10 Anniversary installed. Windows 10 becomes special when it has the anniversary update installed; it gets different version numbers …

    20 Sep 2016 08:32 UTC

  6. Malware Detected ???

    Here you go - [url=http://downloads.ncrunch.net/NCrunch_VS2015_2.26.0.1.msi.7z]http://downloads.ncrunch.net/NCrunch_VS2015_2.26.0.1.msi.7z[/url]

    19 Sep 2016 11:51 UTC

  7. Unable to include other project XML documentation

    Hi, thanks for posting! This is technically a resource co-location assumption - see [url=http://www.ncrunch.net/documentation/considerations-and-constraints_assembly-colocation-assumptions]http://www.ncrunch.net/documentation/considerations-and-constraints_assembly-colocation-assumptions[/url]. …

    19 Sep 2016 11:43 UTC

  8. Seperate parameterized tests

    Hi, thanks for sharing this issue. Although it might look wrong from a glance, this is actually by design and it is caused by a technical limitation. Your test has user-type parameters, which cannot uniquely identify themselves in the parameter line. For example, the DeviceRendition class may…

    18 Sep 2016 00:05 UTC

  9. Rerun flaky test

    Hi, Thanks for posting! This makes sense as a feature request. You're welcome to formally request it on [dead link].

    17 Sep 2016 10:51 UTC

  10. Malware Detected ???

    I'll see what I can do. Can you confirm which version of VS you are using?

    16 Sep 2016 23:52 UTC

  11. Bug with combination of catch-when and params arguments

    Ok, that did the trick. I can reproduce this problem now. Thanks for letting me know about it. I'll see what I can do about getting it fixed. The following options can be used as workarounds: - Code coverage suppression comments around the 'when' - Turning off instrumentation - Turning on A…

    15 Sep 2016 22:29 UTC

  12. Using environment variables in additional files to include path

    [quote=andcoll;9161] we have files that we need to include in the root of our repository, we've got a $(SRCROOT) env variable that points to this. So instead of ..\..\..\..\..\..\includedfile.xyz we'd prefer $(SRCROOT)\includedfile.xyz. We've had issues where we've had to change a lot of ncrunc…

    15 Sep 2016 10:11 UTC

  13. Using environment variables in additional files to include path

    Hi, Thanks for posting! There was some effort made to implement this, but it proved to be much more complicated than expected due to certain edge cases (such as absolute paths, which aren't allowed in this setting). What do you need the environment variable for? Are you trying to work arou…

    15 Sep 2016 09:26 UTC

  14. Bug with combination of catch-when and params arguments

    Hi, Thanks for sharing this issue. I'm fairly certain this is being caused by an IL sequence that is being affected by NCrunch's instrumentation. You can work around the problem by placing code coverage suppression comments around the code block, for example: //THIS TEST FAILS [Test] publi…

    14 Sep 2016 20:54 UTC

  15. Build Project w/ Console Tool

    This looks to be exactly the same problem, but for a different assembly. The O/S is now preventing NCrunch from loading the assemblies of its modules. If you've extracted the tool from ZIP, make sure all binaries in the install path are unblocked by Windows.

    06 Sep 2016 23:25 UTC

  16. After removing a failing project from the solution, it does not disappear from NCrunch

    [quote=abelb;9151]Interestingly, it shows a small bug of NCrunch (which may or may not be present in the current release). If you have a reference like the one shown above, with the $(NCrunch) variable, it is odd that the same reference is [b]not[/b] shown in the NCrunch Configuration window. Appare…

    05 Sep 2016 12:29 UTC

  17. After removing a failing project from the solution, it does not disappear from NCrunch

    NCrunch discovers projects in two ways: 1. From the solution itself (i.e. sln file or reported from VS) 2. By traversing project references from other projects it has loaded When projects are discovered using '2', this will throw out NCrunch's expected project count in the initialisation coun…

    05 Sep 2016 11:57 UTC

  18. Re-running failed tests via NCrunch grid and TeamCity

    Hi Sheryl, If both runs are being executed on the same CI server at the same time, then the contents of the cache file will be decided by whichever run finishes latest. This is because the console tool will always read from the cache from when it starts up, then write to it when it shuts down …

    02 Sep 2016 22:49 UTC

  19. Build Project w/ Console Tool

    Hi, thanks for sharing this issue. This looks to be either an installation issue or .NET configuration issue with the machine you're running the console tool on. Check the following: [dead link] Everything else you've described is the correct setup approach for the console tool. It should…

    02 Sep 2016 22:40 UTC

  20. Print to Debug Windows in TestCaseSource Factory

    Hi Ed, The TestCaseSource factory methods are invoked by NUnit during test discovery, which happens inside the 'Analyse Assembly' tasks in the processing queue. NCrunch runs this after every successful build. The user code inside the factory methods is considered to be a part of the test discov…

    01 Sep 2016 23:23 UTC