book

Programming Microsoft ASP.NET MVC

Name: Programming Microsoft ASP.NET MVC
Author: Dino Esposito
ISBN: 9780735681095

by Dino Esposito

February 2014

Intermediate to advanced

528 pages

14h 36m

English

Microsoft Press

Read now

Unlock full access

Dedication
Introduction
Who should read this bookAssumptionsWho should not read this bookOrganization of this bookSystem requirementsCode samplesInstalling the code samplesUsing the code samplesErrata & book supportWe want to hear from youStay in touch
I. ASP.NET MVC fundamentals
1. ASP.NET MVC controllers
Routing incoming requestsSimulating the ASP.NET MVC runtimeDefining the syntax of recognized URLsDefining the behavior of the HTTP handlerInvoking the HTTP handlerThe URL routing HTTP moduleSuperseding URL rewritingRouting the requestsThe internal structure of the URL routing moduleApplication routesURL patterns and routesDefining application routesProcessing routesRoute handlerHandling requests for physical filesPreventing routing for defined URLsAttribute routingThe controller classAspects of a controllerGranularity of controllersStateless componentsFurther layering is up to youHighly testableWriting controller classesFrom routing to controllersFrom routing to actionsActions and HTTP verbsAction methodsProcessing input dataGetting input data from the Request objectGetting input data from the routeGetting input data from multiple sourcesThe ValueProvider dictionaryProducing action resultsInside the ActionResult classPredefined action result typesThe mechanics of executing action resultsReturning HTML markupReturning JSON contentSummary
2. ASP.NET MVC views
The structure and behavior of a view engineThe mechanics of a view engineDetecting registered view enginesAnatomy of a view engineWho calls the view engine?The view objectDefinition of the view templateResolving the templateDefault conventions and foldersThe template for the viewThe master viewHTML helpersBasic helpersRendering HTML formsRendering input elementsAction linksPartial viewsThe HtmlHelper classTemplated helpersFlavors of a templated helperThe Display helpersThe Editor helpersCustom helpersThe structure of an HTML helperMvcHtmlString is better than just a stringA sample HTML helperA sample Ajax helperThe Razor view engineInside the view engineSearch locationsCode nuggetsSpecial expressions of code nuggetsConditional nuggetsThe Razor view objectDesigning a sample viewDefining the model for the viewDefining a master viewDefining sectionsDefault content for sectionsNested layoutsDeclarative HTML helpersCoding the viewModeling the viewThe ViewData dictionaryThe ViewBag dictionaryStrongly typed view modelsPackaging the view-model classesAdvanced featuresCustom view enginesRender actionsChild actionsSummary
3. The model-binding architecture
The input modelEvolving from the Web Forms input processingRole of server controlsRole of the view stateInput processing in ASP.NET MVCThe role of model bindersFlavors of a modelModel bindingModel-binding infrastructureAnalyzing the method’s signatureGetting the binder for the typeThe default model binderBinding primitive typesDealing with optional valuesValue providers and precedenceBinding complex typesBinding collectionsBinding collections of complex typesBinding content from uploaded filesCustomizable aspects of the default binderThe Bind attributeCreating whitelists of propertiesCreating blacklists of propertiesAliasing parameters by using a prefixAdvanced model bindingCustom type bindersCustomizing the default binderImplementing a model binder from scratchRegistering a custom binderA sample DateTime model binderThe displayed dataThe controller methodsCreating the DateTime binderSummary
4. Input forms
General patterns of data entryA classic Select-Edit-Post scenarioPresenting data and handling the selectionEditing dataSaving dataApplying the Post-Redirect-Get patternKeeping the URL and content synchronizedSplitting POST and GET actionsUpdating only via POSTSaving temporary data across redirectsAutomating the writing of input formsPredefined display and editor templatesAnnotating data members for displayDefault templates for data typesCustom templates for data typesRead-only membersCustom templates for model data typesTabular templatesDealing with nested modelsInput validationUsing data annotationsValidation provider infrastructureDecorating a model classDealing with enumerated typesControlling error messagesAdvanced data annotationsCross-property validationCreating custom validation attributesEnabling client-side validationCulture-based, client-side validationValidating properties remotelySelf-validationThe IValidatableObject interfaceBenefits of centralized validationThe IClientValidatable interfaceDynamic server-side validationSummary
II. ASP.NET MVC software design
5. Aspects of ASP.NET MVC applications
ASP.NET intrinsic objectsHTTP response and SEOPermanent redirectionDevising routes and URLsThe trailing slashManaging the session stateUsing the Session objectNever outside the controllerCaching dataThe bright side and dark side of the native Cache objectInjecting a caching serviceA better way of injecting a caching serviceDistributed cachingCaching the method responsePartial output cachingError handlingHandling program exceptionsHandling exceptions directlyOverriding the OnException methodUsing the HandleError attributeGlobal error handlingGlobal error handling from global.asaxGlobal error handling using an HTTP moduleIntercepting model-binding exceptionsHandling route exceptionsDealing with missing contentCatch-all routeSkipping IIS error-handling policiesLocalizationUsing localizable resourcesLocalizable textLocalizable filesReferencing embedded filesLocalizable viewsDealing with localizable applicationsAuto-adapting applicationsMultilingual applicationsChanging culture programmaticallyGetting localized data from a serviceSummary
6. Securing your application
Security in ASP.NET MVCAuthentication and authorizationConfiguring authentication in ASP.NET MVCRestricting access to action methodsAllowing anonymous callersHandling authorization for action methodsAuthorization and output cachingHiding critical user interface elementsSeparating authentication from authorizationAnonymous or not authorized?Authentication filtersImplementing a membership systemDefining a membership controllerValidating user credentialsIntegrating with the membership APIUsing the SimpleMembership APIIntegrating with the role APIASP.NET identityAuthenticating users by using ASP.NET IdentityThe Remember-Me feature and AjaxReproducing the problemSolving the problemExternal authentication servicesThe OpenID protocolIdentifying users through an OpenID providerOpenID vs. OAuthAuthenticating via social networksRegistering your application with TwitterEnabling social authentication in ASP.NET MVCStarting the authentication processDealing with the Twitter responseFrom authentication to membershipBeyond authenticationSummary

