Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. System.MissingMethodException (.net standard 2.0 class lib + 4.7 test project)

    Hi, thanks for sharing this problem. On following these instructions, the MissingMethodException doesn't seem to appear for me. There must be something different about the assembly referencing behaviour in your environment. When you enable the 'Pre-load all assembly references' setting, NCrun…

  2. NCrunch Grid Node server pre-configuration

    [quote=avishnyakov;11711]Looks good. Would the password value remain the same across different VMs? [/quote] Yes, the hash should be the same across environments.

  3. Log from class' ToString() used in TestCaseSource ?

    Hi, thanks for posting. I know of no mechanism that will allow you to write to the log from inside the discovery step. At this stage in the process, NCrunch doesn't have any hooks into the debug or console streams, so it's effectively deaf to everything you throw at it. One option for debugging…

  4. NCrunch Grid Node server pre-configuration

    Hi, thanks for posting. The settings are stored in the registry, under HKLM\SOFTWARE\Remco Software\NCrunch Grid Node. I'd suggest just doing a registry export of this key on a pre-configured node into a .reg file, then importing on any machine you want to run the node on.

  5. Ruleset files using include

    Thanks for sharing this. I'm not sure how easily this can be resolved to a specific file using NCrunch's MSBuild integration, but will put it on the list to take a look. 'Additional files to include' is the correct workaround for now.

  6. .net 4.7.1 support

    [quote=Magbr;11701]I feel so stupid not having figured this out. I was messing around with the binding redirects, I just wasn't doing it in the right project(test project). As an alternative workaround just simply removing the binding redirect from app.config works! [/quote] Great to hear! T…

  7. .net 4.7.1 support

    Thanks! I now have the test solution and it's producing the problem exactly as you've described. The trigger for this seems to be the binding redirections in the app.config file. Even though they are targeting different versions of System.Runtime, somehow this seems to change the resolution seq…

  8. .net 4.7.1 support

    [quote=Magbr;11697] Tell me if the upload went through or not. If not I can upload it to OneDrive and send you a link.[/quote] Doesn't look like it made it :( Including the Nugets is definitely helpful as it reduces the risk of me getting something wrong when calibrating the solution in my own …

  9. Ncrunch nuget PackageReference

    Thanks Daniel! I agree that the path looks like the problem. I'll see what I can do about reproducing and arranging a fix.

  10. Ncrunch nuget PackageReference

    [quote=danius;11691]Manual msbuild worked just fine, see below. could it be that my when ncrunch is unable to parse unicode character in path (note the -> ??) [/quote] That is suspect ... I'm going to need to fish up some more info to be sure .. Would you be able to do the following? - …

  11. Ncrunch nuget PackageReference

    Hi Daniel, Thanks for sharing this problem. It doesn't make sense to me that MSBuild would be giving you this error under NCrunch. I think we should try comparing the NCrunch workspace to your foreground solution, and trying to find the point of difference that is causing this. Try the f…

  12. Grid Node + MSBuild 14 detection

    Great to hear, thanks for confirming! Don't worry about the missing file warning. This is just a goto-hint if you do actually have any problems. Those files naturally won't be on the grid node because it doesn't have VS installed.

  13. .net 4.7.1 support

    Thanks for the extra details. You mentioned that you'd tried to get this running on your laptop (which I assume is a different machine?), did it work there? I think right now we need to try and establish whether this problem is related to your environment, or whether it's solution specific. If …

  14. Grid Node + MSBuild 14 detection

    This problem is caused by the inability of NCrunch on your grid node to locate the installation of VS2017. VS2017 is much more complicated to reference than other versions of VS, as there is no reliable central way of finding it outside of a COM API, which I've had some problems with in the past.…

  15. .net 4.7.1 support

    Thanks for these extra details. The root of the problem here is that NCrunch is attempting to load System.Runtime from the Facades directory. It's doing this because the build system reports the project as being built against the facade of System.Runtime, while the runtime probably expects this …

  16. .net 4.7.1 support

    Where do you see this error message? Does it happen on test execution or discovery? Is this something you can reproduce in a small sample project? Any chance you could submit a bug report after it's happened to you? I might be able to extract more information from the log in the report.

  17. Copy additional files also need CopyReferencedAssembliesToWorkspace

    I think this issue may be related to synchronisation of the nuget packages over the grid. Could you try copying the contents of your User\.nuget directory over to the corresponding user on the grid node? I think that perhaps the grid node doesn't have the nuget package installed, and for some re…

  18. Issues building project, possibly related to SRP

    [quote=Peska;11672]I have the same problem, but unfortunately I cannot apply any rules to my local machine. Is there a way to change this directory? I tried to set up "Workspace base path" in my NCrunch Configuration, but it doesn't have any effects.[/quote] Hi, I'm sorry to hear this is the case…

  19. Copy additional files also need CopyReferencedAssembliesToWorkspace

    Thanks for sharing these extra details. I've built a sample project containing these references and have analysed the build logic involved here. It looks like the file is being copied via standard MSBuild logic. It's a bit more complicated than other references because this particular file seems …

  20. failing to build test project with .net core2 ncrunch v3.10 visual studio 2017

    Hi, Thanks for sharing this problem. At the time NCrunch v3.10 was released, .NET Core v2 had not yet been formally released and is not supported by this build. To resolve this problem, you'll need to upgrade to a later version of NCrunch. Ideally 3.12.