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
Their versioning scheme seems to have four parts, which means the caching in the dependency resolver fails. Here's the line I'm using to introduce the dependency:
The script (myscript.csx) is not cacheable. For caching and optimal performance, ensure that the script only contains NuGet references with pinned/exact versions.
Removing the last part of the version (#r "nuget: Google.Apis.AndroidPublisher.v3, 1.40.2") allows me to cache, but my assumption is that this will ignore any later package releases with version 1.40.2.xxxx as soon as it has cached something.
This is probably a minor issue affecting only a handful of packages overall, but I thought that it might be worthwhile bringing to your attention. Enabling a way to force caching for non-standard package versions would be my suggestion for working around the issue. Is there a way to do it?
The text was updated successfully, but these errors were encountered:
I'm trying to include some data models from the AndroidPublisher package found at https://www.nuget.org/packages/Google.Apis.AndroidPublisher.v3/
Their versioning scheme seems to have four parts, which means the caching in the dependency resolver fails. Here's the line I'm using to introduce the dependency:
#r "nuget: Google.Apis.AndroidPublisher.v3, 1.40.2.1648"
Here's the resulting error:
The script (myscript.csx) is not cacheable. For caching and optimal performance, ensure that the script only contains NuGet references with pinned/exact versions.
Removing the last part of the version (
#r "nuget: Google.Apis.AndroidPublisher.v3, 1.40.2"
) allows me to cache, but my assumption is that this will ignore any later package releases with version1.40.2.xxxx
as soon as it has cached something.This is probably a minor issue affecting only a handful of packages overall, but I thought that it might be worthwhile bringing to your attention. Enabling a way to force caching for non-standard package versions would be my suggestion for working around the issue. Is there a way to do it?
The text was updated successfully, but these errors were encountered: