Forum member

AlSki

17 posts

Posts by AlSki

  1. NCrunch build failure after adding Microsoft.Net.Compilers package.

    Had the same problem, moving from directory level "Additional folder" to solution level has fixed it.

  2. process has no package identity

    D'oh. Must read the instructions next time. Its a VS2013 Universal app, so shared.dll +WIndows.dll +WindowsPhone.dll. I'm currently testing against the WinPhone dll but I'll switch the testing onto the Windows side. Thanks.

  3. process has no package identity

    Submitted

  4. process has no package identity

    I can still replicate this in 2.13.0.4 and 2.13.0.5 by following the exact instructions above. Switching to HostInsideIDE doesn't help unfortunately. Any suggestions or is there anything else that might help you diagnose? Running VS2013 Premium update 4. The tests work via MS test explorer and…

  5. Hiding UIs during testing

    If you need the full code example with PInvoke just shout, and I'll email it over.

  6. Hiding UIs during testing

    Hi Remco, After steadfastly refusing to unit test Microsoft's UI code for them in the past and working only in the ViewModel and Model tiers, I find myself wanting to write a custom control and therefore test that it works correctly. Which is nice, but also means that some of the time it has to be …

  7. NuGet2.5 native assemblies

    For a while now we've been trying at work to get rid of the last non-packaged dependencies for our applications. We already used NuGet for std things, [i]e.g. nunit.framework, specflow, moq, should etc.[/i] and our own internal libraries but we just had some unmanaged dlls that we couldn't get aroun…

  8. NCrunch instrumentation doesn't show in split/new windows

    If you use the visual studio menu options, Window->Split or Window->New Window then no coverage indicators are applied to additional views. This limits nCrunch interaction to the first window that was opened only.

  9. Integration with SpecFlow

    Sorry been thinking about this a little more. Where a file has a custom tool that generates another file, then nCrunch is kicking off builds as you change the source file even though nothing will be different in the build until you save and therefore trigger the custom tool to create the generat…

  10. Integration with SpecFlow

    Thanks Remco. I'm perfectly happy with the workaround, just wasn't sure if you took account of any Custom Tools, including WinForms Designer or Data Designer generated as well. I suppose if nobody else is raising this then its not a feature to consider yet. :-)

  11. Integration with SpecFlow

    In case you don't use it, Specflow uses xxx.feature files with a Custom Tool attribute in VS, "SpecFlowSingleFileGenerator" that automatically generates a xx.feature.cs file whenever you save the .feature. The feature.cs contains the testable code. So if I modify my feature, ncrunch detects that and…

  12. v1.37b failing to build project that v1.26 did

    Moving to dynamic analysis does correctly solve the problem. The offending code is [quote] public enum TestCategory { FAST_RUNNING_TESTS, SLOW_RUNNING_TESTS } [AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Class | AttributeTargets.Method, AllowM…

  13. v1.37b failing to build project that v1.26 did

    About is now showing correctly though.

  14. v1.37b failing to build project that v1.26 did

    Uninstall - Reboot - Download - Install And still I get the following on ONE of the two different Test projects, the other is fine. (0): System.InvalidCastException: Unable to cast object of type 'System.Int32' to type 'System.String'. at nCrunch.TestExecution.Frameworks.NUnit.NUnitStatic…

  15. v1.37b failing to build project that v1.26 did

    Intruigingly, it looks as if 1.38.17b is lableed in the about box as 1.37b. Attempting to upgrade simply gives me repair/remove.

  16. v1.37b failing to build project that v1.26 did

    After upgrading I'm now getting a build error for an older set of nUnit tests. Thought it might be nUnit related but the stack suggests otherwise. Just reply if you need more info. (0): System.InvalidCastException: Unable to cast object of type 'System.Int32' to type 'System.String'. at nC…

  17. Collapsed regions

    I use Edit->Outlining->Collapse to definitions (Ctrl M-O) a lot, but the only problem is that I now collapse the coverage indicators too. Is there any chance that a summary indicator could be provided on the method definition line, indicating whether the method was called at all?