Challenge to run on Windows OS and .NET core CLI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
A bit of a challenge to execute dotnet cli command on Windows OS.
Whenever configuring using yaml or js config file, the pm2 starts the dotnet service as a new command line window not keeping into monit screen; starting the process as detached.
I understand this could have a better experience on non-Windows OSs, but would be great any support or more cross-platform on Windows for .net CLI.
How could we reproduce this issue?
module.exports = {
apps : [{
cwd: '',
script: 'dotnet',
args: 'run --project src/Services/Payment/Payment.API',
}],
Supporting information
$ pm2 report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows behavior with the JavaScript configuration shown in the issue, using the dotnet run --project src/Services/Payment/Payment.API command. Run pm2 report as requested and compare how the process appears in the monitor versus the new command-line window. Done means the .NET CLI process stays managed and visible in PM2 on Windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100