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
Most official articles about nuget caching (azure, github, and this) suggest using packages.lock.json.
Why nuke does not use the same approach? Is it that key: **/*.csproj is good enough substitution without enabling RestorePackagesWithLockFile property on build?
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
-
Most official articles about nuget caching (azure, github, and this) suggest using packages.lock.json.
Why nuke does not use the same approach? Is it that key:
**/*.csprojis good enough substitution without enabling RestorePackagesWithLockFile property on build?Beta Was this translation helpful? Give feedback.
All reactions