Programming ASP NET MVC 4 Developing Real World Web Applications with ASP NET MVC 1st Edition Jess Chadwick

Visit https://ebookfinal.com to download the full version and explore more ebooks Programming ASP NET MVC 4 Developing Real World Web Applications with ASP NET MVC 1st Edition Jess Chadwick _____ Click the link below to download _____ https://ebookfinal.com/download/programming-asp-net- mvc-4-developing-real-world-web-applications-with-asp- net-mvc-1st-edition-jess-chadwick/ Explore and download more ebooks at ebookfinal.com

Here are some suggested products you might be interested in. Click the link to download Programming Microsoft ASP NET MVC 1st Edition Dino Esposito https://ebookfinal.com/download/programming-microsoft-asp-net-mvc-1st- edition-dino-esposito/ Pro ASP NET MVC 4 4th Edition Adam Freeman https://ebookfinal.com/download/pro-asp-net-mvc-4-4th-edition-adam- freeman/ Beginning jQuery 2 for ASP NET Developers Using jQuery 2 with ASP NET Web Forms and ASP NET MVC 1st Edition Bipin Joshi (Auth.) https://ebookfinal.com/download/beginning-jquery-2-for-asp-net- developers-using-jquery-2-with-asp-net-web-forms-and-asp-net-mvc-1st- edition-bipin-joshi-auth/ ASP NET MVC Framework Unleashed 1st Edition Stephen Walther https://ebookfinal.com/download/asp-net-mvc-framework-unleashed-1st- edition-stephen-walther/

Developing Web applications with Visual Basic NET and ASP NET 1st Edition John Alexander https://ebookfinal.com/download/developing-web-applications-with- visual-basic-net-and-asp-net-1st-edition-john-alexander/ Professional ASP NET MVC 1 0 1st Edition Rob Conery https://ebookfinal.com/download/professional-asp-net-mvc-1-0-1st- edition-rob-conery/ Beginning ASP NET MVC 1 0 1st Edition Simone Chiaretta https://ebookfinal.com/download/beginning-asp-net-mvc-1-0-1st-edition- simone-chiaretta/ Pro ASP NET MVC 2 Framework 2nd Edition Steven Sanderson https://ebookfinal.com/download/pro-asp-net-mvc-2-framework-2nd- edition-steven-sanderson/ Windows Azure and ASP NET MVC Migration 1st Edition Benjamin Perkins https://ebookfinal.com/download/windows-azure-and-asp-net-mvc- migration-1st-edition-benjamin-perkins/

Programming ASP NET MVC 4 Developing Real World Web Applications with ASP NET MVC 1st Edition Jess Chadwick Digital Instant Download Author(s): Jess Chadwick, Todd Snyder, Hrusikesh Panda ISBN(s): 9781449320317, 1449320317 Edition: 1 File Details: PDF, 9.42 MB Year: 2012 Language: english

Programming ASP.NET MVC 4 Jess Chadwick, Todd Snyder, and Hrusikesh Panda Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo

Programming ASP.NET MVC 4 by Jess Chadwick, Todd Snyder, and Hrusikesh Panda Copyright © 2012 Jess Chadwick, Todd Synder, Hrusikesh Panda. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com. Editor: Rachel Roumeliotis Production Editor: Rachel Steely Copyeditor: Rachel Head Proofreader: Leslie Graham, nSight Indexer: Lucie Haskins Cover Designer: Karen Montgomery Interior Designer: David Futato Illustrators: Robert Romano and Rebecca Demarest October 2012: First Edition. Revision History for the First Edition: 2012-09-14 First release See http://oreilly.com/catalog/errata.csp?isbn=9781449320317 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Programming ASP.NET MVC 4, the image of a scabbardfish, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein. ISBN: 978-1-449-32031-7 [LSI] 1347629749

Table of Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Part I. Up and Running 1. Fundamentals of ASP.NET MVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Microsoft’s Web Development Platforms 3 Active Server Pages (ASP) 3 ASP.NET Web Forms 4 ASP.NET MVC 4 The Model-View-Controller Architecture 4 The Model 5 The View 6 The Controller 6 What’s New in ASP.NET MVC 4? 6 Introduction to EBuy 8 Installing ASP.NET MVC 9 Creating an ASP.NET MVC Application 9 Project Templates 10 Convention over Configuration 13 Running the Application 15 Routing 15 Configuring Routes 16 Controllers 18 Controller Actions 19 Action Results 19 Action Parameters 21 Action Filters 23 Views 24 Locating Views 24 Hello, Razor! 26 Differentiating Code and Markup 27 iii

Layouts 28 Partial Views 30 Displaying Data 31 HTML and URL Helpers 33 Models 34 Putting It All Together 35 The Route 35 The Controller 35 The View 38 Authentication 41 The AccountController 42 Summary 44 2. ASP.NET MVC for Web Forms Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 It’s All Just ASP.NET 45 Tools, Languages, and APIs 46 HTTP Handlers and Modules 46 Managing State 46 Deployment and Runtime 47 More Differences than Similarities 47 Separation of Application Logic and View Logic 48 URLs and Routing 48 State Management 49 Rendering HTML 50 Authoring ASP.NET MVC Views Using Web Forms Syntax 54 A Word of Caution 55 Summary 56 3. Working with Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Building a Form 57 Handling Form Posts 59 Saving Data to a Database 59 Entity Framework Code First: Convention over Configuration 60 Creating a Data Access Layer with Entity Framework Code First 60 Validating Data 61 Specifying Business Rules with Data Annotations 63 Displaying Validation Errors 65 Summary 68 4. Client-Side Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Working with JavaScript 69 Selectors 71 Responding to Events 74 iv | Table of Contents

DOM Manipulation 76 AJAX 77 Client-Side Validation 79 Summary 83 Part II. Going to the Next Level 5. Web Application Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 The Model-View-Controller Pattern 87 Separation of Concerns 87 MVC and Web Frameworks 88 Architecting a Web Application 90 Logical Design 90 ASP.NET MVC Web Application Logical Design 90 Logical Design Best Practices 92 Physical Design 93 Project Namespace and Assembly Names 93 Deployment Options 94 Physical Design Best Practices 94 Design Principles 96 SOLID 96 Inversion of Control 102 Don’t Repeat Yourself 110 Summary 110 6. Enhancing Your Site with AJAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Partial Rendering 111 Rendering Partial Views 112 JavaScript Rendering 117 Rendering JSON Data 118 Requesting JSON Data 119 Client-Side Templates 120 Reusing Logic Across AJAX and Non-AJAX Requests 123 Responding to AJAX Requests 124 Responding to JSON Requests 125 Applying the Same Logic Across Multiple Controller Actions 126 Sending Data to the Server 128 Posting Complex JSON Objects 129 Model Binder Selection 131 Sending and Receiving JSON Data Effectively 132 Cross-Domain AJAX 133 JSONP 133 Table of Contents | v

Enabling Cross-Origin Resource Sharing 137 Summary 138 7. The ASP.NET Web API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Building a Data Service 139 Registering Web API Routes 141 Leaning on Convention over Configuration 142 Overriding Conventions 143 Hooking Up the API 143 Paging and Querying Data 146 Exception Handling 147 Media Formatters 149 Summary 152 8. Advanced Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Data Access Patterns 153 Plain Old CLR Objects 153 Using the Repository Pattern 154 Object Relational Mappers 156 Entity Framework Overview 158 Choosing a Data Access Approach 159 Database Concurrency 160 Building a Data Access Layer 161 Using Entity Framework Code First 161 The EBuy Business Domain Model 163 Working with a Data Context 167 Sorting, Filtering, and Paging Data 168 Summary 174 9. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Building Secure Web Applications 175 Defense in Depth 175 Never Trust Input 176 Enforce the Principle of Least Privilege 176 Assume External Systems Are Insecure 176 Reduce Surface Area 176 Disable Unnecessary Features 177 Securing an Application 177 Securing an Intranet Application 178 Forms Authentication 183 Guarding Against Attacks 192 SQL Injection 192 Cross-Site Scripting 198 vi | Table of Contents

Cross-Site Request Forgery 199 Summary 201 10. Mobile Web Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 ASP.NET MVC 4 Mobile Features 203 Making Your Application Mobile Friendly 205 Creating the Auctions Mobile View 205 Getting Started with jQuery Mobile 207 Enhancing the View with jQuery Mobile 209 Avoiding Desktop Views in the Mobile Site 216 Improving Mobile Experience 216 Adaptive Rendering 217 The Viewport Tag 217 Mobile Feature Detection 218 CSS Media Queries 220 Browser-Specific Views 221 Creating a New Mobile Application from Scratch 224 The jQuery Mobile Paradigm Shift 224 The ASP.NET MVC 4 Mobile Template 224 Using the ASP.NET MVC 4 Mobile Application Template 226 Summary 229 Part III. Going Above and Beyond 11. Parallel, Asynchronous, and Real-Time Data Operations . . . . . . . . . . . . . . . . . . . . . 233 Asynchronous Controllers 233 Creating an Asynchronous Controller 234 Choosing When to Use Asynchronous Controllers 236 Real-Time Asynchronous Communication 236 Comparing Application Models 237 HTTP Polling 237 HTTP Long Polling 238 Server-Sent Events 239 WebSockets 240 Empowering Real-Time Communication 241 Configuring and Tuning 245 Summary 246 12. Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Types of Caching 247 Server-Side Caching 248 Client-Side Caching 248 Table of Contents | vii

Server-Side Caching Techniques 248 Request-Scoped Caching 248 User-Scoped Caching 249 Application-Scoped Caching 250 The ASP.NET Cache 251 The Output Cache 252 Donut Caching 255 Donut Hole Caching 257 Distributed Caching 259 Client-Side Caching Techniques 264 Understanding the Browser Cache 264 App Cache 265 Local Storage 268 Summary 269 13. Client-Side Optimization Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Anatomy of a Page 271 Anatomy of an HttpRequest 272 Best Practices 273 Make Fewer HTTP Requests 274 Use a Content Delivery Network 274 Add an Expires or a Cache-Control Header 276 GZip Components 278 Put Stylesheets at the Top 279 Put Scripts at the Bottom 279 Make Scripts and Styles External 281 Reduce DNS Lookups 282 Minify JavaScript and CSS 282 Avoid Redirects 283 Remove Duplicate Scripts 285 Configure ETags 285 Measuring Client-Side Performance 286 Putting ASP.NET MVC to Work 289 Bundling and Minification 289 Summary 293 14. Advanced Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Wayfinding 295 URLs and SEO 297 Building Routes 298 Default and Optional Route Parameters 299 Routing Order and Priority 301 Routing to Existing Files 301 viii | Table of Contents

