NuGet Package ID Validator
Validate NuGet package identifiers against official NuGet Gallery naming conventions, dot-notation rules, and reserved namespace restrictions.
NuGet Naming Best Practices
1. Dot Separators
Identifiers must use alphanumeric characters and dot separators (.). Avoid consecutive dots, spaces, or illegal symbols.
2. Namespace Reservation
Prefixes like Microsoft.* are strictly reserved for official Microsoft publishers and require owner verification on nuget.org.
NuGet Package ID Validator features
- Available tool controls: Add ID.
- Input and option fields: Target Package ID:, Validation Profile:, Batch Test Identifiers:.
Using NuGet Package ID Validator in a development workflow
A validator can narrow down why a sample fails a syntax or rule check. Start with the complete input, inspect the first reported issue, and correct the source rather than only hiding the message. A pass means the checked rules were satisfied; it does not confirm business logic, compatibility, or security unless those checks are explicitly included.
Check the project’s versioning rules
- Check the project manifest and lockfile together before relying on a version or range result.
- Pay attention to these page fields: Target Package ID:, Validation Profile:, Batch Test Identifiers:. Confirm which fields are inputs, options, or output areas before processing.
- The page exposes these relevant actions: Add ID. Choose only the action that matches the result you need.
- A version comparison does not install or test a package. Review release notes and run the project’s checks before upgrading.
Confirm compatibility in the target project
Version ranges depend on package-manager semantics and project lockfiles. Compare the result with the package manager and registry used by the project.