Channel 9

Mobile Model in MVP web app

Andrew Davey — Wed, 17 Oct 2007 18:33:33 GMT

This screencast continues from the work I demonstrated in a previous screencast: http://channel9.msdn.com/Showpost.aspx?postid=344711

When implemented a Model-View-Presenter pattern client-side in JavaScript there is a need to get data from the server. Rather than make this divide explicit with HTTP request, etc, I have used the idea of a model object that moves between the client and server.
So the programmer simply writes the client and server pieces of functionality and lets my framework do the plumbing.

I use code generation and Script# to make writing a client-side web app much more seemless than the usual javascript/XML/JSON/web service madness.

I'm developing the ideas shown here in a project at the moment. If there is sufficient interest I may extract a framework to give to the community.

How do people feel about this approach to web development? What kinds of additions/modifications should be made?

p.s. I have a bit of a cold at the moment, so sorry for the croaky voice in the recording!

Client-side Model-View-Presenter

Andrew Davey — Fri, 28 Sep 2007 16:14:39 GMT

The model-view-presenter pattern is a very powerful way to manage user interaction. It seems popular to use it on the server-side when creating HTML, but why not use it client-side instead?
Our computers are powerful enough to run fairly complex JavaScript. Why burden the server with having to render the page contents?

In this screencast I use Script# to compile a C# project into JavaScript. This project contains the Model, View and Presenter logic.
The HTML page then uses the generated JavaScript.

There is a simple REST service on the server that returns data which is called by the Model. No HTML generation occurs on the server.

Download the source code. You must have Script# installed as well.

Functional ADO.NET

Andrew Davey — Sun, 02 Sep 2007 16:41:14 GMT

Whilst LINQ is almost here, there is still a place in the world for plain old ADO.NET programming. However, procedural ADO.NET code can often be cumbersome to write. Executing some SQL for a data reader can involve three nested layers of C# using statements.
In this screencast, I present a functional approach to using ADO.NET that wraps most of the boiler-plate code into a Database class.
It makes use of anonymous methods to allow the developer to provide the required code at different points in the ADO.NET code.
The result is a syntactically lightweight way to interact with a database.

The code used in the project can be downloaded here:
C# 3.0 http://www.aboutcode.net/screencasts/functional-ado.3.zip
C# 2.0 http://www.aboutcode.net/screencasts/functional-ado.2.zip (same as 3.0 but with non-inferred anonymous methods).