Logo

Maarten Balliauw {blog}

ASP.NET, ASP.NET MVC, Windows Azure, PHP, ...

About the author

Maarten Balliauw is currently employed as .NET Technical Consultant at RealDolmen. His interests are mainly web applications developed in ASP.NET (C#) or PHP and the Windows Azure cloud platform.
More about me More about me
Send mail E-mail me


ASP.NET MVC Quickly Subscribe to my RSS feed Follow me on Twitter! View Maarten Balliauw's profile on LinkedIn
View Maarten Balliauw's MVP profile

Search

Latest Twitter

    Follow me on Twitter...

    Archive

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

    © Copyright Maarten Balliauw 2012


    MSDN Chopsticks on ASP.NET MVC (screencasts)

    A while ago, KatrienDG asked me to do some screencasts on the ASP.NET MVC framework for the MSDN Chopsticks page. I've been working on 2 screencasts: an introductory talk to the ASP.NET MVC framework and a Test Driven Development story. Feel free to leave some comments!

    kick it on DotNetKicks.com

    Introduction to ASP.NET's MVC framework

    Abstract: "The ASP.NET MVC framework is a new approach to web development, based on the model-view-controller design pattern. Microsoft built this framework on top of ASP.NET to allow this alternative to work with existing features like membership caching, user controls... In this video, Maarten shows you some basics on the ASP.NET MVC framework like creating a new controller action and a view."

    Test Driven Development with the ASP.NET MVC framework

    Abstract: "This video explains you how to develop ASP.NET MVC web applications using 2 different approaches: regular development and test-driven development."

    Example code: MvcTodoList.zip (503.21 kb)


    Categories: ASP.NET | C# | General | MVC | Screencasts | Testing

    Comments (1) -

    Dragan Panjkov Bosnia and Herzegovina |

    Thursday, August 07, 2008 10:07 AM

    Dragan Panjkov

    I have one opinion regarding passing strongly typed view data. I think it is not necessary to create wrapper class around employee object when passing t to the view. you might simply pass employee class to the view.
    however, in your approach, you have one advantage that is your wrapper class could contain more objects of different types and pass them to the view, instead of only passing one type of object, for exampe, in method body

    Employee emp = new Employeee { Name = "Name", Email = "eml@eml.com"};
    return View(emp);

    and view could be strongly typed
    ... ViewPage<Employee> {
    }
    in my example, i can pass only employee to View, and not other objects.

    in summary, excellent screencasts. I like ViewData wrapper classes approach you use Smile

    Pingbacks and trackbacks (1)+

    Comments are closed