Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. VS2017, NCrunch 3.2.0.3 build error

    Hi, thanks for sharing this issue. When NCrunch creates a process to execute MSBuild, it does so using a temporary file called 'MSBuildConfigVS2017.config'. This file can be found at C:\Users\[USER]\AppData\Local\NCrunch. It contains a number of binding redirections that force the build system …

  2. "No Coverage" comments not working

    Thanks for sharing the code sample. What you've described is definitely defective behaviour. You've used the coverage suppression comments correctly and there is no structure to this code that would cause ambiguity around whether the shared method is covered. Your clearing of the coverage index…

  3. Risk/Progress bar seems a bit flaky in the latest version

    Thanks Tim. I'll see if I can get it fixed :)

  4. Risk/Progress bar seems a bit flaky in the latest version

    Hi Tim, Thanks for sharing these problems. The Risk/Progress bar has had some issues for a while now and it badly needs a serious rethink. When it was originally designed, the engine was much simpler .. but now we have much more sophisticated states, especially when distributed processing is in…

  5. "No Coverage" comments not working

    Hi, thanks for posting! There's a few issues you've covered here. I'll try to address them each individually. Missing coverage: When NCrunch tracks test coverage, it does so from the moment the test itself starts executing and it will only track the lines of code that are physically execut…

  6. V3.2 and VS2010 Intaller Error

    Hi Ed, Thanks for posting! NCrunch doesn't perform any license checking in the installer. The intention is to make the installers as simple as they can possibly be, as under Windows Installer it seems that even the most basic of steps still finds ways to fail on some systems. A manual inst…

  7. Workaround working with net.core projects?

    Hi, At present, I know of no workaround. To handle .NET Core, NCrunch needs to integrate with the new VS project system. It then needs rewired handling of the load process, integration with the new build logic, cross-compilation of all runtime components to target .NET Core, and a new task …

  8. Loading / running FsCheck tests

    It may be worth attaching a debugger to the test host process, then seeing which modules are loaded into the process. If you have two modules that are different versions of the same assembly, this can cause all kinds of resolution issues. v3.2 is available for download including the binding redi…

  9. RunAll does not work

    Hi, thanks for sharing this issue. Would you be able to submit a bug report after you've had this happen to you? It's possible there's been an internal problem somewhere, and the log in the report may reveal this. A couple more questions to help narrow this down: - Does this happen for you…

  10. Telerik OpenAccess NCrunch Build Error

    [quote=austin;9513] In any case this was just an initial test drive to try and understand how NCrunch works. My immediate goal would be to get a test rig set up that incorporates SpecFlow, Selenium, NCrunch and xUnit for testing against a Sitefinity codebase. Many of these tests are more integratio…

  11. Since V3 does not copy dependant dlls to grid node

    Hi Daniel, Thanks for posting! V3 hasn't introduced any changes to the behaviour of transferring files over to the grid node. If files are being referenced from the GAC on the client, or in 'Program Files', they are considered to be part of an installed SDK on the client and they will not b…

  12. VS15 Installer

    Hi, thanks for the bug report. This is a known issue in v3.1. A fix will be out with v3.2 later this week. You can avoid the problem by using no more than one instance of VS2017 at any one time.

  13. Telerik OpenAccess NCrunch Build Error

    Hi, thanks for sharing this issue. I've had a go at trying to reproduce this problem, but unfortunately I've been having trouble getting the above sample project to build on my machine (without NCrunch involved). Looking at the code here, it seems that there is some very involved build logic h…

  14. Frequent focus loss

    Hi, thanks for sharing this issue. V3 didn't introduce any changes that I would immediately suspect of this. Though there is some history here. The following features of NCrunch use a popup dialog that in older versions has sometimes stolen focus from the main VS window: - Notification of ne…

  15. VS2017, ncrunch 3.1 error

    Thanks for sending through these files. With them, I've managed to reproduce this problem. A fix is pending in the v3.2 release due later this week. For reasons I can't really explain (but probably have much to do with the faulty wiring in my head), when NCrunch ported settings over from the ol…

  16. NCrunch and %TEMP%.

    Hi, This is interesting. NCrunch itself makes minimal (perhaps no?) use of the temp directory directly. I expect that you're probably seeing temporary files being created by either build tasks (i.e. compiler), the code under test, or the CLR itself. You may need to take a closer look at the …

  17. TeamCity integration improved in v3? (vs v2)

    Hi, I'll need to take a closer look at this, but at a glance it feels like the documentation may be unclear/wrong in this particular case. V3 hasn't changed any of the integration in this area. I expect teamcity will have moved a bit since this documentation was written, so it may be a little…

  18. VS2017, ncrunch 3.1 error

    [quote=philliphaydon;9495] So it may just be a conflict between the two. Do you want me to email you the two global files so you can check them to see if there's a patch that's require incase others fall into the same issue?[/quote] Absolutely. If you still have the files, I'd very much like to…

  19. VS2017, ncrunch 3.1 error

    Hi Phillip, This looks to be an unrelated problem. NCrunch tried to load a setting from its global configuration file that it didn't recognise, and dropped the value. This is a non-critical error. It's strange that it hasn't reported the name of the setting. Have you seen this error more th…

  20. VS2017, ncrunch 3.1 error

    Hi, thanks for sharing this issue. There is a fix for this problem coming in v3.2 out later this week. It should be possible to alleviate the problem by avoiding use of more than one instance of VS2017 at any one time.