-
Notifications
You must be signed in to change notification settings - Fork 258
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
Nuget Pack throws System.Xml.XmlException: Unrecognized root element in Core Properties part. Line 2, position 2. #1921
Comments
I get the exact same error! This happens only in v3.3.0, 3.2.1.10581 is fine! |
Can you please share a full repro? |
As we plan to rewrite this part of the pack code, assigning this to @emgarten. A repro will help us build a test making sure this gets resolved for your particular scenario. |
I would like to help out with a repo since it's internal code from the company I can't promise anytrhing since I have to get approval frist. I will test new versions against this bug though and report back. |
@Tak0r the problem is that we don't have a repro for this issue, and we have extensive tests for packing. So it will be a pretty wild goose chase if we can't find a sample that fails. Are you able to perhaps distill a small example that does not include any proprietary code from your company? |
I will try to do so tomorrow if I find the time for it. |
Thanks! |
@yishaigalatzer I have uploaded a repo with a project failing to pack. I was in the same boat as @Tak0r with proprietary code, however I made a stripped down version with all code removed and just a dummy class file added. It still does not pack. I have uploaded that stripped down version to this public repo: https://github.com/Luzenna/nugetbug Please let me know if you require any more information. |
Can you add a readme with exact repro steps? Sent from my Windows Phone From: Luzennamailto:[email protected] I was in the same boat as @Tak0rhttps://github.com/Tak0r with proprietary code, however I made a stripped down version with all code removed and just a dummy class file added. It still does not pack. I have uploaded that stripped down version to this public repo: https://github.com/Luzenna/nugetbug Please let me know if you require any more infomtion. — |
@yishaigalatzer |
For the sake of completeness can you type the exact command you are using? Sent from my Windows Phone From: Luzennamailto:[email protected] @yishaigalatzerhttps://github.com/yishaigalatzer — |
Well, I did write it in my initial post eight days ago, but here it is again:
|
Sorry missed that. Thanks for clarifying |
OK, Got a repro and looking into it. Note that you accidentally left a link to your appveyor ci feed that of course I cannot connect to. Fortunately taking it off makes the repro work. Can you please take it out for the sake of the developer who is going to try and fix it |
@yishaigalatzer Sorry 'bout that. Should be OK now. |
Thanks! Looking into it, it seems to be related to a change we indeed made between 3.2.1 and 3.3 (CC @xavierdecoster) The root cause of the problem is that the package https://www.nuget.org/packages/structuremap/3.1.6.186 is not a compliant OPC package, and hence the OPC package APIs are throwing an exception when trying to traverse the files in it. So this is in a gray area of unintentional breaking change where we used to consume it through different call paths in system.io.packaging that do not expose the issue in this particular package. I'm going to see if we can come up with a quick solution, longish term (starting work on this shortly) the plan is to completely remove the dependency on system.io.packaging and a manifest definition for the nuspec file, and thus not hitting any such issues in 3.4 (or 3.5 at the latest). |
…ncountering non-compliant OPC packages NuGet/Home#1921
@toddm I suspect this could be another item that got fixed with pack being ported from nuget2 to nuget.client repos |
Yes, this works fine with the latest build: http://myget.org/gallery/nugetbuild. Closing the issue. |
When using Nuget Pack with version 3.3.0 it throws the following error: System.Xml.XmlException: Unrecognized root element in Core Properties part. Line 2, position 2.
This does NOT happen when using the nuget command line version 3.2.0.
Here is the full console log:
The text was updated successfully, but these errors were encountered: