Open v-luzh opened 5 months ago
@v-luzh
Can you please help us figure out when this regressed.
Before modifying the settings, the machine-wide feed shows up in a different section of this settings dialog
Unchecking the feed results in this being added to the user-wide config:
<disabledPackageSources>
<add key="Microsoft Visual Studio Offline Packages" value="true" />
</disabledPackageSources>
Now the feed is no longer considered machine-wide:
@v-luzh
Can you please help us figure out when this regressed.
- Please try 17.7 and 17.8
Hi @nkolev92, it reproes on both D17.7\34003.232 with implicit NuGet Client 6.7.0.127 and D17.8\34309.116 with implicit NuGet Client 6.8.0.131.
Turns out guess was incorrect.
Can you try 17.0 and 17.5 as well.
Thanks!
Hi @nkolev92, it doesn't repro on D17.0\31903.59 with implicit NuGet Client 6.0.0.275, but reproes on D17.5\33414.496 with implicit NuGet Client 6.5.0.154.
And we found if the offline source is still considered as machine-wide source (listed under the 'Machine-wide package sources' list) after the first-disabling in step5, the bug will not repro. If the offline source is no longer considered as machine-wide source (considered as package source instead) after the first-disabling in step5, the bug will repro.
@v-luzh Hi can you try again and look at the configuration files before and after disabling the source?
You can look at the configuration files in Options -> NuGet Package Manager -> Configuration files and double click on them so they open in your VS editor.
Hi @martinrrm, here is the configuration files comparison:
It still reproes on VS Main\35222.175 + NuGet Client Dev\6.12.0.82.
NuGet Product Used
Visual Studio Package Management UI
Product Version
Dev\6.11.0.49
Worked before?
It is a regression since it doesn’t repro on D16.11\34601.136, but reproes on D17.9\34601.282.
Impact
It bothers me. A fix would be nice
Repro Steps & Context
Repro Steps:
Expected Result:
The offline package source should be enabled again.
Actual Result:
The offline package source cannot be enabled again as recorded below.
Notes:
Verbose Logs
No response