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
Nice extension and a handy one, but lately I am using Directory.Packages.props file in one of my solutions where I store all the packages versions in one place from where specific multiple projects can read them. This way in the projects themselves we do not indicate the version number but only the name of the package.
It would be nice to see the extension reading from that file and associating version numbers per project as for now it just shows projects without versions. I understand that it can be tricky because you show and update packages per project in the extension, but here you kind of must do it in one place... So it is maybe not the best UX if I click to update in one of the project and under the hood it updates centrally and in all other projects consequently.
Possible workaround and actually more or less proper UX as I see it (correct me if it sounds wrong) is that you will have the Directory.Packages.props section visible separately above (or under) all the projects. There you will be able to manage all the packages which controlled bu it. And then in the projects section it should be clear which packages are retrieved from the Directory.Packages.props file (and they SHOULD NOT be manageable) and which are directly managed per project (and those you can control as we do today).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
Nice extension and a handy one, but lately I am using Directory.Packages.props file in one of my solutions where I store all the packages versions in one place from where specific multiple projects can read them. This way in the projects themselves we do not indicate the version number but only the name of the package.
It would be nice to see the extension reading from that file and associating version numbers per project as for now it just shows projects without versions. I understand that it can be tricky because you show and update packages per project in the extension, but here you kind of must do it in one place... So it is maybe not the best UX if I click to update in one of the project and under the hood it updates centrally and in all other projects consequently.
Possible workaround and actually more or less proper UX as I see it (correct me if it sounds wrong) is that you will have the Directory.Packages.props section visible separately above (or under) all the projects. There you will be able to manage all the packages which controlled bu it. And then in the projects section it should be clear which packages are retrieved from the Directory.Packages.props file (and they SHOULD NOT be manageable) and which are directly managed per project (and those you can control as we do today).
Beta Was this translation helpful? Give feedback.
All reactions