The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →NU1015 means .NET 10 found a PackageReference with no version. If the project uses Central Package Management (CPM), a versionless reference may be intentional: check that CPM is enabled and applies to that reference before changing it. If the project does not use CPM for the dependency, add an explicit version.
Why .NET 10 reports NU1015
Starting with .NET 10, a PackageReference without a version produces error NU1015. Previously, the missing lower bound produced warning NU1604 and could allow restore to select the lowest available version, a behavior Microsoft says developers rarely want. The official error text is: “The following PackageReference item(s) do not have a version specified: PackageA.” Microsoft documents the change and its compatibility options.
As an Amazon Associate I earn from qualifying purchases.
Find the versionless PackageReference
The item may be in the project file or an imported MSBuild file, such as Directory.Build.props. Search the project and relevant imported configuration for the package named in the error. Then establish whether that dependency is meant to have a version in the project or receive one centrally.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the fix that matches your versioning model
If the project does not use Central Package Management for this dependency
Add the intended version to the reference. For example:
<PackageReference Include="Some.Package" Version="1.2.3" />Use the version appropriate to the project; the example is illustrative, not a recommendation for a particular package.
If the project uses Central Package Management
CPM keeps package versions in central configuration, so a versionless PackageReference can be correct. Do not add an arbitrary local version before checking the solution’s policy: first investigate why CPM is disabled or not applied to this project or reference. Microsoft’s NU1015 reference describes the error; the .NET 10 compatibility note explains the behavioral change.
Rank #2
When to use the documented alternatives
Deliberately selecting the lowest package version
If lowest-version selection is intentional, Microsoft’s compatibility note recommends setting Version="0.0.0". It says this results in warning NU1603 instead of the earlier NU1604. This is a specific alternative behavior, not the general fix for a missing version.
Reverting to the previous warning behavior
The compatibility note also documents setting SdkAnalysisLevel to 9.0.300 or lower to restore the previous warning behavior. This setting affects all features gated by SdkAnalysisLevel, not just NU1015. Prefer correcting the missing version or CPM configuration unless that broader change is intended.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
