Learning MVC for the Web Forms Developer (Adam Tuliper)

Date
7-8 Apr 2011 (Add to calendar) GMT
Venue
University of Connecticut , One University Place, US
Cost
Free

The biggest problem for developers moving to MVC is not being able to use a lot of the Web Forms knowledge we’ve already spent so much time learning. This presentation will take the developer from something they already know – ASP.NET Web Forms – and move them into MVC utilizing the knowledge they already have for Web Forms. We will review a complete ASP.NET Web Forms application where we do common tasks, and then see how to do the equivalent type of task in MVC. Procedures such as Data Binding, Error Handling, URL routing, AJAX, and more will be covered. No MVC talk would be complete without discussing how to unit test our MVC code as well. This discussion will also cover common controls (grids, etc) available to the developer and how client libraries used to enhance our MVC applications. Adam Tuliper has been developing software for over 15 years. He started his work in security and reverse engineering (x86 based – pre .NET) with the direction of going into the software protection and anti-piracy field. This gave him a foundation for learning the internals of other technologies from Win32 systems to CLR systems. Besides development, he has performed security audits and penetration testing for large and small companies alike. Adam currently works as a Software Architect for Cegedim. He has been deeply involved in .NET internals since early beta and currently works extensively with WCF, ASP.NET, SQL Server, MVC, C#, jQuery, and Silverlight.

You might also like...

Comments

Other nearby events

Map

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“The trouble with programmers is that you can never tell what a programmer is doing until it's too late.” - Seymour Cray