Skip to content

Commit 7e2da0e

Browse files
committed
clean up
1 parent 85978df commit 7e2da0e

File tree

2 files changed

+0
-215
lines changed

2 files changed

+0
-215
lines changed

aspnetcore/migration/fx-to-core/includes/index5.md

Lines changed: 0 additions & 200 deletions
This file was deleted.

aspnetcore/migration/fx-to-core/index.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -41,23 +41,8 @@ Most non-trivial ASP.NET Framework applications should use incremental migration
4141
- **[Porting ASP.NET Apps eBook](https://aka.ms/aspnet-porting-ebook)** - Complete reference guide
4242
- **[eShop Migration Example](/dotnet/architecture/porting-existing-aspnet-apps/example-migration-eshop)** - Real-world case study
4343

44-
## Key benefits of ASP.NET Core
45-
46-
Understanding these advantages will help justify your migration effort:
47-
48-
- **Performance**: Up to 10x faster than ASP.NET Framework
49-
- **Cross-platform**: Deploy on Windows, Linux, or macOS
50-
- **Modern features**: Built-in dependency injection, configuration, and logging
51-
- **Cloud-ready**: Optimized for containers and microservices
52-
- **Future-proof**: Regular updates and long-term support
53-
5444
## Changes to technology areas
5545

5646
Before you begin, review the [technical differences between ASP.NET Framework and ASP.NET Core](xref:migration/fx-to-core/areas) to understand key changes that may affect your migration.
5747

58-
## What's next?
59-
60-
1. **[Review incremental migration](xref:migration/fx-to-core/inc/overview)** - Recommended for most teams
61-
2. **Choose your application-specific guide** from the table above
62-
6348
:::moniker-end

0 commit comments

Comments
 (0)