-
Notifications
You must be signed in to change notification settings - Fork 45
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
The "PackageRetrievalTask" task failed unexpectedly with version 4.0.0 #47
Comments
Did you perform the upgrade without Visual Studio? Unless you're using PackageReference (which you aren't), NuGet packages need to be installed via VS to run the installation routines. |
Hi, I did the upgrade thru the Visual Studio - but I did customize the previous version a bit - so the upgrade is quite tricky. R. |
Getting the error "Part URI is not valid per rules defined in the Open Packaging Conventions specification." when we click on the "Installed" tab after opening the "Manage NuGet packages for Solution" dialog in Visual Studio. Manually removing Dianoga from packages.config clears the error. We've tried uninstalling/reinstalling, and reverting back to 3.1.1 from 4.0, and the issue persists. |
It sounds like perhaps an issue with one of the files in the nupkg - probably in the dianoga tools folder - may have a character modern NuGet doesn't like (ref: https://help.octopusdeploy.com/discussions/problems/39033-part-uri-is-not-valid-per-rules-defined-in-the-open-packaging-conventions-specification) |
This should be resolved with https://github.com/kamsar/Dianoga/releases/tag/5.0.0-beta.1 can you retest and provide feedback? |
Hi, currently we do go with a different solution so I cannot validate anymore :( |
Hi,
I cannot build our solution once I have updated dianoga plugin from version 3.1.1 to version 4.0.0.
Actually I need the update because of the temp files bug so I have updated just the version of the package:
in .cspoj file I do have:
in package config there is:
<package id="Dianoga" version="4.0.0" targetFramework="net471" />
and once I build the solution I do have an error:
Thx for any tips what can be wrong,
Roman
The text was updated successfully, but these errors were encountered: