-
Notifications
You must be signed in to change notification settings - Fork 224
Provide an option to 'force' install a global command #2132
Comments
Does --overwrite not work? |
@BrennanConroy : --overrwrite is for conflicting commands...like you could have multiple packages with the same command name |
@kichalla What's the behavior when you use |
@muratg I verified and the |
Should we change the behavior of overwrite or add a new command? If new command what should it be called. |
I think overwrite should just work. Not sure why it doesn't when the package name is the same... |
Yeah, make overwrite reinstall the package. Thought your build script should increment the build number (the |
I am writing a class library which has a command meant to be used as a global command. I am going through several iterations to test if this global command works as its supposed to.
Now since I am still developing and the version of this package is not going to change, I am seeing that
dnu commands install
does not replace the package if its already installed(i suppose my assumption is right?).Can we provide a 'force' option for install which will replace the content even if the version of the package having the command hasn't changed?
Current available options:
Workaround:
Do not use as global command just do
dnx . <global-command-name> <rest of the stuff that the command expects>
The text was updated successfully, but these errors were encountered: