You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
Performance has been a key .NET feature. The existing options for optimizing published applications work well for most scenarios that .NET targets today.
Some of you asked us to consider adding native AOT compilation option with distinctly different characteristics. The distinctly different characteristics of native AOT come with tradeoffs such as lower compatibility that are explained in detail in .NET Runtime Form Factors. We’ve created a survey to help us better understand the native AOT use cases.
We would appreciate your feedback so we can work on creating the right plans for future. If you don’t supply contact details, then responses will be anonymous.
Results from the survey have been posted - dotnet/runtime#41522. We are now in the process of following up with people that provided their contact information and have some additional follow-up questions.
Performance has been a key .NET feature. The existing options for optimizing published applications work well for most scenarios that .NET targets today.
Some of you asked us to consider adding native AOT compilation option with distinctly different characteristics. The distinctly different characteristics of native AOT come with tradeoffs such as lower compatibility that are explained in detail in .NET Runtime Form Factors. We’ve created a survey to help us better understand the native AOT use cases.
We would appreciate your feedback so we can work on creating the right plans for future. If you don’t supply contact details, then responses will be anonymous.
Survey: https://www.surveymonkey.com/r/SQCYB2C
Thank you for your time!
The text was updated successfully, but these errors were encountered: