Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch cannot build .NET Standard 2.0 projects

    [quote=Marcello;15826] Creating a path variable "MSBuildSDKsPath" with the value "C:\Program Files\dotnet\sdk\2.1.518\Sdks" did the trick. [/quote] Great to hear! [quote=Marcello;15826] Anyway, if I try uninstalling the Dotnet SDK-6.0.100 package, it does not work anymore. [/quote] Mos…

  2. NCrunch cannot build .NET Standard 2.0 projects

    Thanks for sharing these details. The error confirms that this is a platform install issue and is not specific to NCrunch. The installation of MSBuild on this machine is unable to find the correct install path of the DotNet targets. In theory, if you can solve the install issue and the projec…

  3. NCrunch cannot build .NET Standard 2.0 projects

    Thanks for confirming this. The next step is to try and see if we can build the project on your grid node without NCrunch involved. Please try the following steps: 1. Copy your test solution to the grid node to a temporary directory 2. Find the installed instance of msbuild.exe on your grid …

  4. NCrunch cannot build .NET Standard 2.0 projects

    [quote=Marcello;15819] Unfortunately, it did not help, the issue is still there. [/quote] Sorry, this was my mistake. I sent you the link to download the runtime of .NET 6.0, when actually it seems we needed the SDK. Try the one below instead: [url=https://dotnet.microsoft.com/download/dotne…

  5. NCrunch cannot build .NET Standard 2.0 projects

    Can you try downloading and installing the following version of the .NET SDK on the grid node, then restart the machine and let me know if this changes anything? [url=https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-6.0.0-windows-x64-installer]https://dotnet.microsoft.com/download/d…

  6. NCrunch cannot build .NET Standard 2.0 projects

    Do you know if this use case worked for you before the latest NCrunch version? (I'm trying to identify if this is a long standing issue or a recent regression).

  7. NCrunch cannot build .NET Standard 2.0 projects

    This is perfect, thanks! I'll get back to you soon.

  8. NCrunch cannot build .NET Standard 2.0 projects

    Could you please do the following for me? 1. Open the sample project you sent to me in VS2019 on your client machine 2. Set your 'Log Verbosity' to 'Detailed' in your NCrunch configuration 3. Set your 'Build Log Verbosity' to 'Detailed' in your NCrunch configuration 4. Reset the engine and let…

  9. NCrunch cannot build .NET Standard 2.0 projects

    Thanks - Just to be sure, can you confirm that you are receiving the exact same missing build target error on the grid node when you use both VS2019 and VS2022 on the client?

  10. NCrunch cannot build .NET Standard 2.0 projects

    [quote=Marcello;15806]VStudio Build Tools 2017 --> v15.9.27 VStudio Build Tools 2019 --> v16.7.5[/quote] Can you please confirm the version of Visual Studio you have installed on the client machine that you are using to access the grid node?

  11. NCrunch cannot build .NET Standard 2.0 projects

    You've mentioned that you have the MSBuild tools for VS2017 and VS2019 installed on the grid node. Can you confirm for me the version of Visual Studio being used on the client machine?

  12. NCrunch cannot build .NET Standard 2.0 projects

    Thanks for the video. This confirms that the first problem (locating the installation of Dotnet) on the machine appears to be resolved. I'm going to conduct some experiments on this side to try and identify why the build tools aren't being correctly resolved. At the moment I'm wondering if this m…

  13. NCrunch cannot build .NET Standard 2.0 projects

    Thanks. Can you confirm whether the DOTNET_MSBUILD_SDK_RESOLVER_CLI_DIR environment variable on the grid node has any effect on the issue? Note that you'll need to restart the grid node service before any environment variable changes take effect.

  14. NCrunch cannot build .NET Standard 2.0 projects

    Hi, I've tested your sample project and it compiles fine under NCrunch in all our test environments under both VS2019 and VS2022. Based on the stack trace you've provided, this issue is being caused by a configuration or platform installation issue in your environment. Can you confirm for m…

  15. NCrunch cannot build .NET Standard 2.0 projects

    Hi, thanks for posting. On machine 1, it looks like the Dotnet SDK is not correctly installed. Usually this is installed to 'C:\Program Files\dotnet', and there must be a reference to it in your system's PATH environment variable. Alternatively, you can set the DOTNET_MSBUILD_SDK_RESOLVER_CLI_D…

  16. nCrunch fails building code containing languageext's newtype

    Hi, thanks for sharing this issue. Under NCrunch v4.11 (the latest version), I wasn't able to reproduce this problem using the sample code you've provided. Could you check whether this happens for you under the latest version on NCrunch? If so, would you mind submitting a bug report via NCrun…

  17. NCrunch cannot build dotnet 5 projects

    Thanks for submitting the report. The problem is caused by a couple of custom environment variables you have configured for NCrunch. They are pointing at an SDK install path that most likely doesn't exist: DOTNET_MSBUILD_SDK_RESOLVER_SDKS_VER = 5.0.302 DOTNET_MSBUILD_SDK_RESOLVER_S…

  18. NCrunch cannot build dotnet 5 projects

    Could you try submitting a bug report after you experience the build failure? I might be able to glean some useful info from the log in the report.

  19. NCrunch v4.11 and VS 2022 Pro Current

    Hi Lucian, This could be an install state issue or package loading bug. We've observed situations where VS just decides it won't load packages for a session, and the NCrunch code never gets called. Try starting the IDE without loading a project, then opening your solution using the File menu (t…

  20. TeamCity Timeline incorrectly sized for the window

    Excellent, thanks for sharing this. Outside of writing your own tool to manipulate the report, I can't think of any immediate way to work around this issue. I'm tasking it up here to be addressed and we'll get onto it as soon as we're able to.