Forum member

mgrundner

22 posts

Posts by mgrundner

  1. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    The warning is when you reference a project in a directory.build.prop file, it builds fine. switched to normal project references directly in the csproj, then the warning goes away (if somebody gets the same issue)

  2. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    [quote=Remco;18051][quote=mgrundner;18050] Thanks! This works but I get a rather missleading warning running the tests in ncrunch, nothing to worry but cosmetic WARNING - c:\program files\microsoft visual studio\2022\community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets: MS…

  3. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    [quote=Remco;18048]Hi, you can just turn off the xunit3 adapter for this project in your NCrunch configuration. Set 'XUnit v3+ Enabled' to False.[/quote] Thanks! This works but I get a rather missleading warning running the tests in ncrunch, nothing to worry but cosmetic WARNING - c:\progra…

  4. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    As a workaround i currently do: <!-- TODO: Remove this after NCrunch solved: --> <PropertyGroup Label="https://forum.ncrunch.net/yaf_postst3559_xunit-v3--missing-xunit-v3-runner-inproc-console-net6-0.aspx"> <OutputType>Exe</OutputType> <UseApphost>true</UseApphost> </Property…

  5. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    Hi Remco! I have the same issue. I've got a testing utils library that got <PackageReference Include="Verify.XunitV3" Version="29.2.0" /> which has a transient dependency on. <PackageReference Include="xunit.v3.extensibility.core" Version="2.0.1" /> Basically all project…

  6. Trace Window Copy

    Damn, now it works. Maybe another tool (barrier, powertoys, or the RDP session) was bugging me. Thanks and sorry for bothering you.

  7. Trace Window Copy

    Hi Remco! It's totally annoying that I can't copy (not with Ctrl+C, nor with context menu (there isn't even one)) in the Trace Window: [img=https://gif.xenial.io/UmTudv43HD.png]Trace Window[/img] That makes troubleshooting exceptions sometime hard and I think this is a low hanging fruit fea…

  8. Run Tests explicit in "VisualStudio" compatible way

    Hi Remco! Yeah I was afraid this is the case, however just wanted to make sure I did not miss any obvious setting or so. However: I think in combination with NCrunchEnvironment.GetOriginalProjectPath i might get a workaround. I'll try to figure out a solution with Simon and let you know our…

  9. Run Tests explicit in "VisualStudio" compatible way

    I am running a rather large testsuite in combination with Verify. Currently i run into a lot of troubles (and also in the past) when i use it in combo with Verify. I've read this https://stackoverflow.com/questions/60710020/when-using-ncrunch-how-would-differences-reported-from-verify-nunit-…

  10. Support for central Package Management & Simplified output path

    Hi Remco! I just played around a little bit and it seams that central package management works just fine. I've got an workaround for me now that at least me use NCrunch :) [code=xml] <!--<UseArtifactsOutput>true</UseArtifactsOutput>--> <UseArtifactsOutput Condition="'$(NCrunch)' == '1'">f…

  11. Support for central Package Management & Simplified output path

    Hi Remco! I currently switched my projects to the 2 new features linked down below. I'm pretty sure that only the package management feature is affecting ncrunch failing to build, but just to let you know that I also use the simplified output path feature. https://devblogs.microsoft.com/nuge…

  12. Windows DevKit 2023 (ARM)

    Thanks Remco, thats what i was thinking. I will post a suggestion.

  13. Windows DevKit 2023 (ARM)

    Tried NCrunch on the new Windows DevKit on ARM. Unfortunatly NCrunch (besides being horrible slow, but thats another issue) dies with: [code=plain] An error occurred while analysing this project after it was built: NCrunch encountered an unexpected error occurred while building an environm…

  14. Support for C# source generators?

    [quote=Remco;15972]Would you be interested in trying the build below? This build includes a change that should force the nCrunch.TestRuntime.DotNetCore.dll assembly into the analyzer environment. In theory it will allow the analyzer to run even when the code generator is instrumented. [url=http…

  15. Support for C# source generators?

    [quote=Remco;15968]Can you confirm whether turning off NCrunch's 'Instrument output assembly' setting for the code generation project resolves the issue?[/quote] In deed, this does the trick. It builds fine and runs the tests. But ofc now coverage for the generator is gone. I can live with that…

  16. Support for C# source generators?

    [quote]If you add the source line: System.Diagnostics.Debugger.Launch(); ... As the first line of code in your source generator, does the debugger prompt appear when you run NCrunch over the solution? This should hopefully be a reliable way to determine whether the source generator is actuall…

  17. Support for C# source generators?

    [quote=Remco;15960]Thanks for sending through these logs. Can you try setting the 'UseSharedCompilation' build property to 'false' for the 'Custom build properties' setting in your NCrunch shared solution settings and let me know if this makes any difference for you?[/quote] No that doesn't ma…

  18. Support for C# source generators?

    [quote=Remco;15958]Thanks for sending this through. According to the log, things appear to be functioning normally - except the output from the source generator doesn't seem to exist. We need a more detailed capture of the build system on your side from when the source generator is supposed to b…

  19. Support for C# source generators?

    [quote=Remco;15956][quote=mgrundner;15955] Should i send a bug report log?[/quote] Yes please! [/quote] Done! :)

  20. Support for C# source generators?

    [quote=Remco;15953][quote=mgrundner;15952] I did a quick check with 4.11.0.2 in VisualStudio 2022 (17.0.5) and it's the same issue[/quote] Testing this on VS2022.17.0.5 it seems to work on my end with your sample solution. Can you confirm the error you're seeing? Do you have any extra configur…