[Code Camp 2009] ASP.NET MVC a full (Matías Juan Rubí + Jonathan Solarz)
•Descargar como PPTX, PDF•
0 recomendaciones•720 vistas
![Microsoft Argentina y Uruguay [Official Space]](https://cdn.slidesharecdn.com/profile-photo-comunidadesms-48x48.jpg?cb=1522877393)
Este documento presenta ASP.NET MVC, un framework que separa las responsabilidades de una aplicación web en modelos, vistas y controladores. Explica los componentes principales de MVC como routing, controladores, vistas y modelos, y cómo funciona el framework. También cubre temas como unit testing, model binders, action filters y cómo extender el framework con contribuciones de terceros.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a [Code Camp 2009] ASP.NET MVC a full (Matías Juan Rubí + Jonathan Solarz)
Similar a [Code Camp 2009] ASP.NET MVC a full (Matías Juan Rubí + Jonathan Solarz) (20)
Más de Microsoft Argentina y Uruguay [Official Space]
Más de Microsoft Argentina y Uruguay [Official Space] (20)
[Code Camp 2009] ASP.NET MVC a full (Matías Juan Rubí + Jonathan Solarz)
- 1. ASP.NET MVC A FULL Matias Juan / mjuan@tecnosoftware.com.ar Jonathan Solarz / jsolarz@tecnosoftware.com.ar Tecnosoftware S.A.
- 2. Objetivos Que es ASP.NET MVC Unit Testing con ASP.NET MVC Extendiendo ASP.NET MVC
- 3. ASPNET MVC Foco en separación de responsabilidades (MVC) REST (en contraste a Postback) Extensibilidad Mejor soporte para TDD
- 4. Componentes principales en MVC Routing, Routetables Model, BussinessLogic & DomainEntities Controllers, PresentationLogic Views, PresentationModel, Modelstate
- 5. El framework en funcionamiento Browser MvcHandler Controller Model View Post New InvokeAction InvokeMethod Lookup View Render (ViewData) HTML
- 6. Demo Ejemplo simple de que hace el ASPNET MVC
- 7. Unit testing Probar partes del sistema de manera individual asegurando que funcionan correctamente Provee un contrato escrito y estricto que una porcion de código debe cumplir Como resultado podemos encontrar problemas de manera temprana y de manera instantánea
- 8. Probando la lógica de presentación Aseguremos que todo lo que llega a la vista esta testeado Probamos lógica de navegación Probamos las validaciones La vista la podemos probar navegando el sitio manualmente o con alguna herramienta automatizada
- 9. Demo Agregamos algo de unit testing
- 10. ModelBinders Extensión del framework que permite crear instancias de clases en base a valores enviados por request. Al action llega el objeto instanciado y no los valores del request Nos permite participar del ciclo de vida de creación de la instancia permitiéndonos por ejemplo validar los atributos y agregar mensajes de error invalidando el modelo
- 11. Demo Vemos como simplificamos la responsabilidad del controller agregando el uso de binders
- 12. ActionFiltrers Nos permiten interceptar distintos puntos de la ejecución de un action Se decoran controllers y/o actions Reutilizamos lógica de presentación Ejemplos Validaciones Carga de datos en el viewData Caché
- 13. Demo Aplicamos lógica de presentación en distintos puntos de la aplicación. La responsabilidad la tiene el filtro
- 14. ControllerFactory Necesitamos cambiar la manera de instanciar controllers Por ejemplo: Para integrar la solución con un IoCcontainer y poder inyectar dependencias Request MvcHandler IController MvcRouteHandler IControllerFactory
- 15. Demo Integramos la solución con un IoCcontanier y todo es automágicamente inyectado
- 16. Contribuciones MvcContrib ViewDataExtensions : nospermitetipar el viewDataparavariosobjetos Factories de controllers para containers IoC: StructureMap, Windsor, Spring.Net, etc UI Helpers ActionResults Filters View Engines Controllers Binders
- 17. Referencias ASPNET MVC Referencia: http://www.asp.net/learn/mvc/ Books: http://www.asp.net/community/books/ Unit Testing y Mocking Nunit: http://www.nunit.org/ NMOCK: http://www.nmock.org/index.html RHINO MOCK: http://ayende.com/projects/rhino-mocks.aspx Extras MvcContrib: http://www.codeplex.com/MVCContrib ValidatorToolkit: http://mvcvalidatortoolkit.codeplex.com/
- 18. ¿Preguntas?
Notas del editor
- Acaseteamos las expectativas de la presentación. Explicamos que veremos los temas mas interesantes del framework viendo código, por lo que los ejemplos muestran esto.Extendiendo:Unit Testing:Este es creo el punto más interesante así que mostramos distintas estrategias para sacarle jugo al unit testing usando algunos frameworks como mockups, inversión de control einyección de dependencias, etc.
- The ASP.NET MVC framework provides the following features:Separation of application tasks (input logic, business logic, and UI logic), testability, and test-driven development (TDD) by default. All core contracts in the MVC framework are interface-based and can be tested by using mock objects, which are simulated objects that imitate the behavior of actual objects in the application. You can unit-test the application without having to run the controllers in an ASP.NET process, which makes unit testing fast and flexible. You can use any unit-testing framework that is compatible with the .NET Framework.An extensible and pluggable framework. The components of the ASP.NET MVC framework are designed so that they can be easily replaced or customized. You can plug in your own view engine, URL routing policy, action-method parameter serialization, and other components. The ASP.NET MVC framework also supports the use of Dependency Injection (DI) and Inversion of Control (IOC) container models. DI allows you to inject objects into a class, instead of relying on the class to create the object itself. IOC specifies that if an object requires another object, the first objects should get the second object from an outside source such as a configuration file. This makes testing easier.A powerful URL-mapping component that lets you build applications that have comprehensible and searchable URLs. URLs do not have to include file-name extensions, and are designed to support URL naming patterns that work well for search engine optimization (SEO) and representational state transfer (REST) addressing.Support for using the markup in existing ASP.NET page (.aspx files), user control (.ascx files), and master page (.master files) markup files as view templates. You can use existing ASP.NET features with the ASP.NET MVC framework, such as nested master pages, in-line expressions (<%= %>), declarative server controls, templates, data-binding, localization, and so on.Support for existing ASP.NET features. ASP.NET MVC lets you use features such as forms authentication and Windows authentication, URL authorization, membership and roles, output and data caching, session and profile state management, health monitoring, the configuration system, and the provider architecture.
- Componentes significativos del frameworkControllers:The focus of the Model-View-Controller pattern is the controller. With this pattern, every request is handled by a controller and rendered by a view. Without the controller, presentation and business logic would move to the view, as we have seen with Web Forms. With the ASP.NET MVC Framework, every request routes to a controller, which is simply a class that implements the IController interface. Microsoft provides the base class System.Web.Mvc.Controller to make creating a controller easy. The controller base class you choose is not crucial because most request processing goes into executing the ActionResult, which is the type that each action returns.ControllerAction:An action is a method that handles a particular request. This method can take no parameters or many, but by the time the action method finishes executing, there ought to be one or many objects ready to be sent to the view, and the name of the view should be selected if the view does not follow the convention of having the same name as the action.PresentationModel:The presentation model is responsible for transforming the domain model into a representation that is useful for the presentation layer, namely, the controller and view. Whereas the domain model is an ndimensionobject graph that accurately represents the real world, the presentation model takes these objects and projects them into a flatter model that can easily be represented on a graphical screen.NOTE The presentation model can be many things. Ultimately, it is an object model that serves a particular screen, not the entire domain. This object model can be populated in isolation, or it can take responsibility to populate itself when a domain object is passed into the constructor. The presentation model goes in the /Models folder in an ASP.NET MVC Framework application. The presentation model is part of the presentation layer and should not be referenced by the rest of the application. Typically a complex screen will require a presentation model object graph.