We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
These projects below Paramore.Brighter.MsSql.EntityFrameworkCore Paramore.Brighter.ServiceActivator.Extensions.HealthCheck
Can't be consumed from .net472 because they don't target .netstandard2.0
For this specific case would be overkill to create a repo to reproduce the issue I'm going to submit a Pull-Request to improve the compatibility
https://github.com/BrighterCommand/Brighter/blob/master/src/Paramore.Brighter.MsSql.EntityFrameworkCore/Paramore.Brighter.MsSql.EntityFrameworkCore.csproj#L6 https://github.com/BrighterCommand/Brighter/blob/master/src/Paramore.Brighter.ServiceActivator.Extensions.HealthChecks/Paramore.Brighter.ServiceActivator.Extensions.HealthChecks.csproj#L4
The text was updated successfully, but these errors were encountered:
ccae7e3
No branches or pull requests
Describe the bug
These projects below
Paramore.Brighter.MsSql.EntityFrameworkCore
Paramore.Brighter.ServiceActivator.Extensions.HealthCheck
Can't be consumed from .net472 because they don't target .netstandard2.0
To Reproduce
For this specific case would be overkill to create a repo to reproduce the issue
I'm going to submit a Pull-Request to improve the compatibility
Exceptions (if any)
Further technical details
https://github.com/BrighterCommand/Brighter/blob/master/src/Paramore.Brighter.MsSql.EntityFrameworkCore/Paramore.Brighter.MsSql.EntityFrameworkCore.csproj#L6
https://github.com/BrighterCommand/Brighter/blob/master/src/Paramore.Brighter.ServiceActivator.Extensions.HealthChecks/Paramore.Brighter.ServiceActivator.Extensions.HealthChecks.csproj#L4
The text was updated successfully, but these errors were encountered: