-
Notifications
You must be signed in to change notification settings - Fork 23
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
The .NET binary size is too large #109
Comments
- optimize the JSON serializer with generated code - remove part of warning for trim unused code - optimize binary load time Resolve part of #109 Signed-off-by: Junjie Gao <[email protected]>
Here is the latest status of .NET 8 AOT feature support |
Hi @JeyJeyGao the work we have planned for now for AOT support in the Azure SDK's is mostly complete. If any of the warnings you have listed here are still impacting you, would you mind opening an issue in our repo - https://github.com/Azure/azure-sdk-for-net |
Hi @m-redding , thank you for sharing the good news! Will Azure.Core and Azure.Security.KeyVault be publishing new versions to include the update? |
Azure/azure-sdk-for-net#40892 The warning message in keyvault library has been fixed but didn't release. |
Azure/azure-sdk-for-net#40892 (comment) Warnings have been almost fixed. Waiting for release. |
Resolved in #156 |
The .NET version plugin binary size is over 60 MB. We need to reduce the size by using trimming unused code feature of .NET, however, it will trigger many warnings:
Here is a related issue in azure-sdk-for-dotnet repository
The text was updated successfully, but these errors were encountered: