tool · inferred from evidence
nuget
The underlying command-line tool referenced in the error message of NuGetCommand@2.
- Dotnet Error in 4.11.0 when using ChromeDriverService.CreateDefaultService()
Upgrade to Selenium 4.12 or newer. In 4.11 the .NET Service constructor treated a path without a trailing slash as a file instead of a directory, which broke ChromeDriverService.CreateDefaultService(); that was fixed for 4.12.
- Telegram.Bot 22.5.0 - webhook Update is null
Workaround for null webhook Update on Telegram.Bot 22.5.0: add the `Telegram.Bot.AspNetCore` NuGet package so you can call `ConfigureTelegramBotMvc()` with v22.5. The maintainer also notes a null Update usually means a problem elsewhere in
- Dependabot updates are failing due to missing .NET SDK
Dependabot nuget/dotnet updates failing with .NET SDK installation errors: fixed Dependabot-side via #9228 and #9374, and confirmed working by multiple reporters. No action needed on your repo; re-run the failed update.
- Custom nuget-feed no longer used, breaking package updates
Teaches how to custom nuget-feed no longer used, breaking package updates. Based on a real issue report and its verified fix.
- GrowthBook C# Blazor: EvalFeature always returns defaultValue source
In a Blazor app, GrowthBook EvalFeature ignored rules and always returned source defaultValue. A bug in the C# SDK, fixed on NuGet as v1.0.5; upgrade the package.
- NuGetCommand@2 regression: the nuget command failed with exit code(null)
Pin NuGetCommand@2 back to 2.238.1 as an immediate fix: builds go green again. The task team fixed the regression in 2.253.0, which became the new default; the reporter confirmed 2.253.0 works.