Matthias Koch

Thanks for the heads up. I didn't put much thought into this until yet, but here is what I wish the user experience to look like: 1. User executes global...

Just a heads-up: I crossed this before too and plan to replace with JSON serialization.

``` var newInstance = JsonConvert.DeserializeObject(JsonConvert.SerializeObject(settingsEntity)); ``` ``` [JsonObjectAttribute(MemberSerialization.Fields)] class Settings {} ```

I'm about to prepare the 0.25.0 release. Don't worry about develop. I will rebase this by myself. I'm planning to merge it for 0.26.0 then, but it could take some...

@tunger planned for v0.26.0 ... no worries about the conflicts.

Please see https://github.com/nuke-build/web/blob/master/source/docs/authoring-builds/parameter-declaration.md. Lisp-casing is supported out of the box. But it’s probably still a bug.

So it’s working now? A declaration like `[Parameter] bool SomeThing` will automatically allow the parameter to be passed as `-SomeThing` or `—some-thing`, and even mixed versions. If the doc is...

Ah sorry, I missed that. With quotation it should surely work, that can probably be fixed. But I would recommend to pass the suffix without “-“ and implement the version...

Besides this being an issue, looking at https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-pack?tabs=netcore2x#examples, I really don’t think that VersionSuffix should include a dash prefix.

I think this issue is not trivial to solve, yet it's also not serious. I'm putting it into backlog.