Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. VS2017, NCrunch 3.2.0.3 build error

    Thanks! This helps a great deal. I think I have some idea of what may be going on here, but it isn't clear to me why this is showing up in your case but not in others. Is there a specific VS project template that can surface this issue for you?

    14 Dec 2016 23:30 UTC

  2. Unable to parse the configuration setting Text output font (after upgrade to v3)

    Hi, Thanks for sharing this problem. This actually looks to be a localization issue. Your locale has a comma in the font point size, and NCrunch isn't handling this well. I'll see what I can do about rolling a fix into the next version. I'm glad you like the new config system!

    14 Dec 2016 23:17 UTC

  3. "No Coverage" comments not working

    Wow, I just got it to happen for me. This is pretty crazy. I'll need to take a deeper look at what's happening here, but I think this is being caused by some fallback code used to mark the first lines of test methods to identify test entry points. In which case, it should just be a visual anoma…

    14 Dec 2016 23:12 UTC

  4. VS2017, NCrunch 3.2.0.3 build error

    Thanks for sharing these details. Are there certain projects that seem to trigger this for you? The binding redirections all look to be in order, so if the files exist in the referenced location, it isn't clear to me why the CLR would have trouble finding them. Something worth trying is to …

    14 Dec 2016 10:16 UTC

  5. "No Coverage" comments not working

    Sorry about the screenshot upload. I think we should be OK without it. I mostly just wanted to confirm that these were in fact NCrunch markers. The tooltip you've given me has confirmed that. I've never seen a problem like this before. Something very interesting is happening with this method.…

    14 Dec 2016 00:13 UTC

  6. 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 …

    13 Dec 2016 22:59 UTC

  7. "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…

    13 Dec 2016 22:49 UTC

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

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

    13 Dec 2016 22:29 UTC

  9. 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…

    13 Dec 2016 03:57 UTC

  10. "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…

    13 Dec 2016 02:53 UTC

  11. 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…

    12 Dec 2016 22:01 UTC

  12. 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 …

    12 Dec 2016 11:23 UTC

  13. 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…

    11 Dec 2016 03:12 UTC

  14. 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…

    09 Dec 2016 22:46 UTC

  15. 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…

    09 Dec 2016 22:43 UTC

  16. 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…

    09 Dec 2016 22:31 UTC

  17. 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.

    09 Dec 2016 00:05 UTC

  18. 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…

    08 Dec 2016 23:01 UTC

  19. 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…

    08 Dec 2016 22:42 UTC

  20. 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…

    08 Dec 2016 05:03 UTC