Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Intermittent build error with ANTLR 3

    Hi, thanks for sharing this issue. When working with a 3rd party framework that performs extra build steps, the first things I usually suggest are checking for additional files to include (which you've done), and to try enabling the 'Copy referenced assemblies to output' project-level configurati…

  2. Unit testing with classes from Roslyn.Services namespace results in a SecurityException

    It looks as though this exception is actually an x64/x86 exception in disguise. After setting the 'Use CPU Architecture' NCrunch project-level configuration option to 'x64' for all the projects in the solution, the problem went away. NCrunch normally defaults to x86 when projects are built for…

  3. Testlocation with DeploymentItem inconsistent

    Thanks! I'll take a look and see if I can figure it out. Perhaps if I shake it in the right way, I can reproduce the issue :) Cheers, Remco

  4. Testlocation with DeploymentItem inconsistent

    Hi, thanks for sharing this issue. The working directory of the testing process will definitely vary according to the workspace being used, but the intended behaviour is such that it should be consistent in regards to the TestResults directory or bin\out - so this definitely looks like a defect. …

  5. TF400030: The local data store is currently in use by another operation. Please wait and then try y

    Hi Chris - I haven't heard this one reported before, and there are many NCrunch users running TFS daily. Is there any indication of which file is being locked? Do you have any tests that may be accessing this file? Cheers, Remco

  6. System.Security.VerificationException: Operation could destabilize the runtime

    Hi Atreyu, Thanks for posting! The easiest way to handle this is to simply alter the VB project's .vbproj file and make use of NCrunch's conditional compilation. Inside the default/debug configuration property group, add the following line: <DefineConstants Condition="$(NCRUNCH) == '1'…

  7. NCrunch.Framework.ExclusivelyUses Inheritance

    The declaration for ExclusivelyUsesAttribute doesn't use the AttributeUsage marker for inheritance, but NCrunch does search the entire inheritance structure for it ... so in practice, yes. A test superclass marked with this attribute should have it automatically specified for all subclasses.

  8. xxx.Wait causes intermittent timeout exception

    Hi, thanks for posting! From the description shown, it looks like NCrunch or Xunit is enforcing a timeout of 1000 on your tests. Because the tests are asynchronous and involve waiting between threads, it's possible that while your system is under load, the test takes longer than 1000ms to execut…

  9. Unit testing with classes from Roslyn.Services namespace results in a SecurityException

    Thanks Akim. I've had a good go at trying to resolve and work around this problem using the sample solution you provided. I'm wondering if you can share some more information on the context in which you are working - is this for a critical application where NCrunch simply must work, or for a test …

  10. How do I include generated source code?

    Hi, thanks for posting! The solution to this will depend upon the timing and manner of the generation. How are these files generated? Is this done via an automated test, or special build step? Is there a 3rd party framework involved? Cheers, Remco

  11. Unit testing with classes from Roslyn.Services namespace results in a SecurityException

    Hi Akim - I believe this is related to the same issue described in [url=http://www.ncrunch.net/documentation/troubleshooting_test-and-runtime-related-issues]this troubleshooting page[/url] (the security verification exception). Do the suggestions on this page solve the problem?

  12. Display execution time besides markers when a test runs too slow

    Great idea! Thanks. It might be tough to find physical space for this, but I can see the benefit.

  13. NUnit version

    It is theoretically possible to replace the NUnit binaries that NCrunch uses (which can be found under Program Files (x86)\Microsoft Visual Studio 1X.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010), although the results of this will depend entirely upon how compatible the ver…

  14. Cumulative Processing Time

    Excellent, now I get it! So basically we're talking about introducing a value held against each of the projects that is the sum of the time of all builds executed on this project since the engine was last reset. That should be easy, and useful! I'll see what I can do. Cheers, Remco

  15. Cumulative Processing Time

    Right. Am I correct in my understanding that the problems you are trying to solve are: As a user, given a processing queue full of tests and builds, when a change is made to the codebase, then I want to know how long I need to wait for a specific task to be processed. As a user, given a process…

  16. Problems with code analysis after upgrade

    Thanks Brett! That's just the information I needed. I'll try to introduce a longer term fix, and hope that the additional files will continue to work for you in the meantime. Cheers, Remco

  17. CodeAnalysisRuleSet path does not get copied to workplace

    Excellent, thank you! I'll see if I can sort this out. Cheers, Remco

  18. Problems with code analysis after upgrade

    Hi Brett, Making sure the DLLs are all included using the 'Additional files to include' setting should allow you to work around this. The problem is that NCrunch doesn't have enough of an understanding of your rulesets to identify their DLL dependency, so it just leaves the DLLs out of the works…

  19. Cumulative Processing Time

    Sorry - I misread your post and was trying to think of how such a feature could be applied to the Tests Window, when you were talking about the Processing Queue. What would you see as being the main advantages of the cumulative total as opposed to simply sorting the tasks based on their processin…

  20. Highlight failing test code

    Hi Yang, This is a good suggestion, much because it does highlight a visual issue with the markers and how they line up with source code. Where the source indentation is very deep, it isn't always easy to see what's going on. Implementing this as shown above probably wouldn't be possible with t…