MasterClass: The Future of ASP.NET Development
Devised in the late 1990s at a time in which many companies, in a variety of industry sectors, were rapidly discovering the new media called the Internet. For companies the Internet represented a real breakthrough making it possible things that were impractical or impossible before. In this context, ASP.NET was the right technology at the right time.
ASP.NET was originally designed to fit as closely as possible to the average developer - a former C/C++/Java developer or an early adopter of HTML willing to do fancier things that JavaScript could just not support. In the middle, there was the VB developer, used to RAD programming and slowly absorbing the very basic concepts of object-oriented programming. ASP.NET Web Forms was designed for these developers. And it worked great for several years.
The advent of AJAX revolutionized the perception of a Web application and sparked off a paradigm shift - a long process that we probably went through for no more than 70% of its natural length.
Web Forms is really close to its architectural dead end. If you lead a team of developers, and if your business is based on ASP.NET and Web applications, you should seriously consider alternatives such as ASP.NET MVC.
This seminar provides an architectural overview of the ASP.NET runtime environment shedding some light on features (and design choices) we just passively endured in the past years. As we recognize possible leaks in the today's architecture of ASP.NET we find that some of them are fixed and ready to use in a new framework - ASP.NET MVC. This leads to the dilemma "Web Forms vs. MVC" but it's not exactly a matter of preference. Or, put another way, it could still be a matter of preference but only after you've seen it from a number of angles and perspectives.
ASP.NET was originally designed to fit as closely as possible to the average developer - a former C/C++/Java developer or an early adopter of HTML willing to do fancier things that JavaScript could just not support. In the middle, there was the VB developer, used to RAD programming and slowly absorbing the very basic concepts of object-oriented programming. ASP.NET Web Forms was designed for these developers. And it worked great for several years.
The advent of AJAX revolutionized the perception of a Web application and sparked off a paradigm shift - a long process that we probably went through for no more than 70% of its natural length.
Web Forms is really close to its architectural dead end. If you lead a team of developers, and if your business is based on ASP.NET and Web applications, you should seriously consider alternatives such as ASP.NET MVC.
This seminar provides an architectural overview of the ASP.NET runtime environment shedding some light on features (and design choices) we just passively endured in the past years. As we recognize possible leaks in the today's architecture of ASP.NET we find that some of them are fixed and ready to use in a new framework - ASP.NET MVC. This leads to the dilemma "Web Forms vs. MVC" but it's not exactly a matter of preference. Or, put another way, it could still be a matter of preference but only after you've seen it from a number of angles and perspectives.
Taastrup
23. og 24. november 2010
2 dage
09:00 - 16:30
Nr.: 87066 A
DKK 10.750,- ekskl. moms
Deltagerprofil
Indhold
Dino Esposito
The seminar is aimed at architects and technical managers who are, or might be soon, in the position of making a choice between classic ASP.NET and ASP.NET MVC. What is a free choice today may become an asset or a criticality in the near future. A deep understanding of the architecture and framework capabilities, instead, will put you on the safe side allowing for a thoughtful decision.
Indhold
The seminar is articulated in six sessions spread over two days. The first day provides an architectural review of the ASP.NET internals. Each framework is dissected to let the good and bad emerge clearly. Next, common business scenarios are examined to help understanding where and why classic ASP.NET or ASP.NET MVC may be preferable. The second day offers a programming overview of ASP.NET MVC to showcase its new programming model, extensibility features, and functional capabilities.
From Page Controllers to Controllers.
The best-selling point of ASP.NET is that it discloses the world of Web programming to many developers with limited or no skills at all in HTML and JavaScript. At the same time, ASP.NET can be easily approached by Web people with limited skills in programming languages. The magical compromise is based on the Page Controller pattern - sort of black-box machinery that is optimized to accept the description of a page and produce it. A lot of abstraction is employed to close the machine and make it work. Just the abstraction that sometimes we want to get rid of today...
The best-selling point of ASP.NET is that it discloses the world of Web programming to many developers with limited or no skills at all in HTML and JavaScript. At the same time, ASP.NET can be easily approached by Web people with limited skills in programming languages. The magical compromise is based on the Page Controller pattern - sort of black-box machinery that is optimized to accept the description of a page and produce it. A lot of abstraction is employed to close the machine and make it work. Just the abstraction that sometimes we want to get rid of today...
Exploring Business Scenarios for ASP.NET MVC.
Learning ASP.NET MVC has a cost. Who's supposed to pay for that? Your customer? Your company? You yourself? How would you justify to a project manager the extra training costs for just using ASP.NET MVC? You can try, but the natural objection is: OK, but where's my return? Can't we take this project home by simply using Web Forms that we already know through and through? Maybe; or maybe not..
Learning ASP.NET MVC has a cost. Who's supposed to pay for that? Your customer? Your company? You yourself? How would you justify to a project manager the extra training costs for just using ASP.NET MVC? You can try, but the natural objection is: OK, but where's my return? Can't we take this project home by simply using Web Forms that we already know through and through? Maybe; or maybe not..
Rich Web, Still Web.
AJAX revolutionized the Web and moved companies and software vendors towards new frameworks and a new component model. Today the world seems standardizing on jQuery to add client-side features on top of server-side built views. In alternative, there's Silverlight for those scenarios where you either need to provide a really rich experience or a desktop-like experience to your users. AJAX, however, is the missing link and the litmus test of the completion of the Web revolution it started. We need a Web where we get AJAX capabilities out of the box. Will rich Internet applications come with HTML 5? Who knows..
AJAX revolutionized the Web and moved companies and software vendors towards new frameworks and a new component model. Today the world seems standardizing on jQuery to add client-side features on top of server-side built views. In alternative, there's Silverlight for those scenarios where you either need to provide a really rich experience or a desktop-like experience to your users. AJAX, however, is the missing link and the litmus test of the completion of the Web revolution it started. We need a Web where we get AJAX capabilities out of the box. Will rich Internet applications come with HTML 5? Who knows..
ASP.NET MVC at a Glance.
This session offers a journey in the lifecycle of an ASP.NET MVC request touching on some aspects of the ASP.NET MVC framework such as routing, URL design, controllers, model binding, views, and view engines. Layers of a ASP.NET MVC Application. In ASP.NET MVC the core of the system is the controller component. The controller, however, is still part of the presentation layer and needs be designed with a clear goal - the coordinator stereotype. In other words, the controller must be the dispatcher of requestrelated work to external layers (or services) and the assembler of view-related data. Sounds like not a big deal? Well, the evil is in the details..
This session offers a journey in the lifecycle of an ASP.NET MVC request touching on some aspects of the ASP.NET MVC framework such as routing, URL design, controllers, model binding, views, and view engines. Layers of a ASP.NET MVC Application. In ASP.NET MVC the core of the system is the controller component. The controller, however, is still part of the presentation layer and needs be designed with a clear goal - the coordinator stereotype. In other words, the controller must be the dispatcher of requestrelated work to external layers (or services) and the assembler of view-related data. Sounds like not a big deal? Well, the evil is in the details..
Patterns of ASP.NET MVC Development.
To complete the ASP.NET MVC overview, this session is aimed at showing ASP.NET MVC in action in a number of common situations including data entry, validation, data navigation, access to ASP.NET intrinsic, security.
To complete the ASP.NET MVC overview, this session is aimed at showing ASP.NET MVC in action in a number of common situations including data entry, validation, data navigation, access to ASP.NET intrinsic, security.
Dino Esposito
An architect and trainer at IDesign (http://www.idesign.net), Dino Esposito is one of the world's authorities on Web technology and software design and architecture. Over years, Dino developed hands-on experience and skills in architecting and building distributed systems for banking and insurance companies and, in general, in industry contexts where the demand for security, optimization, performance, scalability, interoperability is dramatically high.
Dino is also a prolific author. Every month, at least five different magazines and Web sites throughout the world publish Dino's articles covering topics ranging from Web development to AJAX architectures and from data access to Silverlight and design patterns. Dino published an array of books, most of which are considered state-of-the-art in their respective areas. His recent books are "Microsoft .NET: Architecting Applications for the Enterprise", "Architecting Web Applications with ASP.NET AJAX" and the evergreen "Programming ASP.NET 3.5-Core Reference". All books are from Microsoft Press. Other books are coming out in 2009 to cover the new version of the .NET Framework.
Dino speaks regularly at industry conferences all over the world, including Microsoft TechED, DevConnections, and premiere European events such as DevWeek and BASTA!.
For yderligere information kontakt
Produktansvarlig, Mette Hougaard Holm
Email: mette.holm@teknologisk.dk
Produktansvarlig, Mette Hougaard Holm
Email: mette.holm@teknologisk.dk
Godkendt: 3. august 2010