Ignoring Routes 302 Catch-All Routes 302 Route Constraints 303 Peering into Routes Using Glimpse 305 Attribute-Based Routing 306 Extending Routing 310 The Routing Pipeline 310 Summary 315 15. Reusable UI Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 What ASP.NET MVC Offers out of the Box 317 Partial Views 317 HtmlHelper Extensions or Custom HtmlHelpers 317 Display and Editor Templates 318 Html.RenderAction() 318 Taking It a Step Further 319 The Razor Single File Generator 319 Creating Reusable ASP.NET MVC Views 321 Creating Reusable ASP.NET MVC Helpers 325 Unit Testing Razor Views 327 Summary 328 Part IV. Quality Control 16. Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Error Handling in ASP.NET MVC 331 Enabling Custom Errors 332 Handling Errors in Controller Actions 333 Defining Global Error Handlers 334 Logging and Tracing 336 Logging Errors 336 ASP.NET Health Monitoring 338 Summary 341 17. Automated Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 The Semantics of Testing 343 Manual Testing 344 Automated Testing 345 Levels of Automated Testing 345 Unit Tests 345 Fast 347 Integration Tests 348 Table of Contents | ix

Acceptance Tests 349 What Is an Automated Test Project? 350 Creating a Visual Studio Test Project 350 Creating and Executing a Unit Test 352 Testing an ASP.NET MVC Application 354 Testing the Model 355 Test-Driven Development 358 Writing Clean Automated Tests 359 Testing Controllers 361 Refactoring to Unit Tests 364 Mocking Dependencies 365 Testing Views 370 Code Coverage 372 The Myth of 100% Code Coverage 374 Developing Testable Code 374 Summary 376 18. Build Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Creating Build Scripts 378 Visual Studio Projects Are Build Scripts! 378 Adding a Simple Build Task 378 Executing the Build 379 The Possibilities Are Endless! 380 Automating the Build 380 Types of Automated Builds 381 Creating the Automated Build 383 Continuous Integration 386 Discovering Issues 386 The Principles of Continuous Integration 386 Summary 391 Part V. Going Live 19. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 What Needs to Be Deployed 395 Core Website Files 395 Static Content 398 What Not to Deploy 398 Databases and Other External Dependencies 399 What the EBuy Application Requires 400 Deploying to Internet Information Server 401 Prerequisites 401 x | Table of Contents

Creating and Configuring an IIS Website 402 Publishing from Within Visual Studio 403 Deploying to Windows Azure 407 Creating a Windows Azure Account 408 Creating a New Windows Azure Website 408 Publishing a Windows Azure Website via Source Control 409 Summary 410 Part VI. Appendixes A. ASP.NET MVC and Web Forms Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 B. Leveraging NuGet as a Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 C. Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 D. Cross-Reference: Targeted Topics, Features, and Scenarios . . . . . . . . . . . . . . . . . . . 455 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Table of Contents | xi

Preface The web application landscape is vast and varied. Microsoft’s ASP.NET Framework— built on top of the mature and robust .NET Framework—is one of the most trusted platforms in the industry. ASP.NET MVC is Microsoft’s latest addition to the world of ASP.NET providing web developers with an alternative development approach that helps you build web applications with ease. The main goal of this book is simple: to help you to build a complete understanding of the ASP.NET MVC 4 Framework from the ground up. However, it doesn’t stop there —the book combines fundamental ASP.NET MVC concepts with real-world insight, modern web technologies (such as HTML 5 and the jQuery JavaScript Framework), and powerful architecture patterns so that you’re ready to produce not just a website that uses the ASP.NET MVC Framework, but a stable and scalable web application that is easy to grow and maintain with your expanding needs. Audience This book is for people who want to learn how to leverage the Microsoft ASP.NET MVC Framework to build robust and maintainable websites. Though the book uses many code examples to describe this process in detail, it is not simply targeted at ap- plicationdevelopers.Muchofthebookintroducesconceptsandtechniquesthatbenefit both developers writing application code and the leaders driving these development projects. Assumptions This Book Makes While this book aims to teach you everything you need to know in order to create robust and maintainable web applications with the ASP.NET MVC Framework, it assumes that you already have some fundamental knowledge about application development with the Microsoft .NET Framework. In other words, you should already be comfort- able using HTML, CSS, and JavaScript to produce a very basic website and have enough knowledge of the .NET Framework and the C# language to create a “Hello World” application. xiii

Code throughout this book can be found at: https://github.com/Program mingAspNetMvcBook/CodeExamples Conventions Used in This Book The following typographical conventions are used in this book: Italic Indicates new terms, URLs, email addresses, databases and tables, filenames, and file extensions. Constant width Used for program listings, as well as within paragraphs to refer to program elements such as variable or function names, data types, environment variables, statements, and keywords. Constant width bold Used for emphasis in code and to show commands or other text that should be typed literally by the user. Constant width italic Shows text that should be replaced with user-supplied values or by values deter- mined by context. This icon signifies a tip, suggestion, or general note. This icon indicates a warning or caution. Using Code Examples This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission. xiv | Preface

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: “Programming ASP.NET MVC 4 by Jess Chadwick, Todd Synder, and Hrusikesh Panda (O’Reilly). Copyright 2012 Jess Chad- wick, Todd Synder, and Hrusikesh Panda, 978-1-449-32031-7.” If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com. Safari® Books Online Safari Books Online is an on-demand digital library that lets you easily search over 7,500 technology and creative reference books and videos to find the answers you need quickly. Withasubscription,youcanreadanypageandwatchanyvideofromourlibraryonline. Read books on your cell phone and mobile devices. Access new titles before they are available for print, and get exclusive access to manuscripts in development and post feedback for the authors. Copy and paste code samples, organize your favorites, download chapters, bookmark key sections, create notes, print out pages, and benefit from lots of other time-saving features. O’Reilly Media has uploaded this book to the Safari Books Online service. To have full digital access to this book and to other books on similar topics from O’Reilly and other publishers, sign up for free at http://my.safaribooksonline.com. How to Contact Us Please address comments and questions concerning this book to the publisher: O’Reilly Media, Inc. 1005 Gravenstein Highway North Sebastopol, CA 95472 800-998-9938 (in the United States or Canada) 707-829-0515 (international or local) 707-829-0104 (fax) We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at: http://bit.ly/Programming_ASP_NET To comment or ask technical questions about this book, send email to: bookquestions@oreilly.com For more information about our books, courses, conferences, and news, see our website at http://www.oreilly.com. Preface | xv

Find us on Facebook: http://facebook.com/oreilly Follow us on Twitter: http://twitter.com/oreillymedia Watch us on YouTube: http://www.youtube.com/oreillymedia xvi | Preface

CHAPTER 1 Fundamentals of ASP.NET MVC Microsoft ASP.NET MVC is a web application development framework built on top of Microsoft’s popular and mature .NET Framework. The ASP.NET MVC Framework leans heavily on proven developmental patterns and practices that place an emphasis on a loosely coupled application architecture and highly maintainable code. In this chapter we’ll take a look at the fundamentals of what makes ASP.NET MVC tick—from its proud lineage and the architectural concepts on which it is built, to the use of Microsoft Visual Studio 2011 to create a fully functioning ASP.NET MVC web application. Then we’ll dive into the ASP.NET MVC web application project and see just what ASP.NET MVC gives you right from the start, including a working web page and built-in forms authentication to allow users to register and log in to your site. By the end of the chapter, you’ll have not only a working ASP.NET MVC web application, but also enough understanding of the fundamentals of ASP.NET MVC to begin building applications with it immediately. The rest of this book simply builds on these fundamentals, showing you how to make the most of the ASP.NET MVC Framework in any web application. Microsoft’s Web Development Platforms Understanding the past can be a big help in appreciating the present; so, before we get into what ASP.NET MVC is and how it works, let’s take a minute to see just where it came from. Long ago, Microsoft saw the need for a Windows-based web development platform, and the company worked hard to produce a solution. Over the past two decades, Microsoft has given the development community several web development platforms. Active Server Pages (ASP) Microsoft’s first answer to web development was Active Server Pages (ASP), a scripting language in which code and markup are authored together in a single file, with each 3

physical file corresponding to a page on the website. ASP’s server-side scripting approach became widely popular and many websites grew out of it. Some of these sites continue to serve visitors today. After a while, though, developers wanted more. They asked for features such as improved code reuse, better separation of concerns, and easier application of object-oriented programming principles. In 2002, Microsoft offered ASP.NET as a solution to these concerns. ASP.NET Web Forms Like ASP, ASP.NET websites rely on a page-based approach where each page on the website is represented in the form of a physical file (called a Web Form) and is accessible using that file’s name. Unlike a page using ASP, a Web Forms page provides some separation of code and markup by splitting the web content into two different files: one for the markup and one for the code. ASP.NET and the Web Forms approach served developers’ needs for many years, and this continues to be the web development framework of choice for many .NET developers. Some .NET developers, however, consider the Web Forms approach too much of an abstraction from the underlying HTML, JavaScript, and CSS. Some developers just can’t be pleased! Or can they? ASP.NET MVC Microsoft was quick to spot the growing need in the ASP.NET developer community for something different than the page-based Web Forms approach, and the company released the first version of ASP.NET MVC in 2008. Representing a total departure from the Web Forms approach, ASP.NET MVC abandons the page-based architecture completely, relying on the Model-View-Controller (MVC) architecture instead. Unlike ASP.NET Web Forms, which was introduced as a replacement to its predecessor, ASP, ASP.NET MVC does not in any way replace the existing Web Forms Framework. Quite the contrary—both ASP.NET MVC and Web Forms applications are built on top of the common ASP.NET Framework, which provides a common web API that both frameworks leverage quite heavily. The idea that ASP.NET MVC and Web Forms are just different ways of making an ASP.NET website is a common theme throughout this book; in fact, both Chapter 2 and Appendix A explore this concept in depth. The Model-View-Controller Architecture The Model-View-Controller pattern is an architectural pattern that encourages strict isolation between the individual parts of an application. This isolation is better known as separation of concerns, or, in more general terms, “loose coupling.” Virtually all 4 | Chapter 1: Fundamentals of ASP.NET MVC