7. Design considerations for ASP.NET MVC controllers
Shaping up your controllerChoosing the right stereotypeRDD at a glanceBreaking down the execution of a requestActing as a “Controller”Acting as a “Coordinator”Fat-free controllersShort is always betterAction methods coded as view-model buildersWorker servicesImplementing a worker serviceDo we really need controllers?The ideal action method codeConnecting the presentation and back endThe Layered Architecture patternBeyond classic layersThe (idiomatic) presentation layerThe application layerThe domain layerExposing entities of the domainThe infrastructure layerInjecting data and services in layersThe Dependency Inversion PrincipleThe Service Locator patternThe Dependency Injection patternUsing tools for Inversion of ControlThe poor-man’s DIGaining control of the controller factoryRegistering a custom controller factoryBuilding a custom controller factoryA Unity-based controller factorySummary
8. Customizing ASP.NET MVC controllers
The extensibility model of ASP.NET MVCThe provider-based modelGallery of extensibility pointsA realistic scenario: alternate TempData storageUsing custom components in your applicationsThe Service Locator patternService Locator vs. Dependency InjectionSL in ASP.NET MVCDefining your dependency resolverAdding aspects to controllersAction filtersEmbedded and external filtersClassification of action filtersBuilt-in action filtersGlobal filtersGallery of action filtersAdding a response headerCompressing the responseView SelectorSpecial filtersAction name selectorsAction method selectorsRestricting a method to Ajax calls onlyRestricting a method to a given submit buttonBuilding a dynamic loader filterInterception points for filtersAdding an action filter by using fluent codeCustomizing the action invokerRegistering the custom invokerEnabling dynamic loading via a filter providerAction result typesBuilt-in action result typesReturning a custom status codeReturning JavaScript codeReturning JavaScript Object Notation dataReturning primitive typesCustom result typesReturning JSONP StringsReturning syndication feedDealing with binary contentReturning PDF filesSummary
9. Testing and testability in ASP.NET MVC
Testability and designDfTThe attribute of controlThe attribute of visibilityThe attribute of simplicityLoosen up your designInterface-based programmingRelativity of software testabilityTestability and couplingTestability and object orientationThe basics of unit testingWorking with a test harnessChoosing a test environmentTest fixturesArrange, act, assertData-driven testsAspects of testingVery limited scopeTesting in isolationFakes and mocksNumber of assertions per testTesting inner membersCode coverageTesting your ASP.NET MVC codeWhich part of your code should you test?How do I find relevant code to test?The domain layerThe orchestration layerThe data access layerUnit testing ASP.NET MVC codeTesting whether the returned view is correctTesting localizationTesting redirectionsTesting routesDealing with dependenciesAbout mock and fake objectsTesting code that performs data accessMocking the HTTP contextMocking the HttpContext objectMocking the Request objectMocking the Response objectMocking the Session objectMocking the Cache objectSummary
10. An executive guide to Web API
The whys and wherefores of Web APIThe need for a unified HTTP APIBeyond WCFWhat Web API means for client applicationsWhat Web API means for ASP.NET Web Forms applicationsMVC controllers vs. Web APIThe Controller class does it allFeeling the differenceBuilding RESTful applicationsPutting Web API to workDesigning a RESTful interfaceDefining the resource typeThe ApiController ClassRouting to action methodsDealing with multiple matchesActive naming conventionsExpected method behaviorSemantic of POST methodsSemantic of PUT methodsSemantic of DELETE methodsSemantic of other methodsUsing the Web APIInvoking Web API from JavaScriptInvoking from server-side codeMaking the call asynchronousDesigning an RPC-oriented InterfaceCRUD-over-HTTP is just one optionAction attributesCustom routesAttribute routingTurning on attribute routingSecurity considerationsThe host takes care of securityUsing Basic authenticationUsing access tokensUsing OAuthUsing cross-origin resource sharingNegotiating the response formatThe ASP.NET MVC approachUnderstanding the requested formatEnforcing data and format separationHow content negotiation works in Web APIInvolved HTTP headersChanging default formattersDefining formatters for specific typesSummary
III. Mobile clients
11. Effective JavaScript
Revisiting the JavaScript languageLanguage basicsThe type systemNull vs. undefinedLocal and global variablesVariables and hoistingObjectsFunctionsObject-orientation in JavaScriptMaking objects look like classesUsing closuresUsing prototypesPlain custom objects vs. a hierarchy of classesjQuery’s executive summaryDOM queries and wrapped setsThe root objectRunning a queryEnumerating the content of a wrapped setSelectorsBasic selectorsCompound selectorsPredefined filtersFilter vs. findChaining operations on a wrapped setEventsBinding and unbindingLive event bindingPage and DOM readinessAspects of JavaScript programmingUnobtrusive codeStyle the view by using codePragmatic rules of unobtrusive JavaScriptReusable packages and dependenciesThe Namespace patternThe Module patternScript and resource loadingThe download is always synchronousScripts at the bottomDealing with static filesUsing spritesBundling and minificationBundling related resourcesBundling script filesAdding minificationSummary
12. Making websites mobile-friendly
Technologies for enabling mobile on sitesHTML5 for the busy developerSemantic markupWhat’s different in HTML5?A native collapsible elementNew input typesThe <datalist> elementLocal storageAudio and videoRWDFeature detectionCSS media queriesCSS media queries in actionFluid layoutWhen RWD meets mobilejQuery Mobile’s executive summaryThemes and stylesData-* attributesPages in jQMHeader and footerLists, lists, and listsFluid layoutCollapsible panelsTwitter Bootstrap at a glanceSetting up BootstrapThe grid systemNavigation barsEmbellishing the UI with icons and imagesDrop-down menusButton groupsAdding mobile capabilities to an existing siteRouting users to the correct siteThe routing algorithmImplementing the routing algorithmTracking the chosen routeTweaking the configuration filesFrom mobile to devicesSummary
13. Building sites for multiple devices
Understanding display modes in ASP.NET MVCSeparated mobile and desktop viewsBuilt-in support for mobile viewsDefault configuration for mobile viewsRules for selecting the display modeNaming a display modeThe matching ruleAdding custom display modesListing current display modesGoing beyond the default configurationDefining custom display modesIntroducing the WURFL databaseStructure of the repositoryThe overall XML schemaGroups of capabilitiesWURFL patch filesEssential WURFL capabilitiesIdentifying the current deviceServing browser-specific contentUsing WURFL with ASP.NET MVC display modesConfiguring the WURFL frameworkInstalling the NuGet packageReferencing the device databaseInitializing the WURFL runtimeDetecting device capabilitiesProcessing the HTTP requestVirtual capabilitiesAccuracy vs. performanceUsing WURFL-based display modesSelecting display modesDefining matching rulesA multidevice site in actionThe WURFL cloud APISetting up the APICloud API vs. on-premises APIWhy you should consider server-side solutionsSummary
A. About the author
Index
About the Author
Copyright

Content preview from Programming Microsoft ASP.NET MVC

Chapter 7. Design considerations for ASP.NET MVC controllers

Part of the inhumanity of the computer is that, once it is competently programmed and working smoothly, it is completely honest.
—Isaac Asimov

The controller is the central element of any operation you perform in ASP.NET MVC. The controller is responsible for getting posted data, executing the related action, and then preparing and requesting the view. More often than not, these apparently simple steps generate a lot of code. Worse yet, similar code ends up being used in similar methods, and similar helper classes sprout up from nowhere.

ASP.NET MVC comes with the promise that it makes it easier for you to write cleaner and more testable code. For sure, ASP.NET MVC is based on some infrastructure ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9780735681095Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Programming Microsoft ASP.NET MVC

by Dino Esposito

Chapter 7. Design considerations for ASP.NET MVC controllers

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.