-
Notifications
You must be signed in to change notification settings - Fork 104
Use a version wildcard for MEL dependency #133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1.4.0 Release
2.0.0 Release
2.0.1 Release
2.0.2 Release
Thanks! Let's give this a try 👍 I've re-targeted it to |
|
||
<ItemGroup Condition=" '$(TargetFramework)' == 'net461' or '$(TargetFramework)' == 'netstandard2.0' "> | ||
<PackageReference Include="Microsoft.Extensions.Logging" Version="2.0.0" /> | ||
<PackageReference Include="Microsoft.Extensions.Logging" Version="2.*" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note that this wont effect the resulting package. on each build the resultant nuget will have the current release version of Microsoft.Extensions.Logging hard coded as a package dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Argh, thanks Simon - lost track of this particular footgun :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only remember due to my missing foot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😂
Added floating version for PackageReference Microsoft.Extensions.Logging to 2.*