Note that there are some explanatory texts on larger screens.

plurals
  1. PONuGet for solution included in TFS Build
    primarykey
    data
    text
    <p>I am having problems with NuGet: it's actually driving me crazy! I am trying to make a TFS build run for a solution that includes nuget.exe. I don't have any issues running it from Visual Studio on my local workstation, but when I queue a new build in the TFS server, the build fails with these very known errors:</p> <blockquote> <p>D:\&lt;...SolutionPath...>.nuget\nuget.targets (88): Package restore is disabled by default. To give consent, open the Visual Studio Options dialog, click on Package Manager node and check 'Allow NuGet to download missing packages during build.' You can also give consent by setting the environment variable 'EnableNuGetPackageRestore' to 'true'.</p> <p>D:\&lt;...SolutionPath...>.nuget\nuget.targets (88): The command ""D:\&lt;...SolutionPath...>.nuget\nuget.exe" install "D:\&lt;...SolutionPath...>\packages.config" -source "" -RequireConsent -solutionDir "D:\&lt;...SolutionPath...>\ "" exited with code 1.</p> </blockquote> <p>The problem is: I already set the <strong>EnableNuGetPackageRestore</strong> to <em>true</em> in the TFS Build server, but it's still throwing the same error. I also tried running nuget.exe with the same parameters FROM a cmd windows in the same TFS server and I don't have any issues.</p> <p>BTW, this is the content of my NuGet.config:</p> <pre><code>&lt;configuration&gt; &lt;solution&gt; &lt;add key="disableSourceControlIntegration" value="true" /&gt; &lt;/solution&gt; &lt;packageRestore&gt; &lt;add key="enabled" value="true" /&gt; &lt;/packageRestore&gt; &lt;/configuration&gt; </code></pre> <p>Any ideas?</p> <p>Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload