Top Microsoft and third party NuGet packages support and work well on ARM64

[jamshedd]

Summary

The top packages developers use need to support ARM64 so when developers try to build new apps or port existing apps to run on ARM64 the packages they need work and they are not blocked.

Getting Microsoft owned NuGet packages to support ARM64 will be a first step towards unblocking the rest of the ecosystem for ARM64. Without a catalog of Microsoft packages that already work it will be hard to evangelize to third parties and get them on board.

For packages that are owned by third parties, we will need to work through the third party package owners to help them be successful on ARM64.

Work in support of this scenario will include:

• Identify/build list of the top 1000 third party shipped packages
• Determine which of these do not support ARM64
• Determine if there are native dependencies and partner with the owners (internal or third party) to resolve. Evangelize the benefits of enabling ARM64.
• Determine if ARM64 was unintentionally excluded due to an x64 RID and if so work with the owners to resolve
• Determine whether any support ARM64 but with limited functionality and if so work with owners.
• Guidance for the top libraries on how they can get better perf for their libraries on ARM64 for e.g. by vectorizing.
• Determine perf characteristics for these packages relative to x64 and evangelize the perf requirements

What does success look like (include a metric if possible)

• Top 1000 packages support ARM64 on all .NET supported operating systems

User Stories in this Epic:

• State of top NuGet packages understood

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Summary

The top packages developers use need to support ARM64 so when developers try to build new apps or port existing apps to run on ARM64 the packages they need work and they are not blocked.

Getting Microsoft owned NuGet packages to support ARM64 will be a first step towards unblocking the rest of the ecosystem for ARM64. Without a catalog of Microsoft packages that already work it will be hard to evangelize to third parties and get them on board.

For packages that are owned by third parties, we will need to work through the third party package owners to help them be successful on ARM64.

Work in support of this scenario will include:

• Identify/build list of the top 1000 third party shipped packages
• Determine which of these do not support ARM64
• Determine if there are native dependencies and partner with the owners (internal or third party) to resolve. Evangelize the benefits of enabling ARM64.
• Determine if ARM64 was unintentionally excluded due to an x64 RID and if so work with the owners to resolve
• Determine whether any support ARM64 but with limited functionality and if so work with owners.
• Guidance for the top libraries on how they can get better perf for their libraries on ARM64 for e.g. by vectorizing.
• Determine perf characteristics for these packages relative to x64 and evangelize the perf requirements

What does success look like (include a metric if possible)

• Top 1000 packages support ARM64 on all .NET supported operating systems

User Stories in this Epic:

• #
• #
• #

Author:	jamshedd
Assignees:	kalaskarsanket
Labels:	Epic, area-Meta, Priority:0
Milestone:	7.0.0

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Summary

The top packages developers use need to support ARM64 so when developers try to build new apps or port existing apps to run on ARM64 the packages they need work and they are not blocked.

Getting Microsoft owned NuGet packages to support ARM64 will be a first step towards unblocking the rest of the ecosystem for ARM64. Without a catalog of Microsoft packages that already work it will be hard to evangelize to third parties and get them on board.

For packages that are owned by third parties, we will need to work through the third party package owners to help them be successful on ARM64.

Work in support of this scenario will include:

• Identify/build list of the top 1000 third party shipped packages
• Determine which of these do not support ARM64
• Determine if there are native dependencies and partner with the owners (internal or third party) to resolve. Evangelize the benefits of enabling ARM64.
• Determine if ARM64 was unintentionally excluded due to an x64 RID and if so work with the owners to resolve
• Determine whether any support ARM64 but with limited functionality and if so work with owners.
• Guidance for the top libraries on how they can get better perf for their libraries on ARM64 for e.g. by vectorizing.
• Determine perf characteristics for these packages relative to x64 and evangelize the perf requirements

What does success look like (include a metric if possible)

• Top 1000 packages support ARM64 on all .NET supported operating systems

User Stories in this Epic:

• State of top NuGet packages understood

Author:	jamshedd
Assignees:	kalaskarsanket
Labels:	Epic, area-Meta, Priority:0
Milestone:	7.0.0