dotnet-version-cli

dotnet-version-cli copied to clipboard

Add recursive option to update all found csproj files

2

Basically `-r|--recursive` which will then search from current directory and down, finding all csproj files, and update them to the same version. Suggestion to keep it simple at first is...

nover

Consider implementing the various version bumps as `commands` and/or change to spectre.console

2

Look here: https://www.areilly.com/2017/04/21/command-line-argument-parsing-in-net-core-with-microsoft-extensions-commandlineutils/ The `CommandLineApplication` has `sub-command` support, and I guess that our different version bumps are actually sub-commands.

nover

Update `dotnet version` to work more like `build` and other baked in dotnet tools

1

Meaning that if you run this in a folder where a `.sln` is present, parse the given solution to find all the csproj files, and then simply apply the specified...

nover

Allow cmd line switches to appear AFTER version bump

1

Invoking as: ``` dotnet version patch -f src/dotnet-version.csproj ``` Does NOT work, whereas ``` dotnet version -f src/dotnet-version.csproj patch ``` Works just fine. It's not a dealbreaker but a nuisance.

nover

To make debugging easier if the tool blows up

nover

If a package has version 1.0.0 and I use the `dotnet version 1.0.0` it errors out with "cannot commit" which is a very bad error. Instead the tool should check...

nover

One possible improvement is to also support `label-number` in the pre-releases, since I noticed that multiple packages use it (and I do it myself from time to time, not always...

eduherminio

nover

Remove default emit of self version

1

When you quickly scan your output buffer it can be confusing. We still want it on the help page, but when it's in "I have fixed stuff mode" it should...

nover

So that the output becomes ``` Bumped abc.csproj from x.y.z to x.y.z ```

nover