[CLPE] Novidades do Asp.net mvc 2
•Download as PPTX, PDF•
1 like•466 views
O documento apresenta o framework ASP.NET MVC 2.0, discutindo suas principais funcionalidades como áreas, helpers HTML, templates, validação com DataAnnotations, atributos como HttpPost e RequireHttps e provedores extensíveis. O ASP.NET MVC é uma opção para desenvolvimento web que separa apresentação, lógica e dados de forma mais clara comparado aos WebForms.
![Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (17)
Similar to [CLPE] Novidades do Asp.net mvc 2
Similar to [CLPE] Novidades do Asp.net mvc 2 (20)
More from Felipe Pimentel
More from Felipe Pimentel (16)
[CLPE] Novidades do Asp.net mvc 2
- 1. Conheça oASP.NET MVC 2 Daniel Ferreira MSP | MCP | MCTS | MCPD C.E.S.A.R @dfsdaniel
- 4. O ASP.NET Hoje! ASP.NET Dynamic Data Presentation ASP.NET WebForms ASP.NET MVC ASP.NET Core Runtime
- 5. WebFormsis great, but options are good…
- 6. Master Page Control Control UI Presentation Logic Business Logic Data Access Control Control Page Control Control Control Control Quemfaz o que? Como e quando? Semdivisão de responsabilidades
- 7. Abstração de controlespodenãoseruma boa idéia…
- 8. Controller (Input) Model (Logic) View (Presentation) Separação de interesses! O Padrão MVC
- 9. Controller Controller Handles input (HTTP requests) Request View View Visually represents the model Response Por outro ângulo…
- 10. O ASP.NET MVC Framework Namespace: System.Web.Mvc Um novo template de projeto no Visual Studio Uma nova maneira de desenvolver com ASP.NET Não é uma nova versão dos webforms Foco na arquitetura do projeto
- 11. O ASP.NET MVC Framework Roadmap: Prédaversão 1 VS 2008 (dez/07 a mar/09) Versão 1.0 VS 2008 (mar/09) Versão 1.1 VS 2010 beta 1 (jun/09) Prédaversão 2 VS 2008 e VS 2010 (jul/09) Versão 2 VS 2008 e VS 2010 (primeirotrimestre de 2010)
- 12. ASP.NET MVC 2.0
- 13. Novidadesda versão 2.0 Agrupamentoporáreas in-the-box Data Annotations Validation Templates Helpers HTML HttpPostAttribute Adição do DefaultValueAttribute Client-side validation RequireHttpsAttribute Model Validation Providers Metadata Providers
- 14. Áreas – Preview 1 Partição e agrupamento de funcionalidadesporáreas; Permitemaiormodularidade e separação. Suporte nativo a URLs mais simpáticas: “/Area1/Controlador1” ou“/Area2/Controlador1” 14
- 15. Áreas – Preview 2 Suporte “in-the-box” semnecessidade de múltiplosprojetos “AddArea” Dialog Registro de rota dinamicamente (AreaRegistration.cs) 15
- 16. Áreas
- 17. HTML Helpers Uso de expressões lambda fortemente tipadas por padrão; Visualização do erro em tempo de compilação; Melhor suporte ao intellisense dentro das views. Preview 1: Html.EditorFor(), Html.LabelFor() e Html.DisplayFor() Preview 2: Html.TextBoxFor(), Html.TextAreaFor(), Html.DropDownListFor(), Html.HiddenFor(), e Html.ValidationMessageFor()
- 18. HTML Helpers ou Antes Agora
- 19. Templates Permite customizar a exibição dos itens do EditorFor() Não precisa colocar o ID Uso do atributo UIHint no objectmodel Reaproveitamento de código
- 20. Templates
- 22. Validação Suporte nativo para validação através de DataAnnotation Declaração de regras nos ObjectModels Namespace System.ComponentModel.DataAnnotations ValidationAttribute como classe base para criação de atributos de validação personalizados Suporte a outras validações como o CastleValidator, EntLibValidation, etc)
- 24. Validação com DataAnnotations public classCustomer { [Required] public stringName{get; set; } [Range(1, 120, ErrorMessage="Invalid age")] public intAge{ get; set; } [RegularExpression(@"^(([a-zA-Z0-9_]+)@([a-zA-Z0-9_]+)([a-zA-Z]{2,5}){1,25})+([;.](([a-zA-Z0-9_]+)@([a-zA-Z0-9_]+)([a-zA-Z]{2,5}){1,25})+)*$", ErrorMessage="Invalid email")] public string Email{get; set; } [UIHint("CountryDropDown")] public string Country {get; set;} [DisplayName("Is Active Customer:")] public bool IsActive{get; set; } }
- 25. Client-side validation Também é possível fazer a validação do lado do cliente de forma mais direta; Intregação do xVal + DataAnnotations + JQuery Já incluso os plugins de validação do JQuery 1.3.2
- 26. HttpPostAttribute Antes: Agora: [AcceptVerbs(HttpVerbs.Post)] publicActionResult Create(Post post) [HttpPost] publicActionResultCreate(Postpost)
- 27. DefaultValueAttribute Agora as ações podem ter valores default, o que antes só era possível com a implementação de diferentes rotas: Agora basta declarar antes do atributo routes.MapRoute( "Default", "{controller}/{action}/{id}", new { controller = "Home", action = "Index", id = "" } ); publicActionResultCreate([DefaultValueAttribute(5)] int pagina)
- 28. RequireHttpsAttribute Por padrão, as requisições são realizadas com chamadas non-SSL (HTTP) Novo atributo de classe RequireHttpsAttributeque permite direcionar as ações dos controllers para requisições HTTP seguras (SSL-Enabled – HTTPS) 28
- 29. Providers ModelMetadata e ModelMetadataProvider A classe ModelMetadataProvider é uma abstração para obter todos os metadados dentro de uma View. Além do provider padrão do MVC para extrair DataAnnotations, é possível criar seus próprios Metadataproviders.
- 30. Providers ModelValidator Providers Também é possível criar seus próprios providers de validação com mapeamentos e regras personalizadas O padrão do MVC também é usando o DataAnnotations.
- 31. Extensibilidade Action Filters Model Binders Controller Builder Controller Factory Controller Controller Action Invoker View Engine View Action Result Qualquer parte podesertrocada!
- 33. Open Source!
- 36. Nósjá o temos, se chama: laço de foreach.Conversa entre desenvolvedoresda Microsoft, segundorelatadopor Scott Hanselman, do time do MVC.
- 40. Muitoscontrolesemsuasmãos, use com moderação! Resumindo
Editor's Notes
- Estimated Time: 2 minutesFor the entire life of ASP.NET it has been seen as a single framework that included both runtime and presentational aspects. This includes core features such as roles and globalization, as well as WebForms features such as master pages and user controls.
- Estimated Time: 2 minutesWith the release of .NET Framework 3.5 SP1, ASP.NET started being seen as more modular. ASP.NET Core now represents just the runtime aspects of ASP.NET, and ASP.NET WebForms is simply a presentation option that sits on top of that runtime. With this, it becomes possible to introduce other presentation layer implementations on top of ASP.NET, such as the new ASP.NET MVC framework.While many who are beginning to investigate into ASP.NET MVC think that it is the replacement for WebForms, as you can see, it is simply another option for developing web applications using the ASP.NET runtime.
- Estimated Time: 1 minuteWebForms has been the only option on the ASP.NET stack and provides a mature product that has proven successful for lots of developers. But it does have some weaknesses.
- Estimated Time: 2 minutesThe level of abstraction that WebForms provides has a lot of benefits to it, but it doesn’t provide any framework-level guidance in terms of what should do what and when. Between your pages, master pages, user controls, server controls, and custom controls, you can end up with a mixture of HTML, data access code, and business logic.There are certainly methodologies/practices that can be employed with WebForms that can remedy that, but it becomes an implementation task of the developer, since the framework doesn’t provide any of that separation/guidance.
- Estimated Time: 2 minutesThe control abstractions that WebForms provides are very powerful in that they neatly contain all of the UI and business logic needed so you can just place them within a page and go. The adverse side of that is that it can end up hiding complexity that you’d rather have control over. A common problem is viewstate[Advance Animation]. It isn’t viewstate’s fault that things like this can happen, but it can be very easy to consume a control that could end up hurting the performance of your application.In addition, many times the markup rendered by server controls aren’t always ideal and there is little control over that without having to redo its rendering completely.
- Estimated Time: 2 minutesMVC is a design pattern that stands for Model-View-Controller. What is strives to do is separate the concerns of an application’s presentation layer by assigning specific roles to the three different components.The Controller is responsible for handling all user input. Once input has been received, the Controller will perform any operations/actions it needs to, which might include interacting with the Model.The Model represents the core concern/logic of the application. Once the Controller retrieves some model data and performs any work with the model/etc it needs to it constructs a presentation model that describes the model in terms the View can understand.The View is the visual representation of the model. It presents the model data to the actual user in a way that is meaningful. In a web application, this would typically be HTML.With these three pieces in place, your presentation layer becomes cleanly separated in such a way that each component can be developed/tested independently.