aspects of MVC—and, consequently, the ASP.NET MVC Framework—are driven by this goal of keeping disparate parts of an application isolated from each other. Architecting applications in a loosely coupled manner brings a number of both short- and long-term benefits: Development Individual components do not directly depend on other components, which means that they can be more easily developed in isolation. Components can also be readily replacedorsubstituted, preventingcomplicationsinone componentfromaffecting the development of other components with which it may interact. Testability Loose coupling of components allows test implementations to stand in for “production”components.Thismakesiteasierto,say,avoidmakingcallstoadatabase, by replacing the component that makes database calls with one that simply returns static data. The ability for components to be easily swapped with mock representations greatly facilitates the testing process, which can drastically increase the reliability of the system over time. Maintenance Isolated component logic means that changes are typically isolated to a small number of components—often just one. Since the risk of change generally correlates to the scope of the change, modifying fewer components is a good thing! The MVC pattern splits an application into three layers: the model, the view, and the controller (see Figure 1-1). Each of these layers has a very specific job that it is responsible for and—most important—is not concerned with how the other layers do their jobs. Figure 1-1. The MVC architecture The Model The model represents core business logic and data. Models encapsulate the properties and behavior of a domain entity and expose properties that describe the entity. For example, the Auction class represents the concept of an “auction” in the application The Model-View-Controller Architecture | 5

and may expose properties such as Title and CurrentBid, as well as exposing behavior in the form of methods such as Bid(). The View The view is responsible for transforming a model or models into a visual representation. In web applications, this most often means generating HTML to be rendered in the user’s browser, although views can manifest in many forms. For instance, the same model might be visualized in HTML, PDF, XML, or perhaps even in a spreadsheet. Following separation of concerns, views should concentrate only on displaying data and should not contain any business logic themselves—the business logic stays in the model, which should provide the view with everything it needs. The Controller The controller, as the name implies, controls the application logic and acts as the co- ordinator between the view and the model. Controllers receive input from users via the view, then work with the model to perform specific actions, passing the results back to the view. What’s New in ASP.NET MVC 4? This book explores the ASP.NET MVC Framework in depth, showing how to make the most of the features and functionality it offers. Since we’re now up to the fourth version of the framework, however, much of what the book covers is functionality that existed prior to this latest version. If you are already familiar with previous versions of the framework, you’re probably eager to skip over what you already know and begin learning all about the new additions. The list below gives a brief description of each of the features new to version 4 of ASP.NET MVC, along with references pointing you to the sections of the book that show these features in action: Asynchronous controllers Internet Information Server (IIS) processes each request it receives on a new thread, so each new request ties up one of the finite number of threads available to IIS, evenifthatthreadissittingidle(forexample,waitingforaresponsefromadatabase query or web service). And, while recent updates in .NET Framework 4.0 and IIS 7 have drastically increased the default number of threads available to the IIS thread pool, it’s still a good practice to avoid holding on to system resources for longer than you need to. Version 4 of the ASP.NET MVC Framework introduces asynchronous controllers to better handle these types of long-running requests in a more asynchronous fashion. Through the use of asynchronous controllers, you can tell the framework to free up the thread that is processing your request, letting it 6 | Chapter 1: Fundamentals of ASP.NET MVC

perform other processing tasks while it waits for the various tasks in the request to finish. Once they finish, the framework picks up where it left off, and returns the same response as if the request had gone through a normal synchronous controller —except now you can handle many more requests at once! If you’re interested in learning more about asynchronous controllers, see Chapter 11, which explains them in depth. Display modes A growing number of devices are Internet-connected and ready to surf your site, and you need to be ready for them. Many times, the data displayed on these devices is the same as the data displayed on desktop devices, except the visual elements need to take into consideration the smaller form factor of mobile devices. ASP.NET MVCdisplaymodesprovideaneasy,convention-basedapproachfortailoringviews and layouts to target different devices. Chapter 10 shows how to apply display modes to your site as part of a holistic approach to adding mobile device support to your sites. Bundling and minification Even though it may seem like the only way to get on the Internet these days is through some sort of high-speed connection, that doesn’t mean you can treat the client-side resources that your site depends on in a haphazard manner. In fact, when you consider how the overall download times are increasing, wasting even fractions of a second in download times can really add up and begin to have a very negative effect on the perceived performance of your site. Concepts such as script and stylesheet combining and minification may not be anything new, but with the .NET Framework 4.5 release, they are now a fundamental part of the framework. What’s more, ASP.NET MVC embraces and extends the core .NET Frame- work functionality to make this tooling even more usable in your ASP.NET MVC applications. Chapter 13 helps you tackle all of these concepts and also shows you how to use the new tooling offered in the core ASP.NET and ASP.NET MVC Frameworks. Web API Simple HTTP data services are rapidly becoming the primary way to supply data to the ever-increasing variety of applications, devices, and platforms. ASP.NET MVC has always provided the ability to return data in various formats, including JSON and XML; however, the ASP.NET Web API takes this interaction a step further, providing a more modern programming model that focuses on providing full-fledged data services rather than controller actions that happen to return data. In Chapter 6, you’ll see how to really take advantage of AJAX on the client—and you’ll use ASP.NET Web API services to do it! What’s New in ASP.NET MVC 4? | 7

Did You Know…? ASP.NET MVC is open source! That’s right—as of March 2012, the entire source code for the ASP.NET MVC, Web API, and Web Pages Frameworks is available to browse and download on CodePlex. What’s more, developers are free to create their own forks and even submit patches to the core framework source code! Introduction to EBuy This book aims to show you not only the ins and outs of the ASP.NET MVC Frame- work, but also how to leverage the framework in real-world applications. The problem with such applications is that the very meaning of “real-world” indicates a certain level of complexity and uniqueness that can’t be adequately represented in a single demo application. Instead of attempting to demonstrate solutions to every problem you may face, we— the authors of this book—have assembled a list of the scenarios and issues that we have most frequently encountered and that we most frequently hear of others encountering. Though this list of scenarios may not include every scenario you’ll face while developing your application, we believe it represents the majority of the real-world problems that most developers face over the course of creating their ASP.NET MVC applications. We’re not kidding, we actually wrote a list—and it’s in the back of this book! Appendix D has a cross-referenced list of all the features and scenarios we cover and the chapter(s) in which we cover them. In order to cover the scenarios on this list, we came up with a web application that combines them all into as close to a real-world application as we could get, while still limiting the scope to something everyone understands: an online auction site. Introducing EBuy, the online auction site powered by ASP.NET MVC! From a high level, the goals of the site are pretty straightforward: allow users to list items they wish to sell, and bid on items they wish to buy. As you take a deeper look, however, you’ll begin to see that the application is a bit more complex than it sounds, requiring not only everything ASP.NET MVC has to offer, but also integration with other technologies. EBuy is not just a bunch of code that we ship along with the book, though. Each chapter of the book not only introduces more features and functionality, but uses them to build the EBuy application—from new project to deployed application, preferably while you follow along and write the code, too! 8 | Chapter 1: Fundamentals of ASP.NET MVC

OK, we’ll admit that EBuy is also “just a bunch of code.” In fact, you can download EBuy in its entirety from the book’s website: http://www .programmingaspnetmvc.com. Now, let’s stop talking about an application that doesn’t exist yet and start building it! Installing ASP.NET MVC In order to begin developing ASP.NET MVC applications, you’ll need to download and install the ASP.NET MVC 4 Framework. This is as easy as visiting the ASP.NET MVC website and clicking the Install button. This launches the Web Platform Installer, a free tool that simplifies the installation of many web tools and applications. Follow the Web Platform Installer wizard to download and install ASP.NET MVC 4 and its dependencies to your machine. NotethatinordertoinstallanduseASP.NETMVC4,youmusthaveatleastPowerShell 2.0 and Visual Studio 2010 Service Pack 1 or Visual Web Developer Express 2010 Service Pack 1. Luckily, if you do not already have them installed, the Web Platform Installer should figure it out and proceed to download and install the latest versions of PowerShell and Visual Studio for you! If you are currently using the previous version of ASP.NET MVC and would like to both create ASP.NET MVC 4 applications and continue working with ASP.NET MVC 3 applications, fear not—ASP.NET MVC can be installed and run side by side with ASP.NET MVC 3 installations. Once you’ve gotten everything installed, it’s time to proceed to the next step: creating your first ASP.NET MVC 4 application. Creating an ASP.NET MVC Application The ASP.NET MVC 4 installer adds a new Visual Studio project type named ASP.NET MVC 4 Web Application. This is your entry point to the world of ASP.NET MVC and is what you’ll use to create the new EBuy web application project that you’ll build on as you progress through this book. To create a new project, select the Visual C# version of the ASP.NET MVC 4 Web Application template and enter Ebuy.Website into the Name field (see Figure 1-2). Creating an ASP.NET MVC Application | 9

Figure 1-2. Creating the EBuy project When you click OK to continue, you’ll be presented with another dialog with more options (see Figure 1-3). This dialog lets you customize the ASP.NET MVC 4 application that Visual Studio is going to generate for you by letting you specify what kind of ASP.NET MVC site you want to create. Project Templates To begin, ASP.NET MVC 4 offers several project templates, each of which targets a different scenario: Empty The Empty template creates a bare-bones ASP.NET MVC 4 application with the appropriate folder structure that includes references to the ASP.NET MVC assemblies as well as some JavaScript libraries that you’ll probably use along the way. The template also includes a default view layout and generates a Global.asax file that includes the standard configuration code that most ASP.NET MVC applications will need. 10 | Chapter 1: Fundamentals of ASP.NET MVC

Basic The Basic template creates a folder structure that follows ASP.NET MVC 4 conventions and includes references to the ASP.NET MVC assemblies. This template represents the bare minimum that you’ll need to begin creating an ASP.NET MVC 4 project, but no more—you’ll have to do all the work from here! Internet Application The Internet Application template picks up where the Empty template leaves off, extending the Empty template to include a simple default controller (Home Controller), an AccountController with all the logic required for users to register and log in to the website, and default views for both of these controllers. Intranet Application The Intranet Application template is much like the Internet Application template, except that it is preconfigured to use Windows-based authentication, which is desirable in intranet scenarios. Figure 1-3. Customizing the EBuy project Creating an ASP.NET MVC Application | 11

