Closed zdfowler closed 2 years ago
Do you have any theories on why it would be different on different machines? Are they using different versions of the dotnet SDK?
On Mon., 11 Oct. 2021, 23:51 Zac, @.***> wrote:
We are having mixed results with dotnet new -i for the 3.1.1 template. On some machines the full version name is required to pull it down (dotnet new -i SAFE.Template::3.1.1) On others, the version number isn't required (dotnet new -i SAFE.Template works).
Referencing https://www.nuget.org/packages/SAFE.Template/, the install sample includes the version spec, but previous versions and the docs do not indicate that is required.
Not sure if this is a packing issue or a client machine issue. Anyone else having trouble?
Thanks!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SAFE-Stack/SAFE-template/issues/478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF5P62R4NMPPMQBH7IAQKDDUGLMVZANCNFSM5FYFMLOA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
We thought it was a corporate network issue, tbh, and ruled that out. Clients working as expected using the SAFE.Template alias were 5.0.302 and 5.0.401 Clients only working with the SAFE.Template::3.1.1 version tested with 5.0.402.
We have a workaround by using the full version spec of course, but my team opened a ticket on it and we couldn't identify. Wondering if it is something in the nuget spec/package deployment, but wouldn't have enough know-how to know.
Do you have any global.json
files floating around in the folder structure? I've noticed this sometimes - it'll pull down a different version depending on which version of .net core the implicit context is bound to.
FWIW -- we did not pursue any further. We updated the pull to use a specific version as noted above and moved on. Appreciate the conversation. Not solved, but the workaround was clearly sufficient.
@isaacabraham - No. It was a clean working directory.
We are having mixed results with dotnet new -i for the 3.1.1 template. On some machines the full version name is required to pull it down (
dotnet new -i SAFE.Template::3.1.1
) On others, the version number isn't required (dotnet new -i SAFE.Template works
).Referencing https://www.nuget.org/packages/SAFE.Template/, the install sample includes the version spec, but previous versions and the docs do not indicate that is required.
Not sure if this is a packing issue or a client machine issue. Anyone else having trouble?
Thanks!