docfx icon indicating copy to clipboard operation
docfx copied to clipboard

docfx metadata hangs at: Determining projects to restore... Nothing to do. None of the projects specified contain packages to restore.

Open bartofzo opened this issue 1 year ago • 15 comments

Describe the bug All of the sudden, when running docfx metadata, I get the message:

Loading project /Users/bart/Develop/anypath/AnyPath/AnyPath.csproj Determining projects to restore... Nothing to do. None of the projects specified contain packages to restore.

And nothing happens.

Expected behavior Metadata for the project should be built but instead nothing happens.

Context (please complete the following information):

  • OS: MacOS Ventura 13.2.1
  • Docfx version: 2.77.0

Additional context This is a Unity project with Rider generating the csproj files. This used to always just work, but all of the sudden it doesn't anymore and I have no idea what changed.

doxfx.json for metadata:

"metadata": [ { "src": [ { "src" : "../AnyPath/", "files": [ "AnyPath.csproj" ] } ], "dest": "api", "disableGitFeatures": false, "globalNamespaceId" : "AnyPath", "disableDefaultFilter": false, "filter": "filterConfig.yml" }

partial AnyPath.csproj (if it helps?)

<PropertyGroup> <LangVersion>latest</LangVersion> <_TargetFrameworkDirectories>non_empty_path_generated_by_unity.rider.package</_TargetFrameworkDirectories> <_FullFrameworkReferenceAssemblyPaths>non_empty_path_generated_by_unity.rider.package</_FullFrameworkReferenceAssemblyPaths> <DisableHandlePackageFileConflicts>true</DisableHandlePackageFileConflicts> <CodeAnalysisRuleSet></CodeAnalysisRuleSet> </PropertyGroup> <PropertyGroup> <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform> <ProductVersion>10.0.20506</ProductVersion> <SchemaVersion>2.0</SchemaVersion> <RootNamespace>AnyPath</RootNamespace> <ProjectGuid>{7792acd9-70d2-b29b-3042-273b6d4beb5a}</ProjectGuid> <ProjectTypeGuids>{E097FAD1-6243-4DAD-9C02-E9B9EFC3FFC1};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids> <OutputType>Library</OutputType> <AppDesignerFolder>Properties</AppDesignerFolder> <AssemblyName>AnyPath</AssemblyName> <TargetFrameworkVersion>v2.0</TargetFrameworkVersion> <FileAlignment>512</FileAlignment> <BaseDirectory>.</BaseDirectory> </PropertyGroup> <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' "> <DebugSymbols>true</DebugSymbols> <DebugType>full</DebugType> <Optimize>false</Optimize> <OutputPath>Temp\Bin\Debug\</OutputPath> <DefineConstants>DEBUG;TRACE;UNITY_2020_3_16;UNITY_2020_3;UNITY_2020;UNITY_5_3_OR_NEWER;UNITY_5_4_OR_NEWER;UNITY_5_5_OR_NEWER;UNITY_5_6_OR_NEWER;UNITY_2017_1_OR_NEWER;UNITY_2017_2_OR_NEWER;UNITY_2017_3_OR_NEWER;UNITY_2017_4_OR_NEWER;UNITY_2018_1_OR_NEWER;UNITY_2018_2_OR_NEWER;UNITY_2018_3_OR_NEWER;UNITY_2018_4_OR_NEWER;UNITY_2019_1_OR_NEWER;UNITY_2019_2_OR_NEWER;UNITY_2019_3_OR_NEWER;UNITY_2019_4_OR_NEWER;UNITY_2020_1_OR_NEWER;UNITY_2020_2_OR_NEWER;UNITY_2020_3_OR_NEWER;PLATFORM_ARCH_64;UNITY_64;UNITY_INCLUDE_TESTS;USE_SEARCH_ENGINE_API;SCENE_TEMPLATE_MODULE;ENABLE_AR;ENABLE_AUDIO;ENABLE_CACHING;ENABLE_CLOTH;ENABLE_MICROPHONE;ENABLE_MULTIPLE_DISPLAYS;ENABLE_PHYSICS;ENABLE_TEXTURE_STREAMING;ENABLE_VIRTUALTEXTURING;ENABLE_UNET;ENABLE_LZMA;ENABLE_UNITYEVENTS;ENABLE_VR;ENABLE_WEBCAM;ENABLE_UNITYWEBREQUEST;ENABLE_WWW;ENABLE_CLOUD_SERVICES;ENABLE_CLOUD_SERVICES_COLLAB;ENABLE_CLOUD_SERVICES_COLLAB_SOFTLOCKS;ENABLE_CLOUD_SERVICES_ADS;ENABLE_CLOUD_SERVICES_USE_WEBREQUEST;ENABLE_CLOUD_SERVICES_CRASH_REPORTING;ENABLE_CLOUD_SERVICES_NATIVE_CRASH_REPORTING;ENABLE_CLOUD_SERVICES_PURCHASING;ENABLE_CLOUD_SERVICES_ANALYTICS;ENABLE_CLOUD_SERVICES_UNET;ENABLE_CLOUD_SERVICES_BUILD;ENABLE_CLOUD_LICENSE;ENABLE_EDITOR_HUB_LICENSE;ENABLE_WEBSOCKET_CLIENT;ENABLE_DIRECTOR_AUDIO;ENABLE_DIRECTOR_TEXTURE;ENABLE_MANAGED_JOBS;ENABLE_MANAGED_TRANSFORM_JOBS;ENABLE_MANAGED_ANIMATION_JOBS;ENABLE_MANAGED_AUDIO_JOBS;INCLUDE_DYNAMIC_GI;ENABLE_MONO_BDWGC;ENABLE_SCRIPTING_GC_WBARRIERS;PLATFORM_SUPPORTS_MONO;RENDER_SOFTWARE_CURSOR;ENABLE_VIDEO;PLATFORM_STANDALONE;PLATFORM_STANDALONE_OSX;UNITY_STANDALONE_OSX;UNITY_STANDALONE;ENABLE_GAMECENTER;ENABLE_RUNTIME_GI;ENABLE_MOVIES;ENABLE_NETWORK;ENABLE_CRUNCH_TEXTURE_COMPRESSION;ENABLE_CLUSTER_SYNC;ENABLE_CLUSTERINPUT;ENABLE_SPATIALTRACKING;PLATFORM_UPDATES_TIME_OUTSIDE_OF_PLAYER_LOOP;ENABLE_WEBSOCKET_HOST;ENABLE_MONO;NET_STANDARD_2_0;ENABLE_PROFILER;UNITY_ASSERTIONS;UNITY_EDITOR;UNITY_EDITOR_64;UNITY_EDITOR_OSX;ENABLE_UNITY_COLLECTIONS_CHECKS;ENABLE_BURST_AOT;UNITY_TEAM_LICENSE;UNITY_PRO_LICENSE;ENABLE_CUSTOM_RENDER_TEXTURE;ENABLE_DIRECTOR;ENABLE_LOCALIZATION;ENABLE_SPRITES;ENABLE_TERRAIN;ENABLE_TILEMAP;ENABLE_TIMELINE;ENABLE_LEGACY_INPUT_MANAGER;CSHARP_7_OR_LATER;CSHARP_7_3_OR_NEWER;DEVELOPMENT_BUILD</DefineConstants> <ErrorReport>prompt</ErrorReport> <WarningLevel>4</WarningLevel> <NoWarn></NoWarn> <AllowUnsafeBlocks>False</AllowUnsafeBlocks> <TreatWarningsAsErrors>False</TreatWarningsAsErrors> </PropertyGroup> <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> <DebugType>pdbonly</DebugType> <Optimize>true</Optimize> <OutputPath>Temp\bin\Release\</OutputPath> <ErrorReport>prompt</ErrorReport> <WarningLevel>4</WarningLevel> <NoWarn></NoWarn> <AllowUnsafeBlocks>False</AllowUnsafeBlocks> <TreatWarningsAsErrors>False</TreatWarningsAsErrors> </PropertyGroup> <PropertyGroup> <NoConfig>true</NoConfig> <NoStdLib>true</NoStdLib> <AddAdditionalExplicitAssemblyReferences>false</AddAdditionalExplicitAssemblyReferences> <ImplicitlyExpandNETStandardFacades>false</ImplicitlyExpandNETStandardFacades> <ImplicitlyExpandDesignTimeFacades>false</ImplicitlyExpandDesignTimeFacades> </PropertyGroup>

bartofzo avatar Aug 04 '24 09:08 bartofzo

We had the same issue when building the documentation in our AzureDevops pipeline. The problem on our side seemed to be that we altered the buildNumber during the run (using Nerdbank.GitVersioning).

I do not really understand how this could interfere with docFx but when we disabled this feature in Nerdbank.GitVersioning the docFx command completed successfully.

Here the configuration in the version.json of Nerdbank that triggered the issue:

"cloudBuild": {
  "setVersionVariables": false, 
  "buildNumber": {
    "enabled": true // When true --> docFx "hangs" and doesn't complete
  }

adrian-moll avatar Aug 09 '24 13:08 adrian-moll

Hello, @bartofzo. I'm encountering the same issue with brew and dotnet. You can try downloading the DocFX build directly from the releases. However, have you found a solution for this issue?

goto01 avatar Aug 13 '24 13:08 goto01

Hello, @bartofzo. I'm encountering the same issue with brew and dotnet. You can try downloading the DocFX build directly from the releases. However, have you found a solution for this issue?

I don't know how to install docfx that way. I've already updated it to the latest release using dotnet tool update -g docfx which says it reinstalled the latest stable version 2.77.0

Is there a difference?

No, I haven't resolved it yet unfortunately...

bartofzo avatar Aug 21 '24 07:08 bartofzo

We had the same issue when building the documentation in our AzureDevops pipeline. The problem on our side seemed to be that we altered the buildNumber during the run (using Nerdbank.GitVersioning).

I do not really understand how this could interfere with docFx but when we disabled this feature in Nerdbank.GitVersioning the docFx command completed successfully.

Here the configuration in the version.json of Nerdbank that triggered the issue:

"cloudBuild": {
  "setVersionVariables": false, 
  "buildNumber": {
    "enabled": true // When true --> docFx "hangs" and doesn't complete
  }

I'm not using NerdBank.GitVersioning. Where does it modify the build number? Is there something on my project side I shoud look into? (I've never modified anything about my project except for code and this issue just appeared out of the blue by the way)

bartofzo avatar Aug 21 '24 07:08 bartofzo

We had the same issue when building the documentation in our AzureDevops pipeline. The problem on our side seemed to be that we altered the buildNumber during the run (using Nerdbank.GitVersioning). I do not really understand how this could interfere with docFx but when we disabled this feature in Nerdbank.GitVersioning the docFx command completed successfully. Here the configuration in the version.json of Nerdbank that triggered the issue:

"cloudBuild": {
  "setVersionVariables": false, 
  "buildNumber": {
    "enabled": true // When true --> docFx "hangs" and doesn't complete
  }

I'm not using NerdBank.GitVersioning. Where does it modify the build number? Is there something on my project side I shoud look into? (I've never modified anything about my project except for code and this issue just appeared out of the blue by the way)

NerdBank.GitVersionning affects the build number of the assembly (incrementing the version based on git-history) and additionally sets some environment variables (influencing the BuildNumber inside our AzureDevops Pipeline) --> unfortunately i dont know what exactly what it does behind the scenes.

When I run docfx manually on my machine everyhting works. We only have the issue inside our build pipeline (and only when enabling the buildNumber options).

Do you have any special tool that affects your build ?

adrian-moll avatar Aug 21 '24 08:08 adrian-moll

Hello, @bartofzo. I'm encountering the same issue with brew and dotnet. You can try downloading the DocFX build directly from the releases. However, have you found a solution for this issue?

I don't know how to install docfx that way. I've already updated it to the latest release using dotnet tool update -g docfx which says it reinstalled the latest stable version 2.77.0

Is there a difference?

No, I haven't resolved it yet unfortunately...

You can download the compiled build from the Releases section here.

In the assets section download archive for your system and unzip it.

Screenshot 2024-08-21 at 10 46 07

Currently i'm using v2.75.3

goto01 avatar Aug 21 '24 08:08 goto01

Hello, @bartofzo. I'm encountering the same issue with brew and dotnet. You can try downloading the DocFX build directly from the releases. However, have you found a solution for this issue?

I don't know how to install docfx that way. I've already updated it to the latest release using dotnet tool update -g docfx which says it reinstalled the latest stable version 2.77.0 Is there a difference? No, I haven't resolved it yet unfortunately...

You can download the compiled build from the Releases section here.

In the assets section download archive for your system and unzip it.

Screenshot 2024-08-21 at 10 46 07 Currently i'm using [v2.75.3](https://github.com/dotnet/docfx/releases/tag/v2.75.3)

Yes, but how do I install it? The documentation only shows installation via the command line.

bartofzo avatar Aug 21 '24 09:08 bartofzo

Just download the archive and use the DocFX file within to generate documentation. For example, I downloaded the archive for macOS and unzipped it into /Users/my-user-name/Documents/Docfx.

In your project folder, you can use the DocFX file to run DocFX in your project folder like this: /Users/my-user-name/Documents/Docfx/docfx docfx-config.json --serve

goto01 avatar Aug 21 '24 09:08 goto01

Just download the archive and use the DocFX file within to generate documentation. For example, I downloaded the archive for macOS and unzipped it into /Users/my-user-name/Documents/Docfx.

In your project folder, you can use the DocFX file to run DocFX in your project folder like this: /Users/my-user-name/Documents/Docfx/docfx docfx-config.json --serve

Ok, I did this (also had to use xattr to make it run because of the malware protection). No difference... still hangs at Nothing to restore.

bartofzo avatar Aug 21 '24 15:08 bartofzo

We had the same issue when building the documentation in our AzureDevops pipeline. The problem on our side seemed to be that we altered the buildNumber during the run (using Nerdbank.GitVersioning). I do not really understand how this could interfere with docFx but when we disabled this feature in Nerdbank.GitVersioning the docFx command completed successfully. Here the configuration in the version.json of Nerdbank that triggered the issue:

"cloudBuild": {
  "setVersionVariables": false, 
  "buildNumber": {
    "enabled": true // When true --> docFx "hangs" and doesn't complete
  }

I'm not using NerdBank.GitVersioning. Where does it modify the build number? Is there something on my project side I shoud look into? (I've never modified anything about my project except for code and this issue just appeared out of the blue by the way)

NerdBank.GitVersionning affects the build number of the assembly (incrementing the version based on git-history) and additionally sets some environment variables (influencing the BuildNumber inside our AzureDevops Pipeline) --> unfortunately i dont know what exactly what it does behind the scenes.

When I run docfx manually on my machine everyhting works. We only have the issue inside our build pipeline (and only when enabling the buildNumber options).

Do you have any special tool that affects your build ?

I don't think so. It's a Unity project. The solution is automatically generated.

bartofzo avatar Aug 21 '24 15:08 bartofzo

Hello, @bartofzo. I'm encountering the same issue with brew and dotnet. You can try downloading the DocFX build directly from the releases. However, have you found a solution for this issue?

I don't know how to install docfx that way. I've already updated it to the latest release using dotnet tool update -g docfx which says it reinstalled the latest stable version 2.77.0 Is there a difference? No, I haven't resolved it yet unfortunately...

You can download the compiled build from the Releases section here.

In the assets section download archive for your system and unzip it.

Screenshot 2024-08-21 at 10 46 07 Currently i'm using [v2.75.3](https://github.com/dotnet/docfx/releases/tag/v2.75.3)

Ok so I've tried v2.75.3 and this opens up another can of worms. Running this gives me the following error:

Failed to find all versions of .NET Core MSBuild. Call to hostfxr_resolve_sdk2. There may be more details in stderr.

Which I've encountered before. I used to be able to resolve this by running:

export PATH=/opt/homebrew/Cellar/dotnet/7.0.100/libexec:$PATH

But apparently, I don't have dotnet 7 anymore and it is now dotnet 8. If I change the path to where dotnet8 .0.4 is located (don't ask me why this is even necessary for docfx to run...)

Then I get the following error: BadImageFormatException: Could not load file or assembly 'Microsoft.Build.Framework, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. An attempt was made to load a program with an incorrect format.

This is all of course with version v2.75.3 of docfx which is not the latest release. Running the most recent version of docfx still gives me the "Nothing to do" hang.

Are there any (Apple silicon) mac users out there that are able to run docfx without any issues?

bartofzo avatar Aug 21 '24 15:08 bartofzo

The whole situation with trying to run docfx on my mac is really odd. I have problems getting it to work, and the only way I’ve been able to run it on macbook m1 is by using the archive from the release section; all other options don’t work properly. I also have dotnet 8 installed.

goto01 avatar Aug 22 '24 07:08 goto01

Managed to work around it by building my project using Rider and running docfx metadata directly on the .dll file with the latest version.

bartofzo avatar Aug 26 '24 11:08 bartofzo

Got the same issue after .NET 6 -> .NET 8 upgrade: docfx hangs, and only on CI (works locally).

Nerdbank.GitVersioning is the problem:

  • Removing it from the project fixes the build
  • Disabling both setVersionVariables and buildNumber.enabled fixes the build

Resulting version.json - docfx works:

{
    "$schema": "https://raw.githubusercontent.com/dotnet/Nerdbank.GitVersioning/main/src/NerdBank.GitVersioning/version.schema.json",
    "version": "3.0.0-snapshot",
    "publicReleaseRefSpec": [
        "^refs/heads/main",
        "^refs/heads/\\d+.*$"
    ],
    "cloudBuild": {
        "setVersionVariables": false,
        "buildNumber": {
            "enabled": false
        }
    }
}

ptupitsyn avatar Oct 30 '24 10:10 ptupitsyn

Also running into this, having upgraded from docfx 2.74.1 to 2.78.3.

Image

Taking a stack dump from the lowest node, which apparently is running a build analysis, it appears it hangs on writing stuff to stdout:

Thread (0xA348):
  [Native Frames]
  System.Console.il!System.ConsolePal+WindowsConsoleStream.WriteFileNative(int,value class System.ReadOnlySpan`1<unsigned int8>,bool)
  System.Console.il!System.ConsolePal+WindowsConsoleStream.Write(value class System.ReadOnlySpan`1<unsigned int8>)
  System.Private.CoreLib.il!System.IO.StreamWriter.Flush(bool,bool)
  System.Private.CoreLib.il!System.IO.StreamWriter.WriteLine(class System.String)
  System.Private.CoreLib.il!System.IO.TextWriter+SyncTextWriter.WriteLine(class System.String)
  Nerdbank.GitVersioning!Nerdbank.GitVersioning.CloudBuildServices.TeamCity.SetCloudBuildVariable(class System.String,class System.String,class System.IO.TextWriter,class System.IO.TextWriter)
  Nerdbank.GitVersioning.Tasks!Nerdbank.GitVersioning.Tasks.SetCloudBuildVariables.Execute()
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder+<ExecuteInstantiatedTask>d__25.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[System.__Canon].Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(class Microsoft.Build.BackEnd.TaskExecutionHost,class Microsoft.Build.BackEnd.Logging.TaskLoggingContext,class Microsoft.Build.BackEnd.TaskHost,class Microsoft.Build.BackEnd.ItemBucket,value class Microsoft.Build.BackEnd.TaskExecutionMode)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder+<InitializeAndExecuteTask>d__23.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[System.__Canon].Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder.InitializeAndExecuteTask(class Microsoft.Build.BackEnd.Logging.TaskLoggingContext,class Microsoft.Build.BackEnd.ItemBucket,class System.Collections.Generic.IDictionary`2<class System.String,class System.String>,class Microsoft.Build.BackEnd.TaskHost,value class Microsoft.Build.BackEnd.TaskExecutionMode)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder+<ExecuteBucket>d__19.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[System.__Canon].Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder.ExecuteBucket(class Microsoft.Build.BackEnd.TaskHost,class Microsoft.Build.BackEnd.ItemBucket,value class Microsoft.Build.BackEnd.TaskExecutionMode,class System.Collections.Generic.Dictionary`2<class System.String,class System.String>)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder+<ExecuteTask>d__18.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[System.__Canon].Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder.ExecuteTask(value class Microsoft.Build.BackEnd.TaskExecutionMode,class Microsoft.Build.BackEnd.Lookup)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder+<ExecuteTask>d__13.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[System.__Canon].Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TaskBuilder.ExecuteTask(class Microsoft.Build.BackEnd.Logging.TargetLoggingContext,class Microsoft.Build.BackEnd.BuildRequestEntry,class Microsoft.Build.BackEnd.ITargetBuilderCallback,class Microsoft.Build.Execution.ProjectTargetInstanceChild,value class Microsoft.Build.BackEnd.TaskExecutionMode,class Microsoft.Build.BackEnd.Lookup,class Microsoft.Build.BackEnd.Lookup,value class System.Threading.CancellationToken)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TargetEntry+<ProcessBucket>d__51.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[System.__Canon].Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TargetEntry.ProcessBucket(class Microsoft.Build.BackEnd.ITaskBuilder,class Microsoft.Build.BackEnd.Logging.TargetLoggingContext,value class Microsoft.Build.BackEnd.TaskExecutionMode,class Microsoft.Build.BackEnd.Lookup,class Microsoft.Build.BackEnd.Lookup)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TargetEntry+<ExecuteTarget>d__44.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start(!!0&)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start(!!0&)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TargetEntry.ExecuteTarget(class Microsoft.Build.BackEnd.ITaskBuilder,class Microsoft.Build.BackEnd.BuildRequestEntry,class Microsoft.Build.BackEnd.Logging.ProjectLoggingContext,value class System.Threading.CancellationToken)
  Microsoft.Build.il!Microsoft.Build.BackEnd.TargetBuilder+<ProcessTargetStack>d__23.MoveNext()
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[System.Threading.Tasks.VoidTaskResult,Microsoft.Build.BackEnd.TargetBuilder+<ProcessTargetStack>d__23].ExecutionContextCallback(class System.Object)
  System.Private.CoreLib.il!System.Threading.ExecutionContext.RunInternal(class System.Threading.ExecutionContext,class System.Threading.ContextCallback,class System.Object)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[System.Threading.Tasks.VoidTaskResult,Microsoft.Build.BackEnd.TargetBuilder+<ProcessTargetStack>d__23].MoveNext(class System.Threading.Thread)
  System.Private.CoreLib.il!System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[System.Threading.Tasks.VoidTaskResult,Microsoft.Build.BackEnd.TargetBuilder+<ProcessTargetStack>d__23].MoveNext()
  System.Private.CoreLib.il!System.Threading.Tasks.TaskSchedulerAwaitTaskContinuation+<>c.<Run>b__2_0(class System.Object)
  System.Private.CoreLib.il!System.Threading.Tasks.Task.ExecuteWithThreadLocal(class System.Threading.Tasks.Task&,class System.Threading.Thread)
  System.Private.CoreLib.il!System.Threading.Tasks.Task.ExecuteEntry()
  Microsoft.Build.il!Microsoft.Build.BackEnd.RequestBuilder+DedicatedThreadsTaskScheduler.<InjectThread>b__6_0()
  System.Private.CoreLib.il!System.Threading.ExecutionContext.RunInternal(class System.Threading.ExecutionContext,class System.Threading.ContextCallback,class System.Object)

Native stack, for what it is worth:

ntoskrnl.exe!KeSynchronizeExecution+0x7f36
ntoskrnl.exe!KeLowerIrql+0x1525
ntoskrnl.exe!KeLowerIrql+0x23aa
ntoskrnl.exe!KeWaitForSingleObject+0x267
ntoskrnl.exe!SePrivilegeCheck+0x3068
ntoskrnl.exe!NtWriteFile+0x8c1
ntoskrnl.exe!setjmpex+0x8b35
ntdll.dll!NtWriteFile+0x14
KERNELBASE.dll!WriteFile+0x7b
System.Console.dll+0xcf41
System.Console.dll+0xcd4b
System.Private.CoreLib.dll+0x49af59
System.Private.CoreLib.dll+0x49bc73
System.Private.CoreLib.dll+0x4a55b6
Microsoft.Build.dll+0x1c23c4

Sebazzz avatar Apr 22 '25 08:04 Sebazzz