Marco van den Oever
Marco van den Oever
@boscodsouza82 Thank you for reporting the issue! Could you post the logs, they should be in: ``` C:/users/username/appdata/local/temp/wtq/logs ```
@boscodsouza82 Thank you for the detailed explanation and the kind words!
@boscodsouza82 Thanks so much, I appreciate the quick responses! Could you drop a screenshot of the multiple powershell windows perhaps? I'm really confused why that's happening. I totally agree though...
Version v2.0.11 has an updated method of starting processes, I'm _pretty_ sure this shouldn't happen anymore.
[Another approach](https://github.com/flyingpie/declarative-command-line) I've been experimenting with, using a source generator.
@juwens I've encountered the same problem, but the latest "main" version does seem to have fixed this. Could you try to test that version? ```bash # Clone git clone https://github.com/dotnet/command-line-api.git...
@juwens With release 2.0, the issue has been fixed for me. Can you check that?
The part where the name handling happens: https://github.com/nuke-build/nuke/blob/develop/source/Nuke.SourceGenerators/StronglyTypedSolutionGenerator.cs#L93C1-L93C72
@nabaxo Thank you for reporting this! Could you share your settings file? Also, what installation method are you using?
Way too much, totally agree. Seems to be some weird stuff going on somewhere, need to try and find out where all this unmanaged memory is coming from: