-
Notifications
You must be signed in to change notification settings - Fork 261
Insights: NuGet/Home
Overview
-
0 Active pull requests
-
- 0 Merged pull requests
- 0 Open pull requests
- 3 Closed issues
- 2 New issues
There hasn’t been any commit activity on NuGet/Home in the last 3 days.
Want to help out?
3 Issues closed by 2 people
-
Stricter validation of Xml elements inside of NuGet.config files
#14303 closed
May 16, 2025 -
Block and remove code for unused restore implementations such as `Standalone`.
#14184 closed
May 16, 2025 -
Can't install NuGet packages even after setting source URL and using VPN
#14296 closed
May 16, 2025
2 Issues opened by 2 people
-
add compatible frameworks to nuspec & protocol
#14321 opened
May 17, 2025 -
Solution 'slnx' format seems to be unsupported
#14320 opened
May 17, 2025
7 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
NRE when a feed is not correct
#14299 commented on
May 16, 2025 • 0 new comments -
Lint NuGet.config files for common errors, typos, and syntax.
#13469 commented on
May 16, 2025 • 0 new comments -
Package lock files is generated with different EOL based on OS
#14314 commented on
May 16, 2025 • 0 new comments -
support nuget client golang SDK
#14315 commented on
May 16, 2025 • 0 new comments -
dotnet commands access default NuGet.Config even when --configfile is specified
#14316 commented on
May 16, 2025 • 0 new comments -
[Bug Bash] Default package format will not be updated to user-selection in Unified Settings until restarting VS and creating another project
#14302 commented on
May 16, 2025 • 0 new comments -
`dotnet add package` does not work with `Directory.Package.props`
#14317 commented on
May 17, 2025 • 0 new comments