nuget.exe fail: Missing required property 'OutputPath' for project type 'PackageReference'How do I sync the...
What language shall they sing in?
Potential client has a problematic employee I can't work with
Cat is tipping over bed-side lamps during the night
How to not let the Identify spell spoil everything?
Why avoid shared user accounts?
How do you voice extended chords?
What is function of "чего" in this sentence?
Does it take energy to move something in a circle?
Is there a verb that means to inject with poison?
Sprint is 2 week and 40-stories
Why is a temp table a more efficient solution to the Halloween Problem than an eager spool?
Separate environment for personal and development use under macOS
Which RAF squadrons and aircraft types took part in the bombing of Berlin on the 25th of August 1940?
Is a new boolean field better than null reference when a value can be meaningfully absent?
Why do neural networks need so many training examples to perform?
How can the probability of a fumble decrease linearly with more dice?
How does Leonard in "Memento" remember reading and writing?
Eww, those bytes are gross
Best way to strengthen a wheel?
Hosting images in SFMC - is it a good idea?
Do authors have to be politically correct in article-writing?
Is there an expiration time for free invocations?
microtype error with lualatex: "attempt to call field warning a nil value"
Does the ditching switch allow an A320 to float indefinitely?
nuget.exe fail: Missing required property 'OutputPath' for project type 'PackageReference'
How do I sync the Solution Explorer with the current File in Visual Studio?“ant” is not recognized as command in WindowsHow can I get ConEmu, Far Manager and the VS Developer Command Prompt to play nice together?How to build Unity3D-Projects for Holo-Lens using Jenkins and MsBuild on WindowsWindows 10 1709 in combination with C# project targetting .NET 4.7.1WSL-bash-launched Windows apps exclusively lock filesWhy doesn't the exe file run while the solution itself in Visual Studio could run smoothly?Python says is 216 bitsSAP NW RFC SDK support for Visual Studio 2017Getting an error trying to find libfftw3-3.dll after adding the containing folder to “Additional Dependencies” in VS2017
(Using nuget.exe version 4.9.2 and Visual Studio 2017 Community Edition)
I'm stumped on a nuget.exe restore issue. I'm using Jenkins to build pushed sources. I had a solution with a single project in it, Roadmap, and that built fine, including using
nuget.exe restore "test.sln"
to restore the nuget packages. My Jenkins builds always start with an empty directory.
Now I have a second project. It uses several of the same nuget packages. But when Jenkins runs the same nuget.exe command on the .sln file, I get this error:
C:Jenkinsworkspacetest>nuget restore "test.sln"
MSBuild auto-detection: using msbuild version '12.0' from 'C:Program Files (x86
)MSBuild12.0binamd64'.
All packages listed in packages.config are already installed.
Invalid restore input. Missing required property 'OutputPath' for project type '
PackageReference'. Input files: C:JenkinsworkspacetestRoadtripRoadtrip.csproj.
I do see the OutputPath set in both of the .csproj files in my solution. But the error message isn't completely misleading. Roadmap.csproj, the original, has lines like these for the nuget packages:
<ItemGroup>
<Reference Include="CommonServiceLocator, Version=2.0.4.0, Culture=neutral, PublicKeyToken=489b6accfaf20ef0, processorArchitecture=MSIL">
<HintPath>..packagesCommonServiceLocator.2.0.4libnet45CommonServiceLocator.dll</HintPath>
</Reference>
...
In Roadtrip.csproj, the new one, the equivalent section holds
<ItemGroup>
<PackageReference Include="CommonServiceLocator">
<Version>2.0.4</Version>
</PackageReference>
...
This is the case whether I use the solution nuget manager to add packages to one or both projects, or use each project nuget manager to add their packages.
From what I've seen online, Roadtrip that looks fine. I'm not sure why it would differ from Roadmap. From within Visual Studio, the references are found and both apps run, with the correct DLLs sitting in the debug and release directories. Additionally, when I run the nuget.exe line on my laptop, the packages are retrieved.
It's only when I run it on the remote Jenkins server that it fails. I've tried looking for the differences in the configurations, but they're not jumping out, what I can find that's relevant matches on both. I'm hoping there's someone knowledgeable here who knows the specifics of why I'd see that error message.
I appreciate any assistance.
Update: I was going to add this in the morning, and Scott mentioned doing so as well... I'm picking on Jenkins, but it's really the machine Jenkins is running on. I can open a cmd window on my laptop (not the MSVC cmd window), wipe out the solution packages directory and all obj/bin subdirectories, and nuget.exe restore test.sln
completes successfully. Doing the same on the machine with Jenkins fails as shown above... and used to work before I added the second project. The versions of nuget and Visual Studio are the same on both, the environment variables in the cmd windows are the same on both.
windows command-line jenkins visual-studio-2017
add a comment |
(Using nuget.exe version 4.9.2 and Visual Studio 2017 Community Edition)
I'm stumped on a nuget.exe restore issue. I'm using Jenkins to build pushed sources. I had a solution with a single project in it, Roadmap, and that built fine, including using
nuget.exe restore "test.sln"
to restore the nuget packages. My Jenkins builds always start with an empty directory.
Now I have a second project. It uses several of the same nuget packages. But when Jenkins runs the same nuget.exe command on the .sln file, I get this error:
C:Jenkinsworkspacetest>nuget restore "test.sln"
MSBuild auto-detection: using msbuild version '12.0' from 'C:Program Files (x86
)MSBuild12.0binamd64'.
All packages listed in packages.config are already installed.
Invalid restore input. Missing required property 'OutputPath' for project type '
PackageReference'. Input files: C:JenkinsworkspacetestRoadtripRoadtrip.csproj.
I do see the OutputPath set in both of the .csproj files in my solution. But the error message isn't completely misleading. Roadmap.csproj, the original, has lines like these for the nuget packages:
<ItemGroup>
<Reference Include="CommonServiceLocator, Version=2.0.4.0, Culture=neutral, PublicKeyToken=489b6accfaf20ef0, processorArchitecture=MSIL">
<HintPath>..packagesCommonServiceLocator.2.0.4libnet45CommonServiceLocator.dll</HintPath>
</Reference>
...
In Roadtrip.csproj, the new one, the equivalent section holds
<ItemGroup>
<PackageReference Include="CommonServiceLocator">
<Version>2.0.4</Version>
</PackageReference>
...
This is the case whether I use the solution nuget manager to add packages to one or both projects, or use each project nuget manager to add their packages.
From what I've seen online, Roadtrip that looks fine. I'm not sure why it would differ from Roadmap. From within Visual Studio, the references are found and both apps run, with the correct DLLs sitting in the debug and release directories. Additionally, when I run the nuget.exe line on my laptop, the packages are retrieved.
It's only when I run it on the remote Jenkins server that it fails. I've tried looking for the differences in the configurations, but they're not jumping out, what I can find that's relevant matches on both. I'm hoping there's someone knowledgeable here who knows the specifics of why I'd see that error message.
I appreciate any assistance.
Update: I was going to add this in the morning, and Scott mentioned doing so as well... I'm picking on Jenkins, but it's really the machine Jenkins is running on. I can open a cmd window on my laptop (not the MSVC cmd window), wipe out the solution packages directory and all obj/bin subdirectories, and nuget.exe restore test.sln
completes successfully. Doing the same on the machine with Jenkins fails as shown above... and used to work before I added the second project. The versions of nuget and Visual Studio are the same on both, the environment variables in the cmd windows are the same on both.
windows command-line jenkins visual-studio-2017
Can you clarify "It's only when I run it on the remote Jenkins server that it fails."? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 21 '18 at 1:37
Did you trynuget.exe update -self
?
– JB.
Feb 5 at 11:07
Hi JB... I did.
– trueskew
Feb 6 at 15:30
add a comment |
(Using nuget.exe version 4.9.2 and Visual Studio 2017 Community Edition)
I'm stumped on a nuget.exe restore issue. I'm using Jenkins to build pushed sources. I had a solution with a single project in it, Roadmap, and that built fine, including using
nuget.exe restore "test.sln"
to restore the nuget packages. My Jenkins builds always start with an empty directory.
Now I have a second project. It uses several of the same nuget packages. But when Jenkins runs the same nuget.exe command on the .sln file, I get this error:
C:Jenkinsworkspacetest>nuget restore "test.sln"
MSBuild auto-detection: using msbuild version '12.0' from 'C:Program Files (x86
)MSBuild12.0binamd64'.
All packages listed in packages.config are already installed.
Invalid restore input. Missing required property 'OutputPath' for project type '
PackageReference'. Input files: C:JenkinsworkspacetestRoadtripRoadtrip.csproj.
I do see the OutputPath set in both of the .csproj files in my solution. But the error message isn't completely misleading. Roadmap.csproj, the original, has lines like these for the nuget packages:
<ItemGroup>
<Reference Include="CommonServiceLocator, Version=2.0.4.0, Culture=neutral, PublicKeyToken=489b6accfaf20ef0, processorArchitecture=MSIL">
<HintPath>..packagesCommonServiceLocator.2.0.4libnet45CommonServiceLocator.dll</HintPath>
</Reference>
...
In Roadtrip.csproj, the new one, the equivalent section holds
<ItemGroup>
<PackageReference Include="CommonServiceLocator">
<Version>2.0.4</Version>
</PackageReference>
...
This is the case whether I use the solution nuget manager to add packages to one or both projects, or use each project nuget manager to add their packages.
From what I've seen online, Roadtrip that looks fine. I'm not sure why it would differ from Roadmap. From within Visual Studio, the references are found and both apps run, with the correct DLLs sitting in the debug and release directories. Additionally, when I run the nuget.exe line on my laptop, the packages are retrieved.
It's only when I run it on the remote Jenkins server that it fails. I've tried looking for the differences in the configurations, but they're not jumping out, what I can find that's relevant matches on both. I'm hoping there's someone knowledgeable here who knows the specifics of why I'd see that error message.
I appreciate any assistance.
Update: I was going to add this in the morning, and Scott mentioned doing so as well... I'm picking on Jenkins, but it's really the machine Jenkins is running on. I can open a cmd window on my laptop (not the MSVC cmd window), wipe out the solution packages directory and all obj/bin subdirectories, and nuget.exe restore test.sln
completes successfully. Doing the same on the machine with Jenkins fails as shown above... and used to work before I added the second project. The versions of nuget and Visual Studio are the same on both, the environment variables in the cmd windows are the same on both.
windows command-line jenkins visual-studio-2017
(Using nuget.exe version 4.9.2 and Visual Studio 2017 Community Edition)
I'm stumped on a nuget.exe restore issue. I'm using Jenkins to build pushed sources. I had a solution with a single project in it, Roadmap, and that built fine, including using
nuget.exe restore "test.sln"
to restore the nuget packages. My Jenkins builds always start with an empty directory.
Now I have a second project. It uses several of the same nuget packages. But when Jenkins runs the same nuget.exe command on the .sln file, I get this error:
C:Jenkinsworkspacetest>nuget restore "test.sln"
MSBuild auto-detection: using msbuild version '12.0' from 'C:Program Files (x86
)MSBuild12.0binamd64'.
All packages listed in packages.config are already installed.
Invalid restore input. Missing required property 'OutputPath' for project type '
PackageReference'. Input files: C:JenkinsworkspacetestRoadtripRoadtrip.csproj.
I do see the OutputPath set in both of the .csproj files in my solution. But the error message isn't completely misleading. Roadmap.csproj, the original, has lines like these for the nuget packages:
<ItemGroup>
<Reference Include="CommonServiceLocator, Version=2.0.4.0, Culture=neutral, PublicKeyToken=489b6accfaf20ef0, processorArchitecture=MSIL">
<HintPath>..packagesCommonServiceLocator.2.0.4libnet45CommonServiceLocator.dll</HintPath>
</Reference>
...
In Roadtrip.csproj, the new one, the equivalent section holds
<ItemGroup>
<PackageReference Include="CommonServiceLocator">
<Version>2.0.4</Version>
</PackageReference>
...
This is the case whether I use the solution nuget manager to add packages to one or both projects, or use each project nuget manager to add their packages.
From what I've seen online, Roadtrip that looks fine. I'm not sure why it would differ from Roadmap. From within Visual Studio, the references are found and both apps run, with the correct DLLs sitting in the debug and release directories. Additionally, when I run the nuget.exe line on my laptop, the packages are retrieved.
It's only when I run it on the remote Jenkins server that it fails. I've tried looking for the differences in the configurations, but they're not jumping out, what I can find that's relevant matches on both. I'm hoping there's someone knowledgeable here who knows the specifics of why I'd see that error message.
I appreciate any assistance.
Update: I was going to add this in the morning, and Scott mentioned doing so as well... I'm picking on Jenkins, but it's really the machine Jenkins is running on. I can open a cmd window on my laptop (not the MSVC cmd window), wipe out the solution packages directory and all obj/bin subdirectories, and nuget.exe restore test.sln
completes successfully. Doing the same on the machine with Jenkins fails as shown above... and used to work before I added the second project. The versions of nuget and Visual Studio are the same on both, the environment variables in the cmd windows are the same on both.
windows command-line jenkins visual-studio-2017
windows command-line jenkins visual-studio-2017
edited Dec 21 '18 at 14:45
trueskew
asked Dec 21 '18 at 1:14
trueskewtrueskew
112
112
Can you clarify "It's only when I run it on the remote Jenkins server that it fails."? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 21 '18 at 1:37
Did you trynuget.exe update -self
?
– JB.
Feb 5 at 11:07
Hi JB... I did.
– trueskew
Feb 6 at 15:30
add a comment |
Can you clarify "It's only when I run it on the remote Jenkins server that it fails."? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 21 '18 at 1:37
Did you trynuget.exe update -self
?
– JB.
Feb 5 at 11:07
Hi JB... I did.
– trueskew
Feb 6 at 15:30
Can you clarify "It's only when I run it on the remote Jenkins server that it fails."? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 21 '18 at 1:37
Can you clarify "It's only when I run it on the remote Jenkins server that it fails."? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 21 '18 at 1:37
Did you try
nuget.exe update -self
?– JB.
Feb 5 at 11:07
Did you try
nuget.exe update -self
?– JB.
Feb 5 at 11:07
Hi JB... I did.
– trueskew
Feb 6 at 15:30
Hi JB... I did.
– trueskew
Feb 6 at 15:30
add a comment |
2 Answers
2
active
oldest
votes
My working answer is that the Visual Studio / nuget.exe versions I'm using do not support PackageReference in .csproj files. I've read that it should, but couldn't get past this issue. Once I modified my Roadmap project to use packages.config and modified my .csproj file to match the Roadmap file, the nuget restore command worked as expected.
add a comment |
I had the same issue while restoring locally, and it worked as expected. But when I tried and started my job on the Jenkins agent, I got the same issue with the nuget restore.
nuget restore pathToProjectMyProject.csproj
Invalid restore input. Missing required property 'OutputPath' for project type 'PackageReference'. Input files: MyProject.csproj
Where on my Jenkins Agent machine I had the same Nuget version as the Nuget version on my machine. And the same MSBuild as my MSBuild on my machine.
But the nuget restore command started another MSBuild version on my agent.
Specifying the MSBuildPath to the MSBuild version 15, helped in my case.
nuget restore pathToProjectMyProject.csproj -MSBuildPath "pathToMSBuildMSBuild15.0Bin"
Or you might try using -MSBuildVersion.
As far as I understand the PackageReference change works best with MSBuild version 15. Since it came with Visual Studio 2017, and at the same time MSBuild 15.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386488%2fnuget-exe-fail-missing-required-property-outputpath-for-project-type-package%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
My working answer is that the Visual Studio / nuget.exe versions I'm using do not support PackageReference in .csproj files. I've read that it should, but couldn't get past this issue. Once I modified my Roadmap project to use packages.config and modified my .csproj file to match the Roadmap file, the nuget restore command worked as expected.
add a comment |
My working answer is that the Visual Studio / nuget.exe versions I'm using do not support PackageReference in .csproj files. I've read that it should, but couldn't get past this issue. Once I modified my Roadmap project to use packages.config and modified my .csproj file to match the Roadmap file, the nuget restore command worked as expected.
add a comment |
My working answer is that the Visual Studio / nuget.exe versions I'm using do not support PackageReference in .csproj files. I've read that it should, but couldn't get past this issue. Once I modified my Roadmap project to use packages.config and modified my .csproj file to match the Roadmap file, the nuget restore command worked as expected.
My working answer is that the Visual Studio / nuget.exe versions I'm using do not support PackageReference in .csproj files. I've read that it should, but couldn't get past this issue. Once I modified my Roadmap project to use packages.config and modified my .csproj file to match the Roadmap file, the nuget restore command worked as expected.
answered Dec 31 '18 at 19:29
trueskewtrueskew
112
112
add a comment |
add a comment |
I had the same issue while restoring locally, and it worked as expected. But when I tried and started my job on the Jenkins agent, I got the same issue with the nuget restore.
nuget restore pathToProjectMyProject.csproj
Invalid restore input. Missing required property 'OutputPath' for project type 'PackageReference'. Input files: MyProject.csproj
Where on my Jenkins Agent machine I had the same Nuget version as the Nuget version on my machine. And the same MSBuild as my MSBuild on my machine.
But the nuget restore command started another MSBuild version on my agent.
Specifying the MSBuildPath to the MSBuild version 15, helped in my case.
nuget restore pathToProjectMyProject.csproj -MSBuildPath "pathToMSBuildMSBuild15.0Bin"
Or you might try using -MSBuildVersion.
As far as I understand the PackageReference change works best with MSBuild version 15. Since it came with Visual Studio 2017, and at the same time MSBuild 15.
New contributor
add a comment |
I had the same issue while restoring locally, and it worked as expected. But when I tried and started my job on the Jenkins agent, I got the same issue with the nuget restore.
nuget restore pathToProjectMyProject.csproj
Invalid restore input. Missing required property 'OutputPath' for project type 'PackageReference'. Input files: MyProject.csproj
Where on my Jenkins Agent machine I had the same Nuget version as the Nuget version on my machine. And the same MSBuild as my MSBuild on my machine.
But the nuget restore command started another MSBuild version on my agent.
Specifying the MSBuildPath to the MSBuild version 15, helped in my case.
nuget restore pathToProjectMyProject.csproj -MSBuildPath "pathToMSBuildMSBuild15.0Bin"
Or you might try using -MSBuildVersion.
As far as I understand the PackageReference change works best with MSBuild version 15. Since it came with Visual Studio 2017, and at the same time MSBuild 15.
New contributor
add a comment |
I had the same issue while restoring locally, and it worked as expected. But when I tried and started my job on the Jenkins agent, I got the same issue with the nuget restore.
nuget restore pathToProjectMyProject.csproj
Invalid restore input. Missing required property 'OutputPath' for project type 'PackageReference'. Input files: MyProject.csproj
Where on my Jenkins Agent machine I had the same Nuget version as the Nuget version on my machine. And the same MSBuild as my MSBuild on my machine.
But the nuget restore command started another MSBuild version on my agent.
Specifying the MSBuildPath to the MSBuild version 15, helped in my case.
nuget restore pathToProjectMyProject.csproj -MSBuildPath "pathToMSBuildMSBuild15.0Bin"
Or you might try using -MSBuildVersion.
As far as I understand the PackageReference change works best with MSBuild version 15. Since it came with Visual Studio 2017, and at the same time MSBuild 15.
New contributor
I had the same issue while restoring locally, and it worked as expected. But when I tried and started my job on the Jenkins agent, I got the same issue with the nuget restore.
nuget restore pathToProjectMyProject.csproj
Invalid restore input. Missing required property 'OutputPath' for project type 'PackageReference'. Input files: MyProject.csproj
Where on my Jenkins Agent machine I had the same Nuget version as the Nuget version on my machine. And the same MSBuild as my MSBuild on my machine.
But the nuget restore command started another MSBuild version on my agent.
Specifying the MSBuildPath to the MSBuild version 15, helped in my case.
nuget restore pathToProjectMyProject.csproj -MSBuildPath "pathToMSBuildMSBuild15.0Bin"
Or you might try using -MSBuildVersion.
As far as I understand the PackageReference change works best with MSBuild version 15. Since it came with Visual Studio 2017, and at the same time MSBuild 15.
New contributor
New contributor
answered 16 mins ago
MalenkoMalenko
11
11
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386488%2fnuget-exe-fail-missing-required-property-outputpath-for-project-type-package%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you clarify "It's only when I run it on the remote Jenkins server that it fails."? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 21 '18 at 1:37
Did you try
nuget.exe update -self
?– JB.
Feb 5 at 11:07
Hi JB... I did.
– trueskew
Feb 6 at 15:30