-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
Invalid entry in NuGet [Content_Types].xml #309
Comments
when i copied the latest version of bundlerminifier.core.2.8.391 to nuget.server 3.1.2 receiving same error-part uri cannot start with two forward slashes. Is there any update on this issue. |
Any updates on this, the issues is also there with : microsoft.visualstudio.web.codegeneration.tools.2.0.4
This is the culprit with double slash '//': |
Product versions
EDIT: NuGet package explorer does not fail anymore, so I have removed it from this list. I will check newer versions of NuGet server soon too, but maybe this whole issue is now unecessary.
Description
The
[Content_Types].xml
file inbundlerminifier.core.2.6.362.nupkg
contains the line:<Override PartName="//prefercliruntime" ContentType="application/octet" />
which causes mentioned NuGet products to fail. The error states that a part uri cannot start with two forward slashes.
Steps to recreate
Install NuGet Server: (Instructions: https://docs.microsoft.com/en-us/nuget/hosting-packages/nuget-server)
Try to publish bundlerminifier.core.2.6.362.nupkg, you will get an error.
Current behavior
The NuGet file is incompatible (presumably invalid).
Screenshot here
Expected behavior
It should work.
Workaround
I have unpacked the nuget file and removed the line, and it works!
Assumed cause
I believe the problem is line 20 at:
BundlerMinifier.Core.csproj
<Content Include="prefercliruntime" Pack="true" PackagePath="\prefercliruntime" />
Maybe the PackagePath needs to be
"prefercliruntime"
(without the trailing slash?)Maybe
"/prefercliruntime"
with a forward slash?Is this line even needed at all anymore?
The text was updated successfully, but these errors were encountered: