Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. InvalidProjectFileException when running

    My suspicion is that there may be file that you manually need to include using the AdditionalFilesToInclude setting. Check that your global build settings files are being picked up in the NCrunch workspace - you can view the workspace by right clicking on the project in the tests window and choosin…

  2. InvalidProgramException on certain tests in solution

    It looks like this was being caused by a certain IL arrangement that the instrumentation didn't handle too well. You can probably work around it by splitting this code up into smaller methods or by turning off the instrumentation. A fix for this issue will be in the 1.36b release, due out before C…

  3. TreeView / DataGrid Hybrid control

    For the functionality it gives, it's definitely a good component... and it's used everywhere through NCrunch, so it made sense to buy it :)

  4. TreeView / DataGrid Hybrid control

    It's a DevExpress TreeViewList control. I wish I could say it was free, but I did have to pay for it. I also looked far and wide for a free control that was powerful enough and fast enough, but was sadly disappointed.

  5. In switch statements that are one line of code and a "break" statement, only "break" shows coverage

    Yes - there is a defect in here around the code coverage marking on switch statements. Not all of the coverage markers on these statements are 100% accurate. This issue also seems to affect reported coverage around some inline delegates. Thanks for reporting the issue. It will be fixed.

  6. ncrunch doesn't support nunit testcase

    Hi Jason, Thanks for posting. These test cases are failing because of an instrumentation defect that causes NCrunch to bug out while processing a file with named attributes. Therefore you'll find that removing the 'Result =' on the TestCase attribute will allow the tests to execute in NCrunch (…

  7. NCrunch build fails when project contains an app.manifest

    Nice one! Thanks for letting me know about these. I'll add them to the autoconfiguration list.

  8. InvalidProgramException on certain tests in solution

    Excellent! Thank you ... it's not always easy to reproduce these problems. I'll take a look at this and will see if I can get a fix introduced.

  9. Issues With Signed Assemblies

    Good find. Sometimes when files get copied the build output can throw some fairly obscure errors. It's often worth right clicking on the failed build in the tests view and browsing through the workspace to ensure it contains all the files needed for your build.

  10. Where does it host?

    Hi Dmitry, Thanks for posting! NCrunch is a closed source project, but if you post the details of your problem perhaps I can help you solve it? Cheers, Remco

  11. Indication that test results are out of date

    Hmmm this is very true. I guess I could make the text a slightly lighter shade for when the test has a question mark. I'll note that one down :)

  12. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I have to recommend taking a look at the difference between the SL .csproj and non-SL .csproj files. You may find you're able to make a single project file work cross-target by using some MSBuild wizardry. This could allow you have the same list of files in the project without needing to duplicate…

  13. NCrunch fails to build

    I wonder if this could be related to the configuration file you're using on the MVC project. I've tried the default MVC3 templates at my end and they didn't cause this problem, but I have had a user before mention a similar sounding problem that they solved by deleting their config files... I sh…

  14. Clickable stack dumps in test results

    Yep!! This one is on the list :)

  15. NCrunch fails to build

    Thanks. If you remove the Local\assembly directory, do you still receive the problem if you immediately try NCrunch with a non-MVC solution (i.e. just a simple class library on its own) with any other test framework?

  16. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Gotcha. I was thinking the same thing, but piggybacking off the same project file. I think the key question here would be the target framework used for building the tests that cover the cross-target project. Right now NCrunch can't build SL application domains, so the tests themselves would nee…

  17. Cannot build with unloaded (dependent) projects

    Hi, thanks for posting! Right now NCrunch doesn't have any handling for unloaded projects. The reason for this is because it cannot read any metadata from the project unless Visual Studio has it loaded, and therefore would be unable to safely determine the location of the project's primary outpu…

  18. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    In theory this is possible. You could make use of the 'UseBuildConfiguration' setting in NCrunch to tell it to use a different build configuration, then rig up your project file to build for non-SL .NET 4.0 under this build configuration. I guess it would create quite a bit of work for you though,…

  19. NCrunch fails to build

    Thanks for sending through the report. It looks as though Visual Studio is loading the NCrunch Taskrunner.dll file from a shadow copied location. This is really wrong. Try removing the contents of the User\AppData\Local\assembly directory - hopefully this will kick it to start using the proper …

  20. Indicators have vanished

    Ok - essentially the issue is being caused by a VS service that is failing to properly add the adornment layer that NCrunch uses for placing the coverage markers onscreen. I've tried somewhat to reproduce this issue in my development environment but have had no luck with this. The issue itself has…