-
Notifications
You must be signed in to change notification settings - Fork 816
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
Trimming/AOT friendliness in 6.0 #3300
Comments
roji
added a commit
to roji/Npgsql
that referenced
this issue
Feb 5, 2021
Just specify them explicitly - simpler and more linker-friendly. Part of npgsql#3300
roji
added a commit
that referenced
this issue
Feb 7, 2021
Just specify them explicitly - simpler and more linker-friendly. Part of #3300
3 tasks
roji
added a commit
to roji/Npgsql
that referenced
this issue
Feb 8, 2021
roji
added a commit
that referenced
this issue
Feb 8, 2021
This was referenced Jun 6, 2021
roji
added a commit
that referenced
this issue
Jun 11, 2021
4 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a general "epic" tracking issue for making Npgsql more compatible with trimming/AOT. A lot of this is about getting rid of runtime code generation (e.g. via source generators), general reflection use, etc. See also dotnet/efcore#21894 for some general comments on what that means and what needs to be done.
The text was updated successfully, but these errors were encountered: