Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. FileNotFoundException UTFResources

    My suspicion here is that there is somehow an indirect reference from the assertion code in Microsoft.VisualStudio.QualityTools.UnitTestFramework to the missing DLL. I haven't seen this before. It's possible you're tied into a version of MSTest that I haven't tested with previously, or there is so…

  2. Building C# solution with some C++/CLI references

    Hi, thanks for sharing this issue. It's unfortunately because of issues like this one that the decision was eventually made not to have official support for C++ builds under NCrunch. While many use cases still work, there were just too many edge cases (like this one) that seemed to need their ow…

  3. FileNotFoundException UTFResources

    Hi Lee, Thanks for sharing this problem. Do your projects have any references to the Microsoft.VisualStudio.QualityTools.UTFResources.dll file? If not, does adding references resolve this issue? Is this for .NET Framework or .NET Core?

  4. Test Only Build Locally

    [quote=alexpolajenko;10519]I went ahead and jsut created a new unit test project and put in the test I needed. Now everything works[/quote] Thanks for confirming this. This problem has me a bit baffled. If you discover what was causing it, please do let me know.

  5. Disable auto restoring nuget packages

    The console tool is programmed to always run "msbuild /t:Restore" for each project at load time. This is because the newer MS CLS project system and .NET Core projects require 'restore' to be run to initialise the project.assets.json file inside the /obj directory for each project. VS does this au…

  6. Weird nuGet issues when NCrunch enabled and reloading a solution

    Hi Chadwick, Thanks for posting! Much of the synchronisation handling around projects and Nuget was adjusted in NCrunch v3.8. I recommend upgrading to see if this helps. I am aware of a race condition that can cause a clash between VS trying to perform restore action on projects at the sam…

  7. Test Only Build Locally

    Thanks for sending through the report. The report didn't show anything out of the ordinary. The NCrunch client is not sending work to the remote server because it believes it has no work that the remote server can process. Everything here points to a configuration issue. Could you try closing …

  8. Error when starting VS

    Hi, it looks like something has gone wrong with your global configuration file. Try deleting the file(s) at C:\Users\USER\AppData\Roaming\NCrunch.

  9. Test Only Build Locally

    Thanks for confirming this. A few more things to check: - Does turning off your local processing in the Distributed Processing Window then resetting the engine make any difference to this behaviour? - If you set up a new little solution with a test project containing a single test, and use dist…

  10. Test Only Build Locally

    Check that the project doesn't have a required capability configured. See here for more information - [url=http://www.ncrunch.net/documentation/reference_project-configuration_required-capabilities]http://www.ncrunch.net/documentation/reference_project-configuration_required-capabilities[/url].

  11. Can't run tests with VS 2017 / XBehave 2.2.0-beta0003-build685 / XUnit 2.2

    I'm wondering if you may be interested in giving the build below a spin. This build includes significant changes to Xunit integration, and should work correctly with v2.2. Assuming it doesn't explode on you, I'll probably release it tomorrow. [url=http://downloads.ncrunch.net/NCrunch_Console_3.…

  12. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    Ok, fixes for both of the above mentioned problems are included in the build below: [url=http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.msi]http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.msi[/url] [url=http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.zip]http://downloads.ncrunch.…

  13. NUnit "Root element is missing" error on multiple brand new projects

    A fix is now available for this in the build below: [url=http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.msi]http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.msi[/url] [url=http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.zip]http://downloads.ncrunch.net/NCrunch_Console_3.9.0.1.zip[…

  14. Test Only Build Locally

    Hi, thanks for posting! I'll need some more information before I can properly answer this question. Here's a few questions to help understand the situation: - If you open the Processing Queue Window, do you see build/analysis tasks for your projects on both your local machine and the remote g…

  15. NUnit "Root element is missing" error on multiple brand new projects

    Hi, This is caused by an unintentional change to the NUnit API. There is a fix pending for this in both NCrunch and in NUnit. See here for more details - [url=https://github.com/nunit/nunit/issues/2205#issuecomment-304873287]https://github.com/nunit/nunit/issues/2205#issuecomment-304873287[/url…

  16. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    [quote=ghelyar;10491][quote=Remco;10490]Since you have the 'Copy referenced assemblies to workspace' setting turned on, it shouldn't make any difference in your case ..[/quote] I have only turned it on because of the new behaviour/warning introduced in ncrunch 3.8. I did what it told me to do, and …

  17. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    Ok, it looks like there is a problem with the TestHost support in that it switches itself on for .NET Framework when it probably isn't needed. This will hurt NCrunch's build optimisation. Since you have the 'Copy referenced assemblies to workspace' setting turned on, it shouldn't make any differen…

  18. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    Thanks Alastair for your help in diagnosing this issue. When .NET Core generates these .deps files, it uses the name of the output assembly (dll) for each project, where it looks like NCrunch is using the project name (oops). Because your solution has projects with a different output assembly name…

  19. .NET Core 2.0 support

    Hi, The last I heard, .NET Core v2 was on a timetable for a September release. I'm not sure if things have changed since then. Integrating with code still under development isn't really feasible, because the code changes faster than it can be tied into. Sorry, I'll need to make an informed a…

  20. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    The 'libraries' and 'targets' declarations for the projects in your referencing structure (most specifically, WebAPI but also the other projects) are the key to making this work. You'll likely find that if you manually add these into the .deps files in your NCrunch-generated workspace then re-run y…