Migration Guide --> General Information --> Reasons for Porting to .NET

[Migration Guide Project](https://github.com/dotnet/docs/projects/128)
New TOC: #23215
**Leverage existing documentation if it exists elsewhere.**

---

Top reasons for porting from .NET Framework to .NET
- Performance
- This is a top attention getter, address the following...
- https://devdiv.visualstudio.com/FirstPartyEngagements/_wiki/wikis/FirstPartyEngagements.wiki/24103/Perf-Benchmarking
- https://devdiv.visualstudio.com/FirstPartyEngagements/_wiki/wikis/FirstPartyEngagements.wiki/10521/1st-Party-Provided-Perf-Data
- https://devdiv.visualstudio.com/FirstPartyEngagements/_wiki/wikis/FirstPartyEngagements.wiki/10893/NET-Core-Perf-Improvements
- Case Studies...
- https://devdiv.visualstudio.com/FirstPartyEngagements/_wiki/wikis/FirstPartyEngagements.wiki/10893/NET-Core-Perf-Improvements
- https://devdiv.visualstudio.com/FirstPartyEngagements/_wiki/wikis/FirstPartyEngagements.wiki/20624/AAD-Gateway-Service-Migration-to-.NET-Core
- https://devdiv.visualstudio.com/FirstPartyEngagements/_wiki/wikis/FirstPartyEngagements.wiki/11493/Bing-XAP's-Migration-to-.NET-Core
- Cross-platform
- Microservice architecture
- Deployment flexibility
- Dependency injection

Inizia con il progetto Migration Guide e il nuovo TOC in issue #23215, quindi verifica se la documentazione esistente copre i motivi elencati per il porting. Usa le risorse sulle prestazioni e i case study collegati quando sono accessibili. Il lavoro è completo quando viene aggiunta una sezione a Migration Guide che copra prestazioni, supporto multipiattaforma, microservizi, flessibilità di deployment e dependency injection.

Scritto dal modello di indicizzazione a partire dal testo della issue.