Forum member

yanglee

89 posts

Posts by yanglee

  1. Markers not clickable

    The issue seems to be fixed after I followed your instruction: 1. Uninstall NCrunch; 2. Reboot and run 'devenv.exe /setup' to reset the VS extension cache; 3. Reinstalling NCrunch; Cheers, Yang

    22 Dec 2012 21:36 UTC

  2. Markers not clickable

    Just sent the Report file via this page: http://www.ncrunch.net/Support/Contact I tried sending Report in VS but got network error.

    20 Dec 2012 11:29 UTC

  3. Markers not clickable

    [quote=Remco;3445]Thanks Yang. If you see this happen again, could you send through a bug report? [/quote] Sure :)

    20 Dec 2012 10:44 UTC

  4. Markers not clickable

    NCrunch 1.43 VS 2012 Windows 8 64bit The markers were displayed correctly but not responding to mouse events. I've experienced this multiple times with version 1.42, but it's the first time I experienced this since upgraded to 1.43 about 9 days ago. I tried resetting NCrunch, restarting VS, …

    19 Dec 2012 22:07 UTC

  5. Run all tests on Build

    [quote=Remco]Yang, I also share your concerns about the lifetime of SSDs under NCrunch. There is a feature I'm working on that I hope will be able to significantly reduce (or even solve) this problem :)[/quote] That's great news, cheers! :)

    17 Dec 2012 20:11 UTC

  6. Run all tests on Build

    Run tests when save or build would be great. Run tests on type is not a big problem for my desktop PC, I put NCrunsh's workspace data on a 4GB RAMDisk. But next month I plan to get a Microsoft Surface Pro. Run tests on type would be a problem because Surface Pro has only 4 GB ram, not space fo…

    17 Dec 2012 13:11 UTC

  7. Add/Move "Allow parallel test execution" to the Project Level

    Just in case you missed this: [url=http://www.ncrunch.net/documentation/guides_integration-testing]Documentation - Integration Testing[/url] You can use [url=http://www.ncrunch.net/documentation/reference_runtime-framework_exclusively-uses-attribute]ExclusivelyUsesAttribute[/url], [url=http://ww…

    07 Dec 2012 19:46 UTC

  8. NCrunch is stuck

    I get this issue about 1~3 times a week. Have to Reset (Resynchronize) NCrunch or restart VS to bring it back. I thought this was a known issue so didn't report it. I also don't think I can reproduce this. I'm not sure but it seems it happens more often when I work with xaml files and when I rena…

    07 Dec 2012 15:01 UTC

  9. How can I force NCrunch to run tests in STA?

    I got this error before when I use Resharper. The solution was add [STAThread] to the test method.

    07 Dec 2012 13:45 UTC

  10. Optional argument causes build error when PCL does not target Silverlight

    It appears turning off 'Instrument Output Assembly' not only turns off code coverage, but also causes another problem: When navigate to a source file via the stack trace of the Exception popup or NCrunch Tests window, a copied file in the NCrunch's workspace will be opened instead of the original so…

    15 Nov 2012 15:29 UTC

  11. Optional argument causes build error when PCL does not target Silverlight

    [quote=Remco;3110]For anyone experiencing this problem, a potential workaround is to turn off the 'Instrument Output Assembly' setting for the project failing to build. Although this will turn off code coverage for the project, it should allow other depending projects in your solution to build and …

    07 Nov 2012 04:55 UTC

  12. Optional argument causes build error when PCL does not target Silverlight

    NCrunch 1.42.0.12 VS2012 Windows 8 64bit This is a similar issue to this one: [url=http://forum.ncrunch.net/yaf_postst577_Portable-class-libraries-fail-to-build-if-they-include-metro.aspx]Portable class libraries fail to build if they include metro[/url] Resharper and the built in test runne…

    06 Nov 2012 05:08 UTC

  13. Cannot change forum profile

    Hi, I just tried to hide my blog, but couldn't find an option to do that. It seems my profile is in read-only mode. Also I couldn't find the PM button. I'm using Firefox 16 and IE 9.

    30 Oct 2012 20:10 UTC

  14. Extensions for NCrunch

    That's great! I never seriously used Visual Studio SDK before. Today I took a look and found it very interesting. Currently I plan to make a small tool window that displays failed tests and their stack trace.

    30 Oct 2012 18:28 UTC

  15. Extensions for NCrunch

    Hi Remco, I'm interested in writing extensions for NCrunch, do you have any plan to make NCrunch support extensions? Cheers

    29 Oct 2012 02:16 UTC

  16. Pin Exceptions window, show markers for TestCase

    [quote=Remco;3051]Hi Yang - Thanks for the suggestions! Can you share a bit more detail around why you feel pinning the stack trace window would help you? The original intention of this popup was to basically be a transient way to navigate up and down the stack. Are you using it to examine t…

    29 Oct 2012 02:01 UTC

  17. Pin Exceptions window, show markers for TestCase

    Hi, Would be great if the Exceptions window could be pinned, this would help quickly fix broken tests. Also markers for TestCase would be cool. See the image below: [img]http://dl.dropbox.com/u/46508238/forum.ncrunch.net/2012-10-28%2012-03-07%20AM.png[/img]

    27 Oct 2012 16:14 UTC

  18. A small "Failed Tests" window

    Just a thought. I think maybe the visibility of the toolbar and error message should be binded to the size of the Tests window. They are hidden when the Tests window becomes too small. This way, when I dock the Tests window below the Solution Explorer, the toolbar and error message would be hidde…

    24 Oct 2012 08:06 UTC

  19. A small "Failed Tests" window

    [quote]I'm of a mind to try and limit the number of tool windows, as there are already so many.[/quote] Understood. [quote]Can you think of modifications that could be made to the Tests Window to allow it to fit in a smaller space? Do you think that adding an option to hide the toolbar would hel…

    23 Oct 2012 23:36 UTC

  20. A small "Failed Tests" window

    Hi, It would be great if there was a small "Failed Tests" window that displays a list of all failed tests. I would dock it below the Solution Explorer. This would help me quickly locate and fix all failed tests. I know the "Tests" window, but it's too large and displays lots of unnecessary inf…

    23 Oct 2012 21:46 UTC