Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Now that you've confirmed that your one-liner fake-nuget is launched under correct account, please verify that:</p> <ul> <li>the 'user profile' is loaded for the app (TBO, I dont remember how, but it's late;) )</li> <li>%APPDATA%\NuGet\NuGet.Config points where it should (related, easy to check)</li> </ul> <p>It might happen that your child process is started with correct credentials, but <strong>without</strong> the user profile information. It is sometimes done to speed up the startup and to limit the process' interaction with user things like desktop layout, etc.</p> <p>I imagine that if somehow the user-profile was skipped, then the %APPDATA% might point not where you have put the nuget's config.</p> <p>I've often see services and workers use the</p> <ul> <li>Windows\System32\config\systemprofile</li> <li>Windows\SysWOW64..uhforgotthepart..\config\systemprofile</li> </ul> <p>paths as their temporary homedirs. In such case, the APPDATA of your process would point there, and lookup for nuget config would fail.</p> <p>Unfortunatelly, I don't know/remember how to force/skip the load-user-profile thing at the <code>ProcessStartInfo</code> level, but I roughly remember that <code>ShellExecute</code> suggested by BlackICE did load the profile, so it should have worked.. Still, be sure to check the APPDATA env variable, it might be it for some other reason.</p> <p>edit: --<br> Sorry for being so chaotic. I've solved a completely different problem (but in the same problem domain) with builds and nuget's package restore, but I hardly can collect bits from memory. My goals were different: I wanted to prevent NuGet from reaching to internet and remote servers and to use only the local cache. So, almost the opposite of what you want. But all boiled down to NuGet not getting the config files. I couldn't "switch on" the profile-loading due to a certain setup of the CI server, so I solved it by putting the nuget config into appdata in syswow64\?\systemprofile on all of the related worker nodes (or system32\config\sysprofile on 32bit machines).</p>
 

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