Freeman - Pro ASP.NET Core MVC 2
Here you can read online Freeman - Pro ASP.NET Core MVC 2 full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Berkeley;CA, year: 2017, publisher: Apress, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
Pro ASP.NET Core MVC 2: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Pro ASP.NET Core MVC 2" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Now in its 7th edition, the best selling book on MVC is updated for ASP.NET Core MVC 2. It contains detailed explanations of the Core MVC functionality which enables developers to produce leaner, cloud optimized and mobile-ready applications for the .NET platform. This book puts ASP.NET Core MVC into context and dives deep into the tools and techniques required to build modern, cloud optimized extensible web applications. All the new MVC features are described in detail and the author explains how best to apply them to both new and existing projects. The ASP.NET Core MVC Framework is the latest evolution of Microsofts ASP.NET web platform, built on a completely new foundation. It represents a fundamental change to how Microsoft constructs and deploys web frameworks and is free of the legacy of earlier technologies such as Web Forms. ASP.NET Core MVC provides a host agnostic framework and a high-productivity programming model that promotes cleaner code architecture, test-driven development, and powerful extensibility. Best-selling author Adam Freeman has thoroughly revised this market-leading book and explains how to get the most from ASP.NET Core MVC. He starts with the nuts-and-bolts and shows you everything through to advanced features, going in-depth to give you the knowledge you need. The book includes a fully worked case study of a functioning web application that readers can use as a template for their own projects. Whats New in This Edition Fully updated for Visual Studio 2017, C# 7 and .NET Core 2 Coverage of new features such as view filters Wider platform and tooling coverage than ever before, with more on Visual Studio Code and working with .NET Core on non-Windows platforms Docker-based application deployment What You Will Learn Gain a solid architectural understanding of ASP.NET Core MVC Explore the entire ASP.NET MVC Framework as a cohesive whole See how MVC and test-driven development work in action Learn whats new in ASP.NET Core MVC 2 and how best to apply these new features to your own work See how to create RESTful web services and Single Page Applications Build on your existing knowledge of previous MVC releases to get up and running with the new programming model quickly and effectively Who This Book Is For This book is for web developers with a basic knowledge of ASP.NET and C# who want to incorporate the latest improvements and functionality in the ASP.NET Core MVC 2 Framework.;Part I: Introducing ASP.NET Core MVC.- 1: Putting ASP.NET MVC In Context -- 2: Your First MVC Application -- 3: The MVC Pattern, Projects and Conventions -- 4: Essential C# Features -- 5: Working with Razor -- 6: Working with Visual Studio -- 7: Testing MVC Applications -- 8: SportsStore: A Real Application -- 9: SportsStore: Navigation -- 10: SportsStore: Cart -- 11: SportsStore: Administration -- 12: SportsStore: Security & Deployment -- 13: SportsStore: Working with Visual Studio Code.- Part II: ASP.NET Core MVC In Depth.- 14: Configuring Applications -- 15: URL Routing -- 16: Advanced Routing Features -- 17: Controllers and Actions -- 18: Dependency Injection -- 19: Filters -- 20: API Controllers -- 21: Views -- 22: View Components -- 23: Tag Helpers -- 24: Using the Form Tag Helpers -- 25: Using Other Built-in Tag Helpers -- 26: Model Binding -- 27: Model Validation -- 28: Identity -- 29: Applying Identity -- 30: Advanced Identity -- 31: Constraints and Conventions.
Freeman: author's other books
Who wrote Pro ASP.NET Core MVC 2? Find out the surname, the name of the author of the book and a list of all author's works by series.
Freeman
![Freeman - Pro design patterns in Swift: [learn how to apply classic design patterns to iOS app development using Swift]](/uploads/posts/book/201359/thumbs/freeman-pro-design-patterns-in-swift-learn-how.jpg)
Freeman
Chowdhuri
Dustin Metzgar
Adam Freeman
Andrew Troelsen
Pro ASP.NET Core MVC 2 — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Pro ASP.NET Core MVC 2" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Part I
Introducing ASP.NET Core MVC 2
Introducing ASP.NET Core MVC 2
Introducing ASP.NET Core MVC 2
ASP.NET Core MVC is a radical shift for web developers using the Microsoft platform. It emphasizes clean architecture, design patterns, and testability, and it doesnt try to conceal how the Web works.
The first part of this book is designed to help you understand broadly the foundational ideas of MVC development, including the new features in ASP.NET Core MVC, and to experience in practice what the framework is like to use.
Adam Freeman 2017
Adam Freeman Pro ASP.NET Core MVC 21. ASP .NET Core MVC in Context
Adam Freeman 1
(1)
London, UK
ASP.NET Core MVC is a web application development framework from Microsoft that combines the effectiveness and tidiness of model-view-controller (MVC) architecture, ideas and techniques from agile development, and the best parts of the .NET platform. In this chapter, youll learn why Microsoft created ASP.NET Core MVC, see how it compares to its predecessors and alternatives, and, finally, get an overview of whats new in ASP.NET Core MVC and whats covered in this book.
Understanding the History of ASP.NET Core MVC
The original ASP.NET was introduced in 2002, at a time when Microsoft was keen to protect a dominant position in traditional desktop application development and saw the Internet as a threat. Figure illustrates Microsofts technology stack as it appeared then. 
Figure 1-1.
The ASP.NET Web Forms technology stack
ASP.NET Web Forms
With Web Forms, Microsoft attempted to hide both Hypertext Transfer Protocol (HTTP), with its intrinsic statelessness, and Hypertext Markup Language (HTML), which at the time was unfamiliar to many developers, by modeling the user interface (UI) as a hierarchy of server-side control objects. Each control kept track of its own state across requests, rendering itself as HTML when needed and automatically connecting client-side events (for example, a button click) with the corresponding server-side event handler code. In effect, Web Forms is a giant abstraction layer designed to deliver a classic event-driven graphical user interface (GUI) over the Web.
The idea was to make web development feel just the same as developing a desktop application. Developers could think in terms of a stateful UI and didnt need to work with a series of independent HTTP requests and responses. Microsoft could seamlessly transition the army of Windows desktop developers into the new world of web applications.
What Was Wrong with ASP.NET Web Forms?
Traditional ASP.NET Web Forms development was good in principle, but reality proved more complicated.
- View State weight : The actual mechanism for maintaining state across requests (known as View State) resulted in large blocks of data being transferred between the client and server. This data could reach hundreds of kilobytes in even modest web applications, and it went back and forth with every request, leading to slower response times and increasing the bandwidth demands of the server.
- Page life cycle : The mechanism for connecting client-side events with server-side event handler code, part of the page life cycle, could be complicated and delicate. Few developers had success manipulating the control hierarchy at runtime without creating View State errors or finding that some event handlers mysteriously failed to execute.
- False sense of separation of concerns : ASP.NET Web Forms code-behind model provided a means to take application code out of its HTML markup and into a separate code-behind class. This was done to separate logic and presentation, but, in reality, developers were encouraged to mix presentation code (for example, manipulating the server-side control tree) with their application logic (for example, manipulating database data) in these same monstrous code-behind classes. The end result could be fragile and unintelligible.
- Limited control over HTML : Server controls rendered themselves as HTML, but not necessarily the HTML you wanted. In early versions of ASP.NET, the HTML output failed to meet web standards or make good use of Cascading Style Sheets (CSS), and server controls generated unpredictable and complex ID attributes that were hard to access using JavaScript. These problems have improved in recent Web Forms releases, but it can still be tricky to get the HTML you expect.
- Leaky abstraction : Web Forms tried to hide HTML and HTTP wherever possible. As you tried to implement custom behaviors, you frequently fell out of the abstraction, which forced you to reverse-engineer the postback event mechanism or perform obtuse acts to make it generate the desired HTML.
- Low testability : The designers of Web Forms could not have anticipated that automated testing would become an essential component of software development. The tightly coupled architecture they designed was unsuitable for unit testing. Integration testing could be a challenge, too.
Web Forms wasnt all bad, and eventually, Microsoft put effort into improving standards compliance and simplifying the development process and even took some features from the original ASP.NET MVC Framework and applied them to Web Forms. Web Forms excelled when you needed quick results, and you could have a reasonably complex web app up and running within a day. But unless you were careful during development, you would find that the application you created was hard to test and hard to maintain.
The Original MVC Framework
In October 2007, Microsoft announced a new development platform, built on the existing ASP.NET platform, that was intended as a direct response to the criticisms of Web Forms and the popularity of competing platforms such as Ruby on Rails. The new platform was called the ASP.NET MVC Framework and reflected the emerging trends in web application development, such as HTML and CSS standardization, RESTful web services, effective unit testing, and the idea that developers should embrace the stateless nature of HTTP.
The concepts that underpin the original MVC Framework seem natural and obvious now, but they were lacking from the world of .NET web development in 2007. The introduction of the ASP.NET MVC Framework brought Microsofts web development platform back into the modern age.
The MVC Framework also signaled an important change in attitude from Microsoft, which had previously tried to control every component in the web application toolchain. With the MVC Framework, Microsoft built on open source tools such as jQuery, took on design conventions and best practices from competing (and more successful) platforms, and released the source code to the MVC Framework for developers to inspect.
What Was Wrong with the Original MVC Framework?
At the time the MVC Framework was created, it made sense for Microsoft to create it on top of the existing ASP.NET platform, which had a lot of solid low-level functionality that provided a head start in the development process and which was already well-known and understood by ASP.NET developers.
But compromises were required to graft the MVC Framework onto a platform that was originally designed for Web Forms. MVC Framework developers became used to using configuration settings and code tweaks that disabled or reconfigured features that didnt have any bearing on their web application but were required to get everything working.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Similar books «Pro ASP.NET Core MVC 2»
Look at similar books to Pro ASP.NET Core MVC 2. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Chowdhuri
Dustin Metzgar
Adam Freeman
Andrew Troelsen
Reviews about «Pro ASP.NET Core MVC 2»
Discussion, reviews of the book Pro ASP.NET Core MVC 2 and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.