04198nam a22004095i 4500001001800000003000900018005001700027007001500044008004100059020003700100024003500137050001100172072001600183072002300199072001500222100008700237245018700324250001800511264005400529300004400583336002600627337002600653338003600679347002400715505044600739520229301185650004703478650003903525710003403564773002603598776003603624776003603660856004603696912001403742912001503756999001703771979-8-8688-0617-9DE-He21320251030113228.0cr nn 008mamaa241015s2024    xxu|    s    |||| 0|eng d  a97988688061799979-8-8688-0617-97 a10.1007/979-8-8688-0617-92doi 4aHD30.2 7aKJQ2bicssc 7aCOM0320002bisacsh 7aKJQ2thema1 aHerceg, Tomáš.eauthor.4aut4http://id.loc.gov/vocabulary/relators/aut98609610aModernizing .NET Web Applicationsh[electronic resource] :bEverything You Need to Know About Migrating ASP.NET Web Applications to the Latest Version of .NET /cby Tomáš Herceg.  a1st ed. 2024. 1aBerkeley, CA :bApress :bImprint: Apress,c2024.  aXVI, 680 p. 45 illus.bonline resource.  atextbtxt2rdacontent  acomputerbc2rdamedia  aonline resourcebcr2rdacarrier  atext filebPDF2rda0 aChapter 1: Introduction -- Chapter 2: Justifying Modernization -- Chapter 3: Before You Start -- Chapter 4: Migrating APIs and Web Services -- Chapter 5: Migrating Data Access -- Chapter 6: Migrating Identity Stores -- Chapter 7: In-place Migration of UI Applications -- Chapter 8: Side-by-Side Migration of UI Applications -- Chapter 9: Migration of ASP.NET MVC and Web Pages -- Chapter 10: A Word on Architecture -- Chapter 11: Conclusion.  aIn 2016, Microsoft introduced the new generation of .NET called .NET Core. It brought many fundamental improvements to the platform, but there were also many breaking changes and missing APIs, especially when it comes to creating web applications. Upgrading any website running on .NET Framework to the new .NET Core proved to be a complex process, which can take months or even years. This book describes two approaches you can take to incrementally modernize legacy .NET web applications. It explains the changes that happened in ASP.NET MVC, ASP.NET Web API, Entity Framework, ASP.NET Identity, SignalR, and other libraries. It also shows a migration path for applications written in ASP.NET Web Forms: a technology which isn’t supported in the new .NET at all. In addition, the book describes the new frameworks available in the ASP.NET Core platform (Blazor, Razor Pages, ASP.NET Core MVC, SignalR Core, and so on) and helps you decide which technology will be the best fit. The book also covers several “soft” areas: how to explain the benefits or necessity for the modernization to your company management, how to deal with refactoring and improving the overall code quality during the entire process, and how to adjust the architecture of the application to be ready for another technology upgrade in the future. The topic of modernization is highly relevant. There are still plenty of legacy .NET applications that are being actively developed and maintained. Many of them were developed for 10+ years, they involve plethora of company-specific know-how, and it is not economically feasible to rewrite them from scratch. What You Will Learn Discover the changes you need to make in a legacy ASP.NET application to migrate it to .NET 8 and beyond Estimate the required effort and prepare the entire process Use the In-place or Side-by-side approach to modernize your application incrementally Migrate from ASP.NET Web Services or WCF to REST or gRPC Migrate from ASP.NET SignalR to SignalR Core or from Entity Framework to EF Core Migrate from Forms Authentication to ASP.NET Identity Migrate ASP.NET Web Forms to Blazor Server or DotVVM Migrate ASP.NET MVC and Web Pages to ASP.NET Core MVC and Razor Pages Refactor and clean up your codebase to make it more maintainable . 0aInformation technologyxManagement.95722314aBusiness IT Infrastructure.9697442 aSpringerLink (Online service)0 tSpringer Nature eBook08iPrinted edition:z979886880616208iPrinted edition:z979886880618640uhttps://doi.org/10.1007/979-8-8688-0617-9  aZDB-2-BUM  aZDB-2-SXBM  c64232d64232