Mobile Application The Mobile Application template is another variation of the Internet Application template. This template, however, is optimized for mobile devices and includes the jQuery Mobile JavaScript framework and views that apply the HTML that works best with jQuery Mobile. Web API The Web API template is yet another variation of the Internet Application template that includes a preconfigured Web API controller. Web API is the new lightweight, RESTful HTTP web services framework that integrates quite nicely with ASP.NET MVC. Web API is a great choice for quickly and easily creating data services that your AJAX-enabled applications can easily consume. Chapter 6 covers this new API in great detail. The New ASP.NET MVC Project dialog also lets you select a view engine, or syntax that your views will be written in. We’ll be using the new Razor syntax to build the EBuy reference application, so you can leave the default value (“Razor”) selected. Rest assured that you can change the view engine your application uses at any time—this option exists only to inform the wizard of the kind of views it should generate for you, not to lock the application into a specific view engine forever. Finally, choose whether or not you’d like the wizard to generate a unit test project for this solution. Once again, you don’t have to worry about this decision too much—as with any other Visual Studio solution, you are able to add a unit test project to an ASP.NET MVC web application anytime you’d like. When you’re happy with the options you’ve selected, click OK to have the wizard generate your new project! NuGet Package Management If you pay attention to the status bar as Visual Studio creates your new web application project, you may notice messages (such as “Installing package AspNetMvc…”) referring to the fact that the project template is utilizing the NuGet Package Manager to install and manage the assembly references in your application. The concept of using a package manager to manage application dependencies—especially as part of the new project template phase—is quite powerful, and also new to ASP.NET MVC 4 project types. Introduced as part of the ASP.NET MVC 3 installer, NuGet offers an alternative work- flow for managing application dependencies. Though it is not actually part of the ASP.NET MVC Framework, NuGet is doing much of the work behind the scenes to make your projects possible. A NuGet package may contain a mixture of assemblies, content, and even tools to aid in development. In the course of installing a package, NuGet will add the assemblies to the target project’s References list, copy any content into the application’s folder structure, and register any tools in the current path so that they can be executed from the Package Manager Console. 12 | Chapter 1: Fundamentals of ASP.NET MVC

However, the most important aspect of NuGet packages—indeed, the primary reason NuGet was created to begin with—has to do with dependency management. .NET applications are not monolithic, single-assembly applications—most assemblies rely on references to other assemblies in order to do their job. What’s more, assemblies generally depend on specific versions (or, at least, a minimum version) of other assemblies. In a nutshell, NuGet calculates the potentially complex relationships between all of the assemblies that an application depends on, then makes sure that you have all of the assemblies you need—and the correct versions of those assemblies. Your gateway to NuGet’s power is the NuGet Package Manager. You can access the NuGet Package Manager in two ways: The graphical user interface The NuGet Package Manager has a graphical user interface (GUI) that makes it easy to search for, install, update, and uninstall packages for a project. You can access the graphical Package Manager interface by right-clicking the website project in the Solution Explorer and selecting the “Manage NuGet Packages…” option. The Console mode The Library Package Manager Console is a Visual Studio window containing an integrated PowerShell prompt specially configured for Library Package Manager access. If you do not see the Package Manager Console window already open in Visual Studio, you can access it via the Tools > Library Package Manager > Package Manager Console menu option. To install a package from the Package Manager Console window, simply type the command Install-Package _Package Name_. For example, to install the Entity Framework package, execute the Install-Package EntityFramework command. The Package Manager Console will proceed to download the EntityFramework package and install it into your project. After the “Install-Package” step has completed, the Entity Framework assemblies will be visible in the project’s References list. Convention over Configuration To make website development easier and help developers be more productive, ASP.NET MVC relies on the concept of convention over configuration whenever possible. This means that, instead of relying on explicit configuration settings, ASP.NET MVC simply assumes that developers will follow certain conventions as they build their applications. The ASP.NET MVC project folder structure (Figure 1-4) is a great example of the framework’s use of convention over configuration. There are three special folders in the project that correspond to the elements of the MVC pattern: the Controllers, Models, and Views folders. It’s pretty clear at a glance what each of these folders contains. Creating an ASP.NET MVC Application | 13

Figure 1-4. The ASP.NET MVC project folder structure When you look at the contents of these folders, you’ll find even more conventions at work. For example, not only does the Controllers folder contain all of the application’s controller classes, but the controller classes all follow the convention of ending their names with the Controller suffix. The framework uses this convention to register the application’s controllers when it starts up and associate controllers with their corresponding routes. Next, take a look at the Views folder. Beyond the obvious convention dictating that the application’s views should live under this folder, it is split into subfolders: a Shared folder, and an optional folder to contain the views for each controller. This convention helps save developers from providing explicit locations of the views they’d like to display to users. Instead, developers can just provide the name of a view—say, “Index”— and the framework will try its best to find the view within the Views folder, first in the controller-specific folder and then, failing that, in the Shared views folder. 14 | Chapter 1: Fundamentals of ASP.NET MVC

Atfirstglance,theconceptofconventionoverconfigurationmayseemtrivial.However, these seemingly small or meaningless optimizations can really add up to significant time savings, improved code readability, and increased developer productivity. Running the Application Once your project is created, feel free to hit F5 to execute your ASP.NET MVC website and watch it render in your browser. Congratulations, you’ve just created your first ASP.NET MVC 4 application! After you’ve calmed down from the immense excitement you experience as a result of making words show up in a web browser, you might be left wondering, “What just happened? How did it do that?” Figure 1-5 shows, from a high level, how ASP.NET MVC processes a request. Figure 1-5. The ASP.NET MVC request lifecycle Though we’ll spend the rest of this book diving deeper and deeper into the components of that diagram, the next few sections start out by explaining those fundamental building blocks of ASP.NET MVC. Routing All ASP.NET MVC traffic starts out like any other website traffic: with a request to a URL. This means that, despite the fact that it is not mentioned anywhere in the name, the ASP.NET Routing framework is at the core of every ASP.NET MVC request. In simple terms, ASP.NET routing is just a pattern-matching system. At startup, the application registers one or more patterns with the framework’s route table to tell the routing system what to do with any requests that match those patterns. When the routing engine receives a request at runtime, it matches that request’s URL against the URL patterns registered with it (Figure 1-6). When the routing engine finds a matching pattern in its route table, it forwards the request to the appropriate handler for that request. Routing | 15

Otherwise, when the request’s URL does not match any of the registered route patterns, the routing engine indicates that it could not figure out how to handle the request by returning a 404 HTTP status code. Configuring Routes ASP.NET MVC routes are responsible for determining which controller method (otherwise known as a controller action) to execute for a given URL. They consist of the following properties: Unique name A name may be used as a specific reference to a given route URL pattern A simple pattern syntax that parses matching URLs into meaningful segments Defaults An optional set of default values for the segments defined in the URL pattern Constraints A set of constraints to apply against the URL pattern to more narrowly define the URLs that it matches Figure 1-6. ASP.NET routing 16 | Chapter 1: Fundamentals of ASP.NET MVC

