Designing and Implementing Controls (13 percent) Choose appropriate controls based on business requirements.
May include but is not limited to: user controls, server controls, built-in controls, custom controls, third-party controls, Web parts Design controls for reusability.
May include but is not limited to: user controls, server controls, inheritance for changing behavior Manage states for controls.
May include but is not limited to: control state, view state, accessing form elements Leverage data-bound controls.
May include but is not limited to: use gridviews, use sorting and paging callbacks when available, when to use custom sorting and paging, server-side pagination Choose appropriate validation controls based on business requirements.
May include but is not limited to: server-side page validation (Page.IsValid), custom validator, validation groups, validation summary Identify the appropriate usage of ASP.NET AJAX.
May include but is not limited to: implementing partial page updates with update panel, using ASP.NET AJAX controls, script services Manage JavaScript dependencies with server controls.
Designing the Presentation and Layout of an Application (16 percent) Design complex layout with Master Pages.
May include but is not limited to: strongly typed master pages, nested master pages Plan for various user agents.
May include but is not limited to: markups for different browsers for mobile devices, screen readers, accessibility Design a brandable user interface by using themes.
May include but is not limited to: shared themes across multiple applications, run time master page selection Design site navigation.
May include but is not limited to: when to extend site map provider, treeview menu vs. site map path, programmatically manipulating site map nodes, overriding menu rendering by using control adapters, filtering site map nodes based on user roles Plan Web sites to support globalization.
May include but is not limited to: custom resource provider vs. resource files, localize applications
Accessing Data and Services (18 percent) Plan vendor-independent database interactions.
May include but is not limited to: IDBconnection, IDBcommand, IDBadapter, IdataReader, Datareader vs. dataset Identify the appropriate usage of data source controls.
May include but is not limited to: SQLDataSource, ObjectDataSource, XMLDataSource Leverage LINQ in data access design.
May include but is not limited to: LINQtoSQL, lambda expressions, LINQtoObjects, LINQtoXML Identify opportunities to access and expose Web services.
May include but is not limited to: WCF, ASMX, REST
Establishing ASP.NET Solution Structure (13 percent)Determine when to use the Web Site model vs. a Web Application Project.
May include but is not limited to: project file, references, namespace, user profile object, precompilation Establish an error-handling strategy.
May include but is not limited to: Global.asax events, Web.config elements, TRY/CATCH blocks, error logging Manipulate configuration files to change ASP.NET behavior.
May include but is not limited to: machine key, tracing, encrypting Web configuration data, custom configuration sections Identify a deployment strategy.
May include but is not limited to: mangement application pools, Web deployment projects, pre-compilation, custom action classes
Leveraging and Extending ASP.NET Architecture (17 percent) Design a state management strategy.
May include but is not limited to: Cache, ViewState, Application object, Session object, cookies, cookieless session Identify the events of the page life cycle.
May include but is not limited to: appending controls, PostBack model, accessing state, data binding Write HttpModules and HttpHandlers.
May include but is not limited to: URL rewriting, SSO application, dynamically retrieve data Debug ASP.NET Web applications.
May include but is not limited to: debug JavaScript, tracing, debug tools in IDE, examining HTTP headers Plan for long-running processes by using asynchronous pages.
May include but is not limited to: AddonPreRenderCompleteAsync, RegisterAsyncTask
Applying security principles (23 percent) Identify appropriate security providers.
May include but is not limited to: membership, role, profile, extending custom providers Decide which user-related information to store in a profile.
May include but is not limited to: create user profile properties, extend membership objects, custom types Establish security settings in Web.config.
May include but is not limited to: identity/impersonation, authentication, authorization (location nodes in Web.config) Identify vulnerable elements in applications.
May include but is not limited to: SQL injection, cross-site scripting, protecting against bots Ensure that sensitive information in applications is protected.
May include but is not limited to: hash and salt passwords, encrypting information
|
