000 04406nam a22004575i 4500
001 979-8-8688-0617-9
003 DE-He213
005 20251030113228.0
007 cr nn 008mamaa
008 241015s2024 xxu| s |||| 0|eng d
020 _a9798868806179
_9979-8-8688-0617-9
024 7 _a10.1007/979-8-8688-0617-9
_2doi
050 4 _aHD30.2
072 7 _aKJQ
_2bicssc
072 7 _aCOM032000
_2bisacsh
072 7 _aKJQ
_2thema
100 1 _aHerceg, Tomáš.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_986096
245 1 0 _aModernizing .NET Web Applications
_h[electronic resource] :
_bEverything You Need to Know About Migrating ASP.NET Web Applications to the Latest Version of .NET /
_cby Tomáš Herceg.
250 _a1st ed. 2024.
264 1 _aBerkeley, CA :
_bApress :
_bImprint: Apress,
_c2024.
300 _aXVI, 680 p. 45 illus.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
505 0 _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.
520 _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 .
650 0 _aInformation technology
_xManagement.
_957223
650 1 4 _aBusiness IT Infrastructure.
_969744
710 2 _aSpringerLink (Online service)
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9798868806162
776 0 8 _iPrinted edition:
_z9798868806186
856 4 0 _uhttps://doi.org/10.1007/979-8-8688-0617-9
912 _aZDB-2-BUM
912 _aZDB-2-SXBM
999 _c64232
_d64232