search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
258 stars 124 forks source link

VS2017 Community csproj doesn't like wildcards #1035

Closed moraleslos closed 7 years ago

moraleslos commented 7 years ago

I'm converting one of my asp.net core projects from VS2015 that uses project.json to VS2017 community that converts it to csproj. This project uses openiddict (and related libs). My csproj file contains this:

    <PackageReference Include="OpenIddict" Version="1.0.0-*" />
    <PackageReference Include="OpenIddict.EntityFrameworkCore" Version="1.0.0-*" />
    <PackageReference Include="OpenIddict.Mvc" Version="1.0.0-*" />
    <PackageReference Include="AspNet.Security.OAuth.Validation" Version="1.0.0-*" />

When building the above I get the following errors: Unable to resolve 'OpenIddict.Mvc(>=1.0.0)' for '.NETCoreApp,Version=v1.1' Same for the other 3 packages with wildcards. When I explicitly set the version numbers for those, it builds ok:

<PackageReference Include="OpenIddict" Version="1.0.0-beta2-0614" />
<PackageReference Include="OpenIddict.EntityFrameworkCore" Version="1.0.0-beta2-0614" />
<PackageReference Include="OpenIddict.Mvc" Version="1.0.0-beta2-0614" />
<PackageReference Include="AspNet.Security.OAuth.Validation" Version="1.0.0" />

Is there a bug when using wildcards in csproj files?

Attached is the VS2017 I'm using image

mlorbetske commented 7 years ago

This issue was moved to NuGet/Home#5537