{"id":250623,"date":"2024-09-17T03:00:19","date_gmt":"2024-09-17T10:00:19","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=250623"},"modified":"2025-08-22T07:40:46","modified_gmt":"2025-08-22T14:40:46","slug":"how-to-run-net-apps-natively-on-arm64-devices","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/how-to-run-net-apps-natively-on-arm64-devices\/","title":{"rendered":"How to run .NET Framework apps natively on Arm64 devices"},"content":{"rendered":"

Are you developing .NET Framework applications for Arm-based processors? Do you want to take advantage of the performance and power efficiency of running your apps natively on Arm64 devices? If so, you’ll be happy to hear that Visual Studio 2022 17.11 has a new feature that makes it easier than ever to do just that.<\/p>\n

\"Mobile<\/p>\n

Visual Studio 2022 natively supports building and debugging Arm64 apps on Arm-based processors. However, if you build your app with the AnyCPU setting, which is the default for most .NET Framework projects, your app will run on an Arm64 device using x64 emulation. While this may seem counterintuitive, this approach allowed many .NET Framework apps with x64 dependencies to work reliably under emulation without requiring additional build or dependency changes.<\/p>\n

Unfortunately, under these conditions, it means your app won’t <\/a>benefit from the native capabilities of the Arm64 <\/a>CPU and may suffer from reduced performance and increased battery consumption.<\/p>\n

To solve this problem, the Windows 24H2 update<\/a> introduces a new setting for your app manifest files. This setting allows you to specify a list of supported architectures (currently amd64 or arm64) for your app, indicating that it should run natively on those platforms. For example, if you include arm64 in the list, your app will run using the Arm64 <\/a>CLR on Arm64 devices when supported, even if it was built with the AnyCPU setting.<\/p>\n

How to use the setting in Visual Studio 2022<\/h2>\n

To use the new setting in Visual Studio 2022, you need to do the following steps:<\/p>\n

    \n
  1. Make sure you have the Windows 24H2<\/strong><\/a> update installed on your development machine and your target device.<\/li>\n
  2. Open your .NET Framework project in Visual Studio 2022 and right-click on your project in Solution Explorer and select Properties<\/strong>.<\/li>\n
  3. <\/a> In the Build<\/strong> area confirm that the AnyCPU <\/strong>configuration is enabled and that the Prefer 32-bit<\/strong> option is unselected.<\/li>\n
  4. Select the new Prefer native ARM64<\/strong> option.<\/li>\n
  5. Save <\/strong>and rebuild your project.<\/li>\n
  6. Deploy your app<\/strong> to your Arm64 device and run it. You can also debug it using Visual Studio 2022, which will automatically detect the correct architecture and launch the debugger accordingly.<\/li>\n<\/ol>\n

    \"A<\/p>\n

    Enjoy the benefits of native Arm64 apps<\/h2>\n

    By using the new setting in Visual Studio 2022, you can easily run and debug your .NET Framework apps natively on Arm64 devices, without changing your code or your build configuration. This will help you improve the performance, reliability, and battery life of your apps, and give your users a better experience.<\/p>\n

    We hope you enjoy this new feature and find it useful for your development scenarios. As always, we appreciate your> feedback and suggestions, which help us make Visual Studio better for you. Please let us know what you think by leaving a comment below, or by using the Report a Problem tool<\/a> in Visual Studio. Thank you for choosing Visual Studio 2022!<\/p>\n","protected":false},"excerpt":{"rendered":"

    Are you developing .NET Framework applications for Arm-based processors? Do you want to take advantage of the performance and power efficiency of running your apps natively on Arm64 devices? If so, you’ll be happy to hear that Visual Studio 2022 17.11 has a new feature that makes it easier than ever to do just that. […]<\/p>\n","protected":false},"author":1017,"featured_media":250626,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[6868],"tags":[237,6932,6852],"class_list":["post-250623","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-performance","tag-net","tag-32-bit","tag-arm64"],"acf":[],"blog_post_summary":"

    Are you developing .NET Framework applications for Arm-based processors? Do you want to take advantage of the performance and power efficiency of running your apps natively on Arm64 devices? If so, you’ll be happy to hear that Visual Studio 2022 17.11 has a new feature that makes it easier than ever to do just that. […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/250623","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/1017"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=250623"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/250623\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/250626"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=250623"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=250623"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=250623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}