Sdk: Commands Wishlist

Created on 12 Nov 2016  路  8Comments  路  Source: dotnet/sdk

This issue tracks asks for additional CLI Commands. These may first be implemented as extensions, but affect fairly core functionality so tracking independently.

  • [ ] dotnet version to update a csproj's property dotnet/sdk#6704
  • [ ] dotnet tools list or an equivalent per dotnet/sdk#6499

Most helpful comment

All 8 comments

@piotrpMSFT as part of the hackaton I've done a dotnet prop extension:
https://github.com/simonech/dotnet-prop/

At the moment the syntax is:

dotnet prop 

Commands:
   add   adds a property
   del    removes a proptery
   list    list the properties

Options:
  --version <version> to add/update or remove (without argument) version number
  --runtime<runtime_identifiers> to add/update (multiples) or remove (without argument) supported runtimes
  --framework <framework> to add/update or remove (without argument) framework 

Still hasn't finished (still travelling home) but planning to complete it beginning of the week.
Let me know if it makes sense as generic property setter or better make one extension per property

I'd happy to contribute as PR if you explain me what is need in term of "quality" (tests, code conventions, signing of license, etc...)

dotnet version to update a csproj's property

Would also be nice, when _path to solution dir is a valid git repo_, git -c core.longpaths=true tag v<Version> -am <Version> is also created (like npm version <Version> command does).

Some minor details on this account:

  • both npm version 2.8.5 and npm version v2.8.5 (with or without v) will create git tag v2.8.5 with v. However, the project file package.json gets the version without v.
  • any char other than v is considered an error and only single v is allowed followed by the version number.
  • both incrementing and decrementing versions are allowed, so long the version wasn't previously used; in which case it throws the error (on re-running the command npm version 2.8.5 or npm version v2.8.5):

npm ERR! Command failed: git -c core.longpaths=true tag v2.8.5 -am 2.8.5
npm ERR! fatal: tag 'v2.8.5' already exists

@simonech: @krwq will be cherrypicking your PR to incorporate into the dotnet add verb he is working on :)

Can we move the version discussion into dotnet/sdk#6704? I'd like for whomever picks that up to have the full context :)

@piotrpMSFT @krwq I completed what I was doing, but it's as external tool.
If you prefer it as PR directly to the repo let me know

it would be great to have a command that can pin/update packages or at least a dotnet packages outdated command.

Closing old issues. The update packages command is being tracked at nuget/home.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aguacongas picture aguacongas  路  3Comments

joffreykern picture joffreykern  路  3Comments

dasMulli picture dasMulli  路  3Comments

thomaslevesque picture thomaslevesque  路  3Comments

fmorriso picture fmorriso  路  3Comments