Skip to content
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 Packager fails with Unrecognized root element in Core Properties part. Line 2, position 2. #2369

Closed
markanewman opened this issue Aug 30, 2016 · 1 comment
Assignees

Comments

@markanewman
Copy link

I don't know if this has a better home, but the version of NuGet deployed to the hosted build servers (C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.104.1\agent\worker\tools\NuGet.exe) seems to suffer from a new-ish issue in the exe.

If I get the latest version of nuget.exe and check it into my repo and set the Advanced | Path to NuGet.exe option to $(build.sourcesDirectory)\nuget.exe, the problem is resolved.

@zjrunner
Copy link
Member

zjrunner commented Oct 7, 2016

We've stopped using the in-agent nuget.exe at this point as it led to complications with update (which agents were you using vs which tasks were you using). The newest (around 0.2.19) has a toggle for you to choose a built-in version of nuget or your custom version. 3.3 is still the default for now and is the same one you mentioned as installed on agents, but 3.5 is also an option. Once we have a deprecation flow in tasks we'll be moving to 3.5 as the default value. At this time we do not plan to update or remove the version on-agent as we do not know who has a legacy custom task dependency here.

@zjrunner zjrunner closed this as completed Oct 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants