You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vytas-dauksa opened this issue
Sep 5, 2022
· 2 comments
· Fixed by #5269
Assignees
Labels
area: docThe issue requires documentation update, not a code change.triagedThe issue was evaluated by the triage team, placed on correct area, next action defined.
One of our templates accepts --package template parameter, which worked fine in .NET 3.1, however since .NET 5 it's now changed to --param:package. I suspect package became a reserved keyword, but I am not able to find any documentation about such backward incompatibilities. Where could I learn more about this?
The text was updated successfully, but these errors were encountered:
However, since .NET 7.0 we moved to new parser that allowed us to do subcommands. Since .NET 7.0 only parent command options and options that required for instantiations are reserved.
It's not documented anywhere, we need to create an article on this.
area: docThe issue requires documentation update, not a code change.triagedThe issue was evaluated by the triage team, placed on correct area, next action defined.
One of our templates accepts
--package
template parameter, which worked fine in .NET 3.1, however since .NET 5 it's now changed to--param:package
. I suspectpackage
became a reserved keyword, but I am not able to find any documentation about such backward incompatibilities. Where could I learn more about this?The text was updated successfully, but these errors were encountered: