Forum member

Tim Long

31 posts

Posts by Tim Long

  1. NCrunch gets stuck on outdated code

    FYI, I already submitted a bug from VS a few minutes before I opened this thread. I'm not (currently) using any distributed processing. I don't believe anything I'm building is GAC registered (it's an ASP.Net MVC web application in this instance but I've had the problem in other non-web projects …

  2. NCrunch gets stuck on outdated code

    Yes I am using "Impacted Tests Only" mode and that is really the killer feature of NCrunch for me. If that isn't going to work then I may as well go back to using ReSharper. The "impacted tests" theory may go some way towards explaining the issue, but why would the test still fail (because it is …

  3. NCrunch gets stuck on outdated code

    I'm running NCrunch 3.7.0.7 in VS2017 and using MSpec tests. I've had lots of problems with NCrunch getting stuck on outdated code. I have the problem right now, where I can run my tests in the R# MSpec runner and everything passes, but NCrunch is still failing a test that I fixed a while back. Even…

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

    It was working reasonably well as recent as 2 minor releases ago. I've just come back to doing development after a few weeks away and have updated all my software, hence noticing the new 'odd' behaviour. I guess in the grand scheme of things, the Risk/Progress bar isn't the most important feature…

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

    Is it just me or is the Risk/Progress bar behaving oddly in version 3.2.0.3? I've noticed the following symptoms: [list] [*] When initially loaded, the progress bar shows OK/green even though the Tests window is showing failed tests. [*] When crunching, the risk % displays but the progress bar st…

  6. Grid Node can't build .NET 4.6.2 projects

    I'm working on a project that targets .NET 4.6.2; I have just installed .NET 4.6.2 Developer Pack on the grid node and rebooted it. Now I get the following from the Grid Node Server: NCrunch encountered an error while trying to construct an environment to execute this test: System.Exception: The …

  7. "Directory Not Found" when testing an assembly that relies on content files

    Wait! Solved it... The class library was referencing the content as ".\subdirectory\filename" which was a bad assumption. I've replaced that with a location based on Assembly.GetExecutingAssembly().Location and that seems to be working now. False alarm, sorry. --Tim

  8. "Directory Not Found" when testing an assembly that relies on content files

    I'm having a problem running tests against a class library that relies on content files that are expected to be in the same location as the class library assembly. I have the content files (plain text) configured as "Content" and "Copy Always" to the output directory. The files get copied to a su…

  9. Any plans to support .NET Core / ASP.Net 5 / UWP?

    I see, thanks for the insight. I'm not sure what constitutes "massive demand" but for perspective, this is the 7th most popular feature on UserVoice with 76 votes. Admittedly, the situation with the tooling and the impenetrable maze of project systems, frameworks, platforms and dependencies is…

  10. Any plans to support .NET Core / ASP.Net 5 / UWP?

    Thanks for the response. I'm encouraged to see that support for .NET Core is "#1 Priority" once the toolchain is released. The way Microsoft has released this new platform has been a bit messy, to say the least... with their "It's an RC, oh wait we are completely rewriting everything but its stil…

  11. Any plans to support .NET Core / ASP.Net 5 / UWP?

    I would like to know if there are any plans to support .NET Core projects, ASP.Net 5 / MVC 6 and the Universal Windows Platform. This is a huge area of the .NET landscape where there is a lot of new opportunity but which is is currently lacking in support from many of the tools vendors. It's earl…