The default ASP.NET MVC project templates add a generic route that uses the following URL convention to break the URL for a given request into three named segments, wrapped with brackets ({}): “controller”, “action”, and “id”: {controller}/{action}/{id} This route pattern is registered via a call to the MapRoute() extension method that runs during application startup (located in App_Start/RouteConfig.cs): routes.MapRoute( "Default", // Route name "{controller}/{action}/{id}", // URL with parameters new { controller = "Home", action = "Index", id = UrlParameter.Optional } // Parameter defaults ); In addition to providing a name and URL pattern, this route also defines a set of default parameters to be used in the event that the URL fits the route pattern, but doesn’t actually provide values for every segment. For instance, Table 1-1 contains a list of URLs that match this route pattern, along with corresponding values that the routing framework will provide for each of them. Table 1-1. Values provided for URLs that match our route pattern URL Controller Action ID /auctions/auction/1234 AuctionsController Auction 1234 /auctions/recent AuctionsController Recent /auctions AuctionsController Index / HomeController Index The first URL (/auctions/auction/1234) in the table is a perfect match because it satisfies every segment of the route pattern, but as you continue down the list and remove segments from the end of the URL, you begin to see defaults filling in for values that are not provided by the URL. This is a very important example of how ASP.NET MVC leverages the concept of convention over configuration: when the application starts up, ASP.NET MVC dis- covers all of the application’s controllers by searching through the available assemblies for classes that implement the System.Web.Mvc.IController interface (or derive from a class that implements this interface, such as System.Web.Mvc.Controller) and whose class names end with the suffix Controller. When the routing framework uses this list to figure out which controllers it has access to, it chops off the Controller suffix from all of the controller class names. So, whenever you need to refer to a controller, you do so by its shortened name, e.g., AuctionsController is referred to as Auctions, and Home Controller becomes Home. Routing | 17

What’s more, the controller and action values in a route are not case-sensitive. This means that each of these requests—/Auctions/Recent, /auctions/Recent, /auctions/ recent, or even /aucTionS/rEceNt—will successfully resolve to the Recent action in the AuctionsController. URL route patterns are relative to the application root, so they do not need to start with a forward slash (/) or a virtual path designator (~/). Route patterns that include these characters are invalid and will cause the routing system to throw an exception. As you may have noticed, URL routes can contain a wealth of information that the routing engine is able to extract. In order to process an ASP.NET MVC request, however, the routing engine must be able to determine two crucial pieces of information: the controller and the action. The routing engine can then pass these values to the ASP.NET MVC runtime to create and execute the specified action of the appropriate controller. Controllers In the context of the MVC architectural pattern, a controller responds to user input (e.g., a user clicking a Save button) and collaborates between the model, view, and (quiteoften)dataaccesslayers.InanASP.NETMVCapplication,controllersareclasses that contain methods that are called by the routing framework to process a request. To see an example of an ASP.NET MVC controller, take a look at the HomeController class found in Controllers/HomeController.cs: using System.Web.Mvc; namespace Ebuy.Website.Controllers { public class HomeController : Controller { public ActionResult Index() { ViewBag.Message = "Your app description page."; return View(); } public ActionResult About() { ViewBag.Message = "Your quintessential app description page."; return View(); } public ActionResult Contact() 18 | Chapter 1: Fundamentals of ASP.NET MVC

{ ViewBag.Message = "Your quintessential contact page."; return View(); } } } Controller Actions As you can see, controller classes themselves aren’t very special; that is, they don’t look much different from any other .NET class. In fact, it’s the methods in controller classes—referred to as controller actions—that do all the heavy lifting that’s involved in processing requests. You’ll often hear the terms controller and controller action used some- what interchangeably, even throughout this book. This is because the MVC pattern makes no differentiation between the two. However, the ASP.NET MVC Framework is mostly concerned with controller actions since they contain the actual logic to process the request. For instance, the HomeController class we just looked at contains three actions: Index, About, and Contact. Thus, given the default route pattern {controller}/{action}/ {id}, when a request is made to the URL /Home/About, the routing framework determines that it is the About() method of the HomeController class that should process the request. The ASP.NET MVC Framework then creates a new instance of the Home Controller class and executes its About() method. In this case, the About() method is pretty simple: it passes data to the view via the ViewBag property (more on that later), and then tells the ASP.NET MVC Framework to display the view named “About” by calling the View() method, which returns an ActionResult of type ViewResult. Action Results It is very important to note that it is the controller’s job to tell the ASP.NET MVC Framework what it should do next, but not how to do it. This communication occurs through the use of +ActionResult+s, the return values which every controller action is expected to provide. For example, when a controller decides to show a view, it tells the ASP.NET MVC Framework to show the view by returning a ViewResult. It does not render the view itself. This loose coupling is another great example of separation of concerns in action (what to do versus how it should be done). Controllers | 19

Despite the fact that every controller action needs to return an ActionResult, you will rarely be creating them manually. Instead, you’ll usually rely on the helper methods that the System.Web.Mvc.Controller base class provides, such as: Content() Returns a ContentResult that renders arbitrary text, e.g., “Hello, world!” File() Returns a FileResult that renders the contents of a file, e.g., a PDF. HttpNotFound() Returns an HttpNotFoundResult that renders a 404 HTTP status code response. JavaScript():: Returns a JavaScriptResult that renders JavaScript, e.g., “function hello() { alert(Hello, World!); }”. Json() Returns a JsonResult that serializes an object and renders it in JavaScript Object Notation (JSON) format, e.g., “{ “Message”: Hello, World! }”. PartialView() Returns a PartialViewResult that renders only the content of a view (i.e., a view without its layout). Redirect() Returns a RedirectResult that renders a 302 (temporary) status code to redirect the user to a given URL, e.g., “302 http://www.ebuy.com/auctions/recent”. This method has a sibling, RedirectPermanent(), that also returns a RedirectResult, but uses HTTP status code 301 to indicate a permanent redirect rather than a temporary one. RedirectToAction() and RedirectToRoute() Act just like the Redirect() helper, only the framework dynamically determines the external URL by querying the routing engine. Like the Redirect() helper, these two helpers also have permanent redirect variants: RedirectToActionPermanent() and RedirectToRoutePermanent(). View() Returns a ViewResult that renders a view. As you can tell from this list, the framework provides an action result for just about any situation you need to support, and, if it doesn’t, you are free to create your own! 20 | Chapter 1: Fundamentals of ASP.NET MVC

Though all controller actions are required to provide an ActionResult that indicates the next steps that should be taken to process the request, not all controller actions need to specify ActionResult as their return type. Controller actions can specify any return type that derives from ActionResult, or even any other type. When the ASP.NET MVC Framework comes across a controller action that returns a non-ActionResult type, it automatically wraps the value in a ContentResult and renders the value as raw content. Action Parameters Controller actions are—when it comes down to it—just like any other method. In fact, a controller action can even specify parameters that ASP.NET MVC populates, using information from the request, when it executes. This functionality is called model binding, and it is one of ASP.NET MVC’s most powerful and useful features. Before diving into how model binding works, first take a step back and consider an example of the “traditional” way of interacting with request values: public ActionResult Create() { var auction = new Auction() { Title = Request["title"], CurrentPrice = Decimal.Parse(Request["currentPrice"]), StartTime = DateTime.Parse(Request["startTime"]), EndTime = DateTime.Parse(Request["endTime"]), }; // ... } The controller action in this particular example creates and populates the properties of a new Auction object with values taken straight from the request. Since some of Auction’s properties are defined as various primitive, non-string types, the action also needs to parse each of those corresponding request values into the proper type. This example may seem simple and straightforward, but it’s actually quite frail: if any of the parsing attempts fails, the entire action will fail. Switching to the various Try Parse() methods may help avoid most exceptions, but applying these methods also means additional code. The side effect of this approach is that every action is very explicit. The downside to writing such explicit code is that it puts the burden on you, the developer, to perform all the work and to remember to perform this work every time it is required. A larger amount of code also tends to obscure the real goal: in this example, adding a new Auction to the system. Controllers | 21

Model binding basics Not only does model binding avoid all of this explicit code, it is also very easy to apply. So easy, in fact, that you don’t even need to think about it. For example, here’s the same controller action as before, this time using model-bound method parameters: public ActionResult Create( string title, decimal currentPrice, DateTime startTime, DateTime endTime ) { var auction = new Auction() { Title = title, CurrentPrice = currentPrice, StartTime = startTime, EndTime = endTime, }; // ... } Now, instead of retrieving the values from the Request explicitly, the action declares them as parameters. When the ASP.NET MVC framework executes this method, it attempts to populate the action’s parameters using the same values from the request that the previous example showed. Note that—even though we’re not accessing the Request dictionary directly—the parameter names are still very important, because they still correspond to values from in the Request. The Request object isn’t the only place the ASP.NET MVC model binder gets its values from, however. Out of the box, the framework looks in several places, such as route data, query string parameters, form post values, and even serialized JSON objects. For example, the following snippet retrieves the id value from the URL simply by declaring a parameter with the same name: Example 1-1. Retrieving the id from a URL (e.g. /auctions/auction/123) public ActionResult Auction(long id) { var context = new EBuyContext(); var auction = context.Auctions.FirstOrDefault(x => x.Id == id); return View("Auction", auction); } Where and how the ASP.NET MVC model binder finds these values is actually quite configurable and even extensible. See Chapter 8 for an in- depth discussion of ASP.NET MVC model binding. 22 | Chapter 1: Fundamentals of ASP.NET MVC

Exploring the Variety of Random Documents with Different Content

The Project Gutenberg eBook of A way of life

This ebook is for the use of anyone anywhere in the United States and most other parts of the world at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this ebook or online at www.gutenberg.org. If you are not located in the United States, you will have to check the laws of the country where you are located before using this eBook. Title: A way of life An address to Yale students Sunday evening, April 20th, 1913 Author: Sir William Osler Release date: March 6, 2024 [eBook #73116] Language: English Original publication: London: Constable & Company, 1913 Credits: Al Haines *** START OF THE PROJECT GUTENBERG EBOOK A WAY OF LIFE ***

A WAY OF LIFE An Address to Yale Students Sunday evening, April 20th, 1913 By WILLIAM OSLER LONDON CONSTABLE & COMPANY LTD. 1913 What each day needs that shall thou ask, Each day will set its proper task. Goethe. FELLOW STUDENTS—

Every man has a philosophy of life in thought, in word, or in deed, worked out in himself unconsciously. In possession of the very best, he may not know of its existence; with the very worst he may pride himself as a paragon. As it grows with the growth it cannot be taught to the young in formal lectures. What have bright eyes, red blood, quick breath and taut muscles to do with philosophy? Did not the great Stagirite say that young men were unfit students of it?—they will hear as though they heard not, and to no profit. Why then should I trouble you? Because I have a message that may be helpful. It is not philosophical, nor is it strictly moral or religious, one or other of which I was told my address should be, and yet in a way it is all three. It is the oldest and the freshest, the simplest and the most useful, so simple indeed is it that some of you may turn away disappointed as was Naaman the Syrian when told to go wash in Jordan and be clean. You know those composite tools, to be bought for 50 cents, with one handle to fit a score or more of instruments. The workmanship is usually bad, so bad, as a rule, that you will not find an example in any good carpenter's shop; but the boy has one, the chauffeur slips one into his box, and the sailor into his kit, and there is one in the odds-and-ends drawer of the pantry of every well- regulated family. It is simply a handy thing about the house, to help over the many little difficulties of the day. Of this sort of philosophy I wish to make you a present—a handle to fit your life tools. Whether the workmanship is Sheffield or shoddy, this helve will fit anything from a hatchet to a corkscrew. My message is but a word, a Way, an easy expression of the experience of a plain man whose life has never been worried by any philosophy higher than that of the shepherd in As You Like It. I wish to point out a path in which the wayfaring man, though a fool, cannot err; not a system to be worked out painfully only to be discarded, not a formal scheme, simply a habit as easy—or as hard!—to adopt as any other habit, good or bad. I

A few years ago a Xmas card went the rounds, with the legend "Life is just one 'denied' thing after another," which, in more refined language, is the same as saying "Life is a habit," a succession of actions that become more or less automatic. This great truth, which lies at the basis of all actions, muscular or psychic, is the keystone of the teaching of Aristotle, to whom the formation of habits was the basis of moral excellence. "In a word, habits of any kind are the result of actions of the same kind; and so what we have to do, is to give a certain character to these particular actions" (Ethics). Lift a seven months old baby to his feet—see him tumble on his nose. Do the same at twelve months—he walks. At two years he runs. The muscles and the nervous system have acquired the habit. One trial after another, one failure after another, has given him power. Put your finger in a baby's mouth, and he sucks away in blissful anticipation of a response to a mammalian habit millions of years old. And we can deliberately train parts of our body to perform complicated actions with unerring accuracy. Watch that musician playing a difficult piece. Batteries, commutators, multipliers, switches, wires innumerable control those nimble fingers, the machinery of which may be set in motion as automatically as in a pianola, the player all the time chatting as if he had nothing to do in controlling the apparatus— habit again, the gradual acquisition of power by long practice and at the expense of many mistakes. The same great law reaches through mental and moral states. "Character," which partakes of both, in Plutarch's words, is "long-standing habit." Now the way of life that I preach is a habit to be acquired gradually by long and steady repetition. It is the practice of living for the day only, and for the day's work, Life in day-tight compartments. "Ah," I hear you say, "that is an easy matter, simple as Elisha's advice!" Not as I shall urge it, in words which fail to express the depth of my feelings as to its value. I started life in the best of all environments—in a parsonage, one of nine children. A man who has filled Chairs in four universities, has written a successful book, and has been asked to lecture at Yale, is supposed popularly to have brains of a special quality. A few of my intimate friends really know the truth about me, as I know it! Mine, in good faith I say it, are of the most mediocre character. But what about those professorships, etc.? Just habit, a way of life, an outcome of the day's work, the vital importance of which I wish to impress upon you with all the force at my command.

Dr. Johnson remarked upon the trifling circumstances by which men's lives are influenced, "not by an ascendant planet, a predominating humour, but by the first book which they read, some early conversation which they have heard, or some accident which excited ardour and enthusiasm." This was my case in two particulars. I was diverted to the Trinity College School, then at Weston, Ontario, by a paragraph in the circular stating that the senior boys would go into the drawing-room in the evenings, and learn to sing and dance—vocal and pedal accomplishments for which I was never designed; but like Saul seeking his asses, I found something more valuable, a man of the White of Selborne type, who knew nature, and who knew how to get boys interested in it.[1] The other happened in the summer of 1871, when I was attending the Montreal General Hospital. Much worried as to the future, partly about the final examination, partly as to what I should do afterwards, I picked up a volume of Carlyle, and on the page I opened there was the familiar sentence—"Our main business is not to see what lies dimly at a distance, but to do what lies clearly at hand." A commonplace sentiment enough, but it hit and stuck and helped, and was the starting-point of a habit that has enabled me to utilize to the full the single talent entrusted to me. [1] The Rev. W. A. Johnson, the founder of the school. II The workers in Christ's vineyard were hired by the day; only for this day are we to ask for our daily bread, and we are expressly bidden to take no thought for the morrow. To the modern world these commands have an Oriental savour, counsels of perfection akin to certain of the Beatitudes, stimuli to aspiration, not to action. I am prepared on the contrary to urge the literal acceptance of the advice, not in the mood of Ecclesiastes—"Go to now, ye that say to-day or to-morrow we will go into such a city, and

continue there a year, and buy and sell and get gain; whereas ye know not what shall be on the morrow"; not in the Epicurean spirit of Omar with his "jug of wine and Thou," but in the modernist spirit, as a way of life, a habit, a strong enchantment, at once against the mysticism of the East and the pessimism that too easily besets us. Change that hard saying "Sufficient unto the day is the evil thereof" into "the goodness thereof," since the chief worries of life arise from the foolish habit of looking before and after. As a patient with double vision from some transient unequal action of the muscles of the eye finds magical relief from well-adjusted glasses, so, returning to the clear binocular vision of to-day, the over-anxious student finds peace when he looks neither backward to the past nor forward to the future. I stood on the bridge of one of the great liners, ploughing the ocean at 25 knots. "She is alive," said my companion, "in every plate; a huge monster with brain and nerves, an immense stomach, a wonderful heart and lungs, and a splendid system of locomotion." Just at that moment a signal sounded, and all over the ship the water-tight compartments were closed. "Our chief factor of safety," said the Captain. "In spite of the Titanic," I said. "Yes," he replied, "in spite of the Titanic." Now each one of you is a much more marvellous organization than the great liner, and bound on a longer voyage. What I urge is that you so learn to control the machinery as to live with "day-tight compartments" as the most certain way to ensure safety on the voyage. Get on the bridge, and see that at least the great bulkheads are in working order. Touch a button and hear, at every level of your life, the iron doors shutting out the Past—the dead yesterdays. Touch another and shut off, with a metal curtain, the Future—the unborn to- morrows. Then you are safe,—safe for to-day! Read the old story in the Chambered Nautilus, so beautifully sung by Oliver Wendell Holmes, only change one line to "Day after day beheld the silent toil." Shut off the past! Let the dead past bury its dead. So easy to say, so hard to realize! The truth is, the past haunts us like a shadow. To disregard it is not easy. Those blue eyes of your grandmother, that weak chin of your grandfather, have mental and moral counterparts in your make-up. Generations of ancestors, brooding over "Providence, Foreknowledge, Will and Fate—Fixed fate, free will, foreknowledge, absolute," may have bred a New England conscience, morbidly sensitive, to heal which some of you had rather sing the 51st

Psalm than follow Christ into the slums. Shut out the yesterdays, which have lighted fools the way to dusty death, and have no concern for you personally, that is, consciously. They are there all right, working daily in us, but so are our livers and our stomachs. And the past, in its unconscious action on our lives, should bother us as little as they do. The petty annoyances, the real and fancied slights, the trivial mistakes, the disappointments, the sins, the sorrows, even the joys—bury them deep in the oblivion of each night. Ah! but it is just then that to so many of us the ghosts of the past, Night-riding Incubi Troubling the fantasy, come in troops, and pry open the eyelids, each one presenting a sin, a sorrow, a regret. Bad enough in the old and seasoned, in the young these demons of past sins may be a terrible affliction, and in bitterness of heart many a one cries with Eugene Aram, "Oh God! Could I so close my mind, and clasp it with a clasp." As a vaccine against all morbid poisons left in the system by the infections of yesterday, I offer "a way of life." "Undress," as George Herbert says, "your soul at night," not by self-examination, but by shedding, as you do your garments, the daily sins whether of omission or of commission, and you will wake a free man, with a new life. To look back, except on rare occasions for stock-taking, is to risk the fate of Lot's wife. Many a man is handicapped in his course by a cursed combination of retro- and intro-spection, the mistakes of yesterday paralysing the efforts of to- day, the worries of the past hugged to his destruction, and the worm Regret allowed to canker the very heart of his life. To die daily, after the manner of St. Paul, ensures the resurrection of a new man, who makes each day the epitome of a life. III

The load of to-morrow, added to that of yesterday, carried to-day makes the strongest falter. Shut off the future as tightly as the past. No dreams, no visions, no delicious fantasies, no castles in the air, with which, as the old song so truly says, "hearts are broken, heads are turned." To youth, we are told, belongs the future, but the wretched to-morrow that so plagues some of us has no certainty, except through to-day. Who can tell what a day may bring forth? Though its uncertainty is a proverb, a man may carry its secret in the hollow of his hand. Make a pilgrimage to Hades with Ulysses, draw the magic circle, perform the rites, and then ask Tiresias the question. I have had the answer from his own lips. The future is to-day,—there is no to- morrow! The day of a man's salvation is now—the life of the present, of to- day, lived earnestly, intently, without a forward-looking thought, is the only insurance for the future. Let the limit of your horizon be a twenty-four hour circle. On the title page of one of the great books of science, the Discours de la Méthode of Descartes (1637) is a vignette showing a man digging in a garden with his face towards the earth, on which rays of light are streaming from the heavens; beneath is the legend "Fac et Spera." 'Tis a good attitude and a good motto. Look heavenward, if you wish, but never to the horizon —that way danger lies. Truth is not there, happiness is not there, certainty is not there, but the falsehoods, the frauds, the quackeries, the ignes fatui which have deceived each generation—all beckon from the horizon, and lure the men not content to look for the truth and happiness that tumble out at their feet. Once while at College climb a mountain-top, and get a general outlook of the land, and make it the occasion perhaps of that careful examination of yourself, that inquisition which Descartes urges every man to hold once in a lifetime,—not oftener. Waste of energy, mental distress, nervous worries dog the steps of a man who is anxious about the future. Shut close, then, the great fore and aft bulkheads, and prepare to cultivate the habit of a life of Day-Tight Compartments. Do not be discouraged,—like every other habit, the acquisition takes time, and the way is one you must find for yourselves. I can only give general directions and encouragement, in the hope that while the green years are on your heads, you may have the courage to persist.

IV Now, for the day itself! What first? Be your own daysman! and sigh not with Job for any mysterious intermediary, but prepare to lay your own firm hand upon the helm. Get into touch with the finite, and grasp in full enjoyment that sense of capacity in a machine working smoothly. Join the whole creation of animate things in a deep, heartfelt joy that you are alive, that you see the sun, that you are in this glorious earth which nature has made so beautiful, and which is yours to conquer and to enjoy. Realise, in the words of Browning, that "There's a world of capability for joy spread round about us, meant for us, inviting us." What are the morning sensations?—for they control the day. Some of us are congenitally unhappy during the early hours; but the young man who feels on awakening that life is a burden or a bore has been neglecting his machine, driving it too hard, stoking the engines too much, or not cleaning out the ashes and clinkers. Or he has been too much with the Lady Nicotine, or fooling with Bacchus, or, worst of all, with the younger Aphrodite—all "messengers of strong prevailment in unhardened youth." To have a sweet outlook on life you must have a clean body. As I look on the clear-cut, alert, earnest features, and the lithe, active forms of our college men, I sometimes wonder whether or not Socrates and Plato would find the race improved. I am sure they would love to look on such a gathering as this. Make their ideal yours—the fair mind in the fair body. The one cannot be sweet and clean without the other, and you must realise, with Rabbi Ben Ezra, the great truth that flesh and soul are mutually helpful. The morning outlook—which really makes the day—is largely a question of a clean machine—of physical morality in the wide sense of the term. "C'est l'estomac qui fait les heureux," as Voltaire says; no dyspeptic can have a sane outlook on life; and a man whose bodily functions are impaired has a lowered moral resistance. To keep the body fit is a help in keeping the mind pure, and the sensations of the first few hours of the day are the best test of its normal state. The clean tongue, the clear head, and the bright eye are birth-rights of each day. Just as the late Professor Marsh would diagnose an unknown animal from a single bone, so can the day be predicted from the first waking hour. The start is everything,

as you well know, and to make a good start you must feel fit. In the young, sensations of morning slackness come most often from lack of control of the two primal instincts—biologic habits—the one concerned with the preservation of the individual, the other with the continuance of the species. Yale students should by this time be models of dietetic propriety, but youth does not always reck the rede of the teacher; and I dare say that here, as elsewhere, careless habits of eating are responsible for much mental disability. My own rule of life has been to cut out unsparingly any article of diet that had the bad taste to disagree with me, or to indicate in any way that it had abused the temporary hospitality of the lodging which I had provided. To drink, nowadays, but few students become addicted, but in every large body of men a few are to be found whose incapacity for the day results from the morning clogging of nocturnally-flushed tissues. As moderation is very hard to reach, and as it has been abundantly shown that the best of mental and physical work may be done without alcohol in any form, the safest rule for the young man is that which I am sure most of you follow— abstinence. A bitter enemy to the bright eye and the clear brain of the early morning is tobacco when smoked to excess, as it is now by a large majority of students. Watch it, test it, and if need be, control it. That befogged, woolly sensation reaching from the forehead to the occiput, that haziness of memory, that cold fish-like eye, that furred tongue, and last week's taste in the mouth—too many of you know them—I know them—they often come from too much tobacco. The other primal instinct is the heavy burden of the flesh which Nature puts on all of us to ensure a continuation of the species. To drive Plato's team taxes the energies of the best of us. One of the horses is a raging, untamed devil, who can only be brought into subjection by hard fighting and severe training. This much you all know as men: once the bit is between his teeth the black steed Passion will take the white horse Reason with you and the chariot rattling over the rocks to perdition. With a fresh, sweet body you can start aright without those feelings of inertia that so often, as Goethe says, make the morning's lazy leisure usher in a useless day. Control of the mind as a working machine, the adaptation in it of habit, so that its action becomes almost as automatic as walking, is the end of education—and yet how rarely reached! It can be accomplished with deliberation and repose, never with hurry and worry. Realise how much time there is, how long the day is. Realise that you have sixteen

waking hours, three or four of which at least should be devoted to making a silent conquest of your mental machinery. Concentration, by which is grown gradually the power to wrestle successfully with any subject, is the secret of successful study. No mind however dull can escape the brightness that comes from steady application. There is an old saying, "Youth enjoyeth not, for haste"; but worse than this, the failure to cultivate the power of peaceful concentration is the greatest single cause of mental breakdown. Plato pities the young man who started at such a pace that he never reached the goal. One of the saddest of life's tragedies is the wreckage of the career of the young collegian by hurry, hustle, bustle and tension—the human machine driven day and night, as no sensible fellow would use his motor. Listen to the words of a master in Israel, William James: "Neither the nature nor the amount of our work is accountable for the frequency and severity of our breakdowns, but their cause lies rather in those absurd feelings of hurry and having no time, in that breathlessness and tension, that anxiety of feature and that solicitude of results, that lack of inner harmony and ease, in short, by which the work with us is apt to be accompanied, and from which a European who would do the same work would, nine out of ten times, be free." Es bildet ein Talent sich in der Stille, but it need not be for all day. A few hours out of the sixteen will suffice, only let them be hours of daily dedication—in routine, in order and in system, and day by day you will gain in power over the mental mechanism, just as the child does over the spinal marrow in walking, or the musician over the nerve centres. Aristotle somewhere says that the student who wins out in the fight must be slow in his movements, with voice deep, and slow speech, and he will not be worried over trifles which make people speak in shrill tones and use rapid movements. Shut close in hour-tight compartments, with the mind directed intensely upon the subject in hand, you will acquire the capacity to do more and more, you will get into training; and once the mental habit is established, you are safe for life. Concentration is an art of slow acquisition, but little by little the mind is accustomed to habits of slow eating and careful digestion, by which alone you escape the "mental dyspepsy" so graphically described by Lowell in the Fable for Critics. Do not worry your brains about that bugbear Efficiency, which, sought consciously and with effort, is just one of those elusive qualities very apt to be missed. The man's college output is never to be

gauged at sight; all the world's coarse thumb and finger may fail to plumb his most effective work, the casting of the mental machinery of self- education, the true preparation for a field larger than the college campus. Four or five hours daily—it is not much to ask; but one day must tell another, one week certify another, one month bear witness to another of the same story, and you will acquire a habit by which the one-talent man will earn a high interest, and by which the ten-talent man may at least save his capital. Steady work of this sort gives a man a sane outlook on the world. No corrective so valuable to the weariness, the fever and the fret that are so apt to wring the heart of the young. This is the talisman, as George Herbert says, The famous stone That turneth all to gold, and with which, to the eternally recurring question, What is Life? you answer, I do not think—I act it; the only philosophy that brings you in contact with its real values and enables you to grasp its hidden meaning. Over the Slough of Despond, past Doubting Castle and Giant Despair, with this talisman you may reach the Delectable Mountains, and those Shepherds of the Mind—Knowledge, Experience, Watchful and Sincere. Some of you may think this to be a miserable Epicurean doctrine—no better than that so sweetly sung by Horace:— Happy the man—and Happy he alone, He who can call to-day his own, He who secure within can say, To-morrow, do thy worst—for I have lived to-day. I do not care what you think, I am simply giving you a philosophy of life that I have found helpful in my work, useful in my play. Walt Whitman, whose physician I was for some years, never spoke to me much of his poems, though occasionally he would make a quotation; but I remember late one summer afternoon as we sat in the window of his little house in

Camden there passed a group of workmen whom he greeted in his usual friendly way. And then he said: "Ah, the glory of the day's work, whether with hand or brain! I have tried To exalt the present and the real, To teach the average man the glory of his daily work or trade." In this way of life each one of you may learn to drive the straight furrow and so come to the true measure of a man. V With body and mind in training, what remains? Do you remember that most touching of all incidents in Christ's ministry, when the anxious ruler Nicodemus came by night, worried lest the things that pertained to his everlasting peace were not a part of his busy and successful life? Christ's message to him is His message to the world—never more needed than at present: "Ye must be born of the spirit." You wish to be with the leaders—as Yale men it is your birthright—know the great souls that make up the moral radium of the world. You must be born of their spirit, initiated into their fraternity, whether of the spiritually-minded followers of the Nazarene or of that larger company, elect from every nation, seen by St. John. Begin the day with Christ and His prayer—you need no other. Creedless, with it you have religion; creed-stuffed, it will leaven any theological dough in which you stick. As the soul is dyed by the thoughts, let no day pass without contact with the best literature of the world. Learn to know your Bible, though not perhaps as your fathers did. In forming

character and in shaping conduct, its touch has still its ancient power. Of the kindred of Ram and sons of Elihu, you should know its beauties and its strength. Fifteen or twenty minutes day by day will give you fellowship with the great minds of the race, and little by little as the years pass you extend your friendship with the immortal dead. They will give you faith in your own day. Listen while they speak to you of the fathers. But each age has its own spirit and ideas, just as it has its own manners and pleasures. You are right to believe that yours is the best University, at its best period. Why should you look back to be shocked at the frowsiness and dullness of the students of the seventies or even of the nineties? And cast no thought forward, lest you reach a period when you and yours will present to your successors the same dowdiness of clothes and times. But while change is the law, certain great ideas flow fresh through the ages, and control us effectually as in the days of Pericles. Mankind, it has been said, is always advancing, man is always the same. The love, hope, fear and faith that make humanity, and the elemental passions of the human heart, remain unchanged, and the secret of inspiration in any literature is the capacity to touch the cord that vibrates in a sympathy that knows nor time nor place. The quiet life in day-tight compartments will help you to bear your own and others' burdens with a light heart. Pay no heed to the Batrachians who sit croaking idly by the stream. Life is a straight, plain business, and the way is clear, blazed for you by generations of strong men, into whose labours you enter and whose ideals must be your inspiration. In my mind's eye I can see you twenty years hence—resolute-eyed, broad-headed, smooth-faced men who are in the world to make a success of life; but to whichever of the two great types you belong, whether controlled by emotion or by reason, you will need the leaven of their spirit, the only leaven potent enough to avert that only too common Nemesis to which the Psalmist refers: "He gave them their heart's desire, but sent leanness withal into their souls." I quoted Dr. Johnson's remark about the trivial things that influence. Perhaps this slight word of mine may help some of you so to number your days that you may apply your hearts unto wisdom.

WILLIAM BRENDON AND SON, LTD. PRINTERS, PLYMOUTH

*** END OF THE PROJECT GUTENBERG EBOOK A WAY OF LIFE *** Updated editions will replace the previous one—the old editions will be renamed. Creating the works from print editions not protected by U.S. copyright law means that no one owns a United States copyright in these works, so the Foundation (and you!) can copy and distribute it in the United States without permission and without paying copyright royalties. Special rules, set forth in the General Terms of Use part of this license, apply to copying and distributing Project Gutenberg™ electronic works to protect the PROJECT GUTENBERG™ concept and trademark. Project Gutenberg is a registered trademark, and may not be used if you charge for an eBook, except by following the terms of the trademark license, including paying royalties for use of the Project Gutenberg trademark. If you do not charge anything for copies of this eBook, complying with the trademark license is very easy. You may use this eBook for nearly any purpose such as creation of derivative works, reports, performances and research. Project Gutenberg eBooks may be modified and printed and given away—you may do practically ANYTHING in the United States with eBooks not protected by U.S. copyright law. Redistribution is subject to the trademark license, especially commercial redistribution. START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE

PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK To protect the Project Gutenberg™ mission of promoting the free distribution of electronic works, by using or distributing this work (or any other work associated in any way with the phrase “Project Gutenberg”), you agree to comply with all the terms of the Full Project Gutenberg™ License available with this file or online at www.gutenberg.org/license. Section 1. General Terms of Use and Redistributing Project Gutenberg™ electronic works 1.A. By reading or using any part of this Project Gutenberg™ electronic work, you indicate that you have read, understand, agree to and accept all the terms of this license and intellectual property (trademark/copyright) agreement. If you do not agree to abide by all the terms of this agreement, you must cease using and return or destroy all copies of Project Gutenberg™ electronic works in your possession. If you paid a fee for obtaining a copy of or access to a Project Gutenberg™ electronic work and you do not agree to be bound by the terms of this agreement, you may obtain a refund from the person or entity to whom you paid the fee as set forth in paragraph 1.E.8. 1.B. “Project Gutenberg” is a registered trademark. It may only be used on or associated in any way with an electronic work by people who agree to be bound by the terms of this agreement. There are a few things that you can do with most Project Gutenberg™ electronic works even without complying with the full terms of this agreement. See paragraph 1.C below. There are a lot of things you can do with Project Gutenberg™ electronic works if you follow the terms of this agreement and help preserve free future access to Project Gutenberg™ electronic works. See paragraph 1.E below.

1.C. The Project Gutenberg Literary Archive Foundation (“the Foundation” or PGLAF), owns a compilation copyright in the collection of Project Gutenberg™ electronic works. Nearly all the individual works in the collection are in the public domain in the United States. If an individual work is unprotected by copyright law in the United States and you are located in the United States, we do not claim a right to prevent you from copying, distributing, performing, displaying or creating derivative works based on the work as long as all references to Project Gutenberg are removed. Of course, we hope that you will support the Project Gutenberg™ mission of promoting free access to electronic works by freely sharing Project Gutenberg™ works in compliance with the terms of this agreement for keeping the Project Gutenberg™ name associated with the work. You can easily comply with the terms of this agreement by keeping this work in the same format with its attached full Project Gutenberg™ License when you share it without charge with others. 1.D. The copyright laws of the place where you are located also govern what you can do with this work. Copyright laws in most countries are in a constant state of change. If you are outside the United States, check the laws of your country in addition to the terms of this agreement before downloading, copying, displaying, performing, distributing or creating derivative works based on this work or any other Project Gutenberg™ work. The Foundation makes no representations concerning the copyright status of any work in any country other than the United States. 1.E. Unless you have removed all references to Project Gutenberg: 1.E.1. The following sentence, with active links to, or other immediate access to, the full Project Gutenberg™ License must appear prominently whenever any copy of a Project Gutenberg™ work (any work on which the phrase “Project Gutenberg” appears, or with which the phrase “Project Gutenberg” is associated) is accessed, displayed, performed, viewed, copied or distributed:

This eBook is for the use of anyone anywhere in the United States and most other parts of the world at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org. If you are not located in the United States, you will have to check the laws of the country where you are located before using this eBook. 1.E.2. If an individual Project Gutenberg™ electronic work is derived from texts not protected by U.S. copyright law (does not contain a notice indicating that it is posted with permission of the copyright holder), the work can be copied and distributed to anyone in the United States without paying any fees or charges. If you are redistributing or providing access to a work with the phrase “Project Gutenberg” associated with or appearing on the work, you must comply either with the requirements of paragraphs 1.E.1 through 1.E.7 or obtain permission for the use of the work and the Project Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9. 1.E.3. If an individual Project Gutenberg™ electronic work is posted with the permission of the copyright holder, your use and distribution must comply with both paragraphs 1.E.1 through 1.E.7 and any additional terms imposed by the copyright holder. Additional terms will be linked to the Project Gutenberg™ License for all works posted with the permission of the copyright holder found at the beginning of this work. 1.E.4. Do not unlink or detach or remove the full Project Gutenberg™ License terms from this work, or any files containing a part of this work or any other work associated with Project Gutenberg™. 1.E.5. Do not copy, display, perform, distribute or redistribute this electronic work, or any part of this electronic work, without prominently displaying the sentence set forth in paragraph 1.E.1

with active links or immediate access to the full terms of the Project Gutenberg™ License. 1.E.6. You may convert to and distribute this work in any binary, compressed, marked up, nonproprietary or proprietary form, including any word processing or hypertext form. However, if you provide access to or distribute copies of a Project Gutenberg™ work in a format other than “Plain Vanilla ASCII” or other format used in the official version posted on the official Project Gutenberg™ website (www.gutenberg.org), you must, at no additional cost, fee or expense to the user, provide a copy, a means of exporting a copy, or a means of obtaining a copy upon request, of the work in its original “Plain Vanilla ASCII” or other form. Any alternate format must include the full Project Gutenberg™ License as specified in paragraph 1.E.1. 1.E.7. Do not charge a fee for access to, viewing, displaying, performing, copying or distributing any Project Gutenberg™ works unless you comply with paragraph 1.E.8 or 1.E.9. 1.E.8. You may charge a reasonable fee for copies of or providing access to or distributing Project Gutenberg™ electronic works provided that: • You pay a royalty fee of 20% of the gross profits you derive from the use of Project Gutenberg™ works calculated using the method you already use to calculate your applicable taxes. The fee is owed to the owner of the Project Gutenberg™ trademark, but he has agreed to donate royalties under this paragraph to the Project Gutenberg Literary Archive Foundation. Royalty payments must be paid within 60 days following each date on which you prepare (or are legally required to prepare) your periodic tax returns. Royalty payments should be clearly marked as such and sent to the Project Gutenberg Literary Archive Foundation at the address specified in Section 4, “Information

about donations to the Project Gutenberg Literary Archive Foundation.” • You provide a full refund of any money paid by a user who notifies you in writing (or by e-mail) within 30 days of receipt that s/he does not agree to the terms of the full Project Gutenberg™ License. You must require such a user to return or destroy all copies of the works possessed in a physical medium and discontinue all use of and all access to other copies of Project Gutenberg™ works. • You provide, in accordance with paragraph 1.F.3, a full refund of any money paid for a work or a replacement copy, if a defect in the electronic work is discovered and reported to you within 90 days of receipt of the work. • You comply with all other terms of this agreement for free distribution of Project Gutenberg™ works. 1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™ electronic work or group of works on different terms than are set forth in this agreement, you must obtain permission in writing from the Project Gutenberg Literary Archive Foundation, the manager of the Project Gutenberg™ trademark. Contact the Foundation as set forth in Section 3 below. 1.F. 1.F.1. Project Gutenberg volunteers and employees expend considerable effort to identify, do copyright research on, transcribe and proofread works not protected by U.S. copyright law in creating the Project Gutenberg™ collection. Despite these efforts, Project Gutenberg™ electronic works, and the medium on which they may be stored, may contain “Defects,” such as, but not limited to, incomplete, inaccurate or corrupt data, transcription errors, a copyright or other intellectual property infringement, a defective or

damaged disk or other medium, a computer virus, or computer codes that damage or cannot be read by your equipment. 1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for the “Right of Replacement or Refund” described in paragraph 1.F.3, the Project Gutenberg Literary Archive Foundation, the owner of the Project Gutenberg™ trademark, and any other party distributing a Project Gutenberg™ electronic work under this agreement, disclaim all liability to you for damages, costs and expenses, including legal fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE. 1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you discover a defect in this electronic work within 90 days of receiving it, you can receive a refund of the money (if any) you paid for it by sending a written explanation to the person you received the work from. If you received the work on a physical medium, you must return the medium with your written explanation. The person or entity that provided you with the defective work may elect to provide a replacement copy in lieu of a refund. If you received the work electronically, the person or entity providing it to you may choose to give you a second opportunity to receive the work electronically in lieu of a refund. If the second copy is also defective, you may demand a refund in writing without further opportunities to fix the problem. 1.F.4. Except for the limited right of replacement or refund set forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,

INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PURPOSE. 1.F.5. Some states do not allow disclaimers of certain implied warranties or the exclusion or limitation of certain types of damages. If any disclaimer or limitation set forth in this agreement violates the law of the state applicable to this agreement, the agreement shall be interpreted to make the maximum disclaimer or limitation permitted by the applicable state law. The invalidity or unenforceability of any provision of this agreement shall not void the remaining provisions. 1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation, the trademark owner, any agent or employee of the Foundation, anyone providing copies of Project Gutenberg™ electronic works in accordance with this agreement, and any volunteers associated with the production, promotion and distribution of Project Gutenberg™ electronic works, harmless from all liability, costs and expenses, including legal fees, that arise directly or indirectly from any of the following which you do or cause to occur: (a) distribution of this or any Project Gutenberg™ work, (b) alteration, modification, or additions or deletions to any Project Gutenberg™ work, and (c) any Defect you cause. Section 2. Information about the Mission of Project Gutenberg™ Project Gutenberg™ is synonymous with the free distribution of electronic works in formats readable by the widest variety of computers including obsolete, old, middle-aged and new computers. It exists because of the efforts of hundreds of volunteers and donations from people in all walks of life. Volunteers and financial support to provide volunteers with the assistance they need are critical to reaching Project Gutenberg™’s goals and ensuring that the Project Gutenberg™ collection will

remain freely available for generations to come. In 2001, the Project Gutenberg Literary Archive Foundation was created to provide a secure and permanent future for Project Gutenberg™ and future generations. To learn more about the Project Gutenberg Literary Archive Foundation and how your efforts and donations can help, see Sections 3 and 4 and the Foundation information page at www.gutenberg.org. Section 3. Information about the Project Gutenberg Literary Archive Foundation The Project Gutenberg Literary Archive Foundation is a non-profit 501(c)(3) educational corporation organized under the laws of the state of Mississippi and granted tax exempt status by the Internal Revenue Service. The Foundation’s EIN or federal tax identification number is 64-6221541. Contributions to the Project Gutenberg Literary Archive Foundation are tax deductible to the full extent permitted by U.S. federal laws and your state’s laws. The Foundation’s business office is located at 809 North 1500 West, Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up to date contact information can be found at the Foundation’s website and official page at www.gutenberg.org/contact Section 4. Information about Donations to the Project Gutenberg Literary Archive Foundation Project Gutenberg™ depends upon and cannot survive without widespread public support and donations to carry out its mission of increasing the number of public domain and licensed works that can be freely distributed in machine-readable form accessible by the widest array of equipment including outdated equipment. Many

small donations ($1 to $5,000) are particularly important to maintaining tax exempt status with the IRS. The Foundation is committed to complying with the laws regulating charities and charitable donations in all 50 states of the United States. Compliance requirements are not uniform and it takes a considerable effort, much paperwork and many fees to meet and keep up with these requirements. We do not solicit donations in locations where we have not received written confirmation of compliance. To SEND DONATIONS or determine the status of compliance for any particular state visit www.gutenberg.org/donate. While we cannot and do not solicit contributions from states where we have not met the solicitation requirements, we know of no prohibition against accepting unsolicited donations from donors in such states who approach us with offers to donate. International donations are gratefully accepted, but we cannot make any statements concerning tax treatment of donations received from outside the United States. U.S. laws alone swamp our small staff. Please check the Project Gutenberg web pages for current donation methods and addresses. Donations are accepted in a number of other ways including checks, online payments and credit card donations. To donate, please visit: www.gutenberg.org/donate. Section 5. General Information About Project Gutenberg™ electronic works Professor Michael S. Hart was the originator of the Project Gutenberg™ concept of a library of electronic works that could be freely shared with anyone. For forty years, he produced and distributed Project Gutenberg™ eBooks with only a loose network of volunteer support.

Project Gutenberg™ eBooks are often created from several printed editions, all of which are confirmed as not protected by copyright in the U.S. unless a copyright notice is included. Thus, we do not necessarily keep eBooks in compliance with any particular paper edition. Most people start at our website which has the main PG search facility: www.gutenberg.org. This website includes information about Project Gutenberg™, including how to make donations to the Project Gutenberg Literary Archive Foundation, how to help produce our new eBooks, and how to subscribe to our email newsletter to hear about new eBooks.

Welcome to our website – the ideal destination for book lovers and knowledge seekers. With a mission to inspire endlessly, we offer a vast collection of books, ranging from classic literary works to specialized publications, self-development books, and children's literature. Each book is a new journey of discovery, expanding knowledge and enriching the soul of the reade Our website is not just a platform for buying books, but a bridge connecting readers to the timeless values of culture and wisdom. With an elegant, user-friendly interface and an intelligent search system, we are committed to providing a quick and convenient shopping experience. Additionally, our special promotions and home delivery services ensure that you save time and fully enjoy the joy of reading. Let us accompany you on the journey of exploring knowledge and personal growth! ebookfinal.com

Programming ASP NET MVC 4 Developing Real World Web Applications with ASP NET MVC 1st Edition Jess Chadwick

More Related Content

Similar to Programming ASP NET MVC 4 Developing Real World Web Applications with ASP NET MVC 1st Edition Jess Chadwick

Recently uploaded

Programming ASP NET MVC 4 Developing Real World Web Applications with ASP NET MVC 1st Edition Jess Chadwick