Change package ID?

[Pathoschild]

Consider changing the package ID in a future version to match the library name (from Pathoschild.Http.FluentClient to Pathoschild.FluentHttpClient).

[Pathoschild]

Background

FluentHttpClient is the top Google result for "FluentHttpClient", but it's way down the list in the Visual Studio package manager (which mainly searches the package ID):

It's near the top for "FluentClient" though, since that's in the ID (no idea why a package with 73 downloads is first):

Pros & cons

• Pros:
  • Less confusing when users search "FluentHttpClient".
  • ID is more logical and consistent going forward.
• Cons:
  • Resets downloads to zero, which decreases visibility.
  • Existing users need to uninstall the old package, and install the new one.

Ideally NuGet would support renaming a package, but that seems unlikely since they've closed all previous proposals to implement it. We might have package deprecation soon though.

[Huntk23]

Perhaps this is no longer a problem? When I search FluentHttpClient it is 3rd in my list.

[Pathoschild]

Yeah, and it doesn't seem like we'll ever have a good way to change NuGet package IDs, so I think we can close this.