Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. .NET Core support for NCrunch (first public build)

    [quote=memark;9863]Oh ok, I see. No problem, I fully understand your reasoning. But it's still little confusing when you provide builds for all versions of Visual Studio in your post. You might consider removing the ones not actually supported, since users visiting this post probably came here to…

  2. .NET Core support for NCrunch (first public build)

    Sorry, I should have clarified. This build won't work with .NET core projects that are using xproj/project.json. It will only work with .NET Core projects as built from the VS project templates under VS2017. This is because the xproj/project.json system is built on a whole toolchain that has be…

  3. Inconsistent compiler results

    Ok, I think we're narrowing this down. My theory right now is that there is a specific code element causing this problem. The good news is that because this is your test project, it's likely at the top of the dependency structure, so it should be possible to deductively figure out which elemen…

  4. .NET Core support for NCrunch (first public build)

    I'm happy to announce the first public test build for .NET Core support in NCrunch. This build of NCrunch is able to load .NET Core projects, build them, instrument their assemblies, construct test environments and run xUnit/MSTest/NUnit tests end-to-end. Distributed processing has also been imple…

  5. Inconsistent compiler results

    I don't think this problem is likely to be caused by the MSBuild warnings. There must be a physical reason for the hash being different between these machines. Are both machines using x64 processors? Would you be able to walk me through the exact steps you've used to compare the two files using…

  6. Unnecessary .ncrunchproject files

    The "Project Config File Storage Path" setting was actually designed specifically to address the problem with NCrunch config files messing with git submodules. Are you experiencing any problems with this setting? Removing the 'PreviouslyBuiltSuccessfully' value from the configuration files would…

  7. Inconsistent compiler results

    Are you using the log4net library? I'm wondering if there may be more to this problem than an IL difference. How many machines do you have in your grid? I'm also particularly interested in whether you can find some kind of pattern around when this is reported.

  8. NCrunch Issue with NuGet Package with Generic

    Ideally a sample of the project itself with any dependencies required to build it. I might be able to reproduce it with just the compiled DLL for this project, but a full code sample with dependencies will usually give certainty that I can reproduce the problem and produce a proper test case for it…

  9. Inconsistent compiler results

    I think these comments are generated by ildasm.exe, so it may not be the cause of the problem. If you copy the assembly over from the other machine, then use the same machine to generate the IL dump from both assemblies, are the comments consistent? Does the problem appear to be inconsistent for…

  10. Inconsistent compiler results

    NCrunch will ignore the image base and MVID. The hash is generated using the IL contents of the methods themselves, with a few considerations for oddities (such as compiler generated code). You mentioned that there are cultural differences between the assemblies. This may be suspect. Can you e…

  11. NCrunch Runs Wrong Test(s)

    Hi Ed, I wish I could give a fast answer on this, but it would take either some running through the NUnit source code or a bit of testing to confirm whether the description would be enough. Personally, I would recommend SetName, because this is one that I'm sure will work. In all prior situatio…

  12. Build exception

    Hi, thanks for sharing this issue. This problem is likely being caused by an IL sequence that NCrunch isn't designed to handle. It may be possible to work around this problem by turning off the 'Instrument output assembly' setting for this project. Are you able to share with me a project that…

  13. NCrunch Runs Wrong Test(s)

    Hi Ed, When using user types as parameters to test cases, you need to be very careful to make sure that the name NUnit is generating for the test is unique. If you have two tests with different instances of the same user type, it's possible that NUnit's generated name for the tests ends up being…

  14. NCrunch Runs Wrong Test(s)

    Hi Ed, Can you share any details about how these tests are being generated? Are you using TestCaseSource? The working of this are all behind the test framework itself (NUnit3), though I think this may be a test case identification issue of some kind. If the tests don't have unique and distin…

  15. Inconsistent compiler results

    Hi Michael, Do you have any other versions of VS (i.e. VS2017 or any of its updates) installed on either your local machine or the grid server? One way to analyse this issue further is to use ildasm.exe to obtain an IL-dump of the assembly on both your workstation and your grid server. You can…

  16. Memory Leak in Large Project

    There must be a build step that is causing this. Are you able to narrow it down to a specific project? Do you have any projects in your solution that could be considered unusual?

  17. Memory Leak in Large Project

    Hi, thanks for sharing this issue. Svchost.exe is used to host a range of services and O/S level software. This won't be hosting any of NCrunch's code, but because NCrunch executes builds and test code, I would say there is a likelihood here that it is triggering this problem indirectly. Do y…

  18. Build Issue - VS 2017 RC 4

    Hi, Thanks for sharing this issue. Please note that NCrunch does not yet support netstandard or .NET core projects. This is currently a work in progress. For the latest information, please see [dead link].

  19. 3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

    [quote=jnm236;9819]This is a brand new installation of Windows. I needed to build for net20, so I went to "Turn Windows features on or off" and checked the .NET Framework 3.5 box. Then I restarted. Then on a whim I tried the NCrunch installer again and it worked fine. I hadn't run the VS install…

  20. 3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

    Hi, thanks for sharing this issue. Do you still have the error message that the NCrunch installer was giving you? The NCrunch installer is mostly just an xcopy MSI into the VS directory. The error you've described doesn't seem like any of the error checks that are manually coded into the MSI. …