We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you install 6.0 from this link:
https://dotnet.microsoft.com/en-us/download/dotnet?utm_source=getdotnetcorecli&utm_medium=referral
You may get the following looking error when running the NSwag CLI tool:
Failed to initialize CoreCLR, HRESULT: 0x80004005 node:child_process:903 throw err; ^ Error: Command failed: dotnet "/Users/chris/enterprise/InClub/inclub-cms-frontend/src/node_modules/nswag/bin/binaries/NetCore21/dotnet-nswag.dll" run service.config.nswag at checkExecSyncError (node:child_process:826:11) at Object.execSync (node:child_process:900:15) at /Users/chris/enterprise/InClub/inclub-cms-frontend/src/node_modules/nswag/bin/nswag.js:69:11 at ChildProcess.exithandler (node:child_process:388:7) at ChildProcess.emit (node:events:390:28) at maybeClose (node:internal/child_process:1064:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) { status: 137, signal: null, output: [ null, null, null ], pid: 47757, stdout: null, stderr: null }
This is due to a bug in .NET 6.0 (still open) here: dotnet/sdk#13954
I reinstalled 5.0 and my NSwag CLI generator script is working again as expected.
The text was updated successfully, but these errors were encountered:
;)
No branches or pull requests
If you install 6.0 from this link:
https://dotnet.microsoft.com/en-us/download/dotnet?utm_source=getdotnetcorecli&utm_medium=referral
You may get the following looking error when running the NSwag CLI tool:
This is due to a bug in .NET 6.0 (still open) here: dotnet/sdk#13954
I reinstalled 5.0 and my NSwag CLI generator script is working again as expected.
The text was updated successfully, but these errors were encountered: