New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option --no-cache don't work as expected #580
Comments
it is a bug. The no-cache option was intended to bypass dotnet-script cache (forces a full recompile and dependency restore) but your scenario to be able o force an update of the package used by dotnet restore makes sense here too. |
The |
I am not convinced, perhaps it needs a separate flag, something like |
I agree. It should be a separate flag indeed |
Cool! I'll be waiting for the new flag then :) |
This might help with a problem I have seen where the script won't run after I run |
Hello!
Version:
Command:
I expected to see
--no-cache
argument inside commanddotnet restore
, but i don't see it here -Executing 'dotnet restore "/root/.cache/dotnet-script/mnt/c/work/projects/test-project/netcoreapp3.1/script.csproj" -r linux-x64 --configfile "/root/.nuget/NuGet/NuGet.Config"'
I don't have any local errors if run command
dotnet restore --no-cache /root/.cache/dotnet-script/mnt/c/work/projects/test-project/netcoreapp3.1/script.csproj
Does it work as disigned or does it a bug?
The text was updated successfully, but these errors were encountered: