Forum member

eriove

21 posts

Posts by eriove

  1. A project using Fody & PropertyChanged not building

    Just submitted a bug report for the same issue. Should have looked here first. 5.3.0.1 resolved the issue for me.

    11 Mar 2024 08:10 UTC

  2. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    While I was traversing the history, checking out commit after commit and rerunning all tests I found what seems to be a similar issue. I was doing the checkouts from the command line this time and I imagine that there are less events for you to listen on from Visual Studio in that case. Unless yo…

    28 Apr 2020 07:07 UTC

  3. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    I've switched branches multiple times and just when I wrote this message I got the error for the first time. But, it disappeared by itself after 10 seconds so the only reason I saw it was that I looked at the nCrunch window. Even if the problem isn't solved to 100% the error is certainly occurring l…

    24 Apr 2020 13:51 UTC

  4. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    Got the error again while switching between two branches with Dirkster99.AvalonDock version 3.6.2 on both branches, so that might be unrelated.

    23 Apr 2020 06:57 UTC

  5. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    The version in the about window says 4.4.0.7. The nCrunch.BuildHost48.x86.exe and nCrunch.TestHost48.x86.exe is has the Product and File version 4.4.0.7. My feeling is that the error occurs much less often with 4.4.0.7 than the previous version. Perhaps there are two ways of reaching the same sta…

    23 Apr 2020 06:34 UTC

  6. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    I've experimented throughout the day. These are my conclusions: - "Reload and rebuild selected component" does not help resolving the problem, I have to "Restart the nCrunch engine" to resolve the problem. - The .NET Core builds never fail only the .NET Framework builds. - Switching branch is the…

    22 Apr 2020 15:16 UTC

  7. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    Unfortunately I triggered the error again at the first switch of branch. Exactly the same stack trace as in the first post.

    22 Apr 2020 07:03 UTC

  8. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    Thanks! I will test during the day. Looking good for the first 20 minutes, but the error has been intermittent. Will try to provoke it by branch changes and edits to project files.

    22 Apr 2020 06:56 UTC

  9. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    I'm running 4.4.0.2, I was hoping that that version would solve the problem. Had the same problem on 4.3.

    21 Apr 2020 08:40 UTC

  10. The FrameworkReference 'Microsoft.WindowsDesktop.App.WPF' was not recognized

    First of all thanks for an amazing product! We've had a problem for a while with some of our WPF projects targeting .NET Framework 4.8 and .NET Core 3.1. I've been hoping that it would have been a WPF on .NET Core problem but the more patched .NET Core get the more I suspect that it is something …

    21 Apr 2020 08:31 UTC

  11. Setting instrumentation mode to Optimised fails to take project references in account

    We seem to have the same error in one of our solutions. Let me know if I should try to create a smaller project that reproduces the problem as well.

    09 Mar 2020 12:07 UTC

  12. Grid Node Storage Data Limit

    [quote=Remco;8509] NCrunch is quite militant in keeping the snapshot storage directory under the specified limit. If there is a new solution being uploaded to the grid node and there are no solutions to clear out (i.e. they're all in use), the server will actually kick up an error rather than go…

    21 Jun 2017 07:09 UTC

  13. Theory based tests doesn't execute on distributed processing nodes

    I'm surprised it has ever worked if that's the case (and it has). There seems to be something more to it. I've now set all machines to the same settings but still get "This test was not executed during a planned execution run. Ensure your test project is stable and does not contain issues in initi…

    09 Jun 2017 12:45 UTC

  14. Theory based tests doesn't execute on distributed processing nodes

    I didn't check carefully enough. I still have the same problem as in the original post (using the latest version on all machines). Now they sometimes fail on my local machine too and not just on the nodes. I've also noticed that the code coverage shows that the test fails on the first line but…

    09 Jun 2017 12:00 UTC

  15. Local variables unavailable when debugging

    After a couple of restarts of the computer and then it started working. With the latest release (3.9) I've reverted to the files installed by nCrunch and it still works.

    09 Jun 2017 11:40 UTC

  16. Theory based tests doesn't execute on distributed processing nodes

    It was the 2015 version which that wasn't upgraded (which I don't use). But I remember that I replaced the xunit files manually [url=http://forum.ncrunch.net/yaf_postsm10400_Local-variables-unavailable-when-debugging.aspx#post10400]a while ago[/url]. I removed those and ran a repair. Now it works. …

    09 Jun 2017 11:39 UTC

  17. Theory based tests doesn't execute on distributed processing nodes

    I have files from the 26th of May on my local machine and the 1st of June on the grid node. I'll upgrade my machine and get back to you.

    09 Jun 2017 11:24 UTC

  18. Theory based tests doesn't execute on distributed processing nodes

    Hi, After adding a second distributed processing node I've started getting the message [i]"This test was not executed during a planned execution run. Ensure your test project is stable and does not contain issues in initialisation/teardown fixtures." [/i]for all tests with the [Theory] (xunit) a…

    09 Jun 2017 10:37 UTC

  19. Local variables unavailable when debugging

    I tried replacing the files. It still uses the older xunit dll. Will investigate more next week.

    18 May 2017 07:48 UTC

  20. Local variables unavailable when debugging

    Hi, No problem. I haven't managed to reproduce it in a small solution. Only in our 80 project solution. However I get this error message when trying to look at "this" in the watch window: error CS1705: Assembly 'aaa.bbb..UnitTests' with identity 'aaa.bbb.UnitTests, Version=1.0.0.0, Culture=neu…

    18 May 2017 07:03 UTC