Project Description
The purpose of this project is to try and strip back a lot of the "bloat" in asp.net, use jquery and to build effective MVC in to WebForms

The purpose of this project is to try and strip back a lot of the "bloat" in asp.net, creating a fast and efficient set of pages, whilst maintaining the same development style.

ASP.Net MVC striped everything back, but also took with it a large chunk of the convenience - I am trying to find a middle ground.

gaiaware.net attempted to make nice ajax calls in asp.net, but has become quite bloaty, and still suffers from performance when it comes to the page lifecycle. It also is heavily reliant on prototype, in a world where jQuery rules...

The Initial Idea (although where this goes is anyones guess)

Currently - to utilise PageMethods to create a clean, and quick server side method, but without having to write any page specific jquery to present the result...

So far - the markup looks like this:

<p><IP:Label runat="server" ID="MyLabel" Text="label text" /></p>
<p><IP:TextBox runat="server" ID="MyTextBox" Text="First text" /></p>

<p><IP:LinkButton runat="server" ID="Link" Text="Go!" Callback="MyMethod" /></p>

while the code behind looks like this:

public partial class Default : MvcController
{
protected override void MvcPage_Load(object sender, EventArgs e)
{

}

WebMethod
public static ReturnView MyMethod(View postData)
{
postData.MyTextBox = "textbox updated";
postData.MyLabel = "label updated";

return postData.Updated;
}

public class View : MvcView
{
public string MyTextBox { get { return Get<string>("MyTextBox"); } set { Set<string>("MyTextBox", value); } }
public string MyLabel { get { return Get<string>("MyLabel"); } set { Set<string>("MyLabel", value); } }
}
}

ReturnView is automatically re-applied back to the aspx page.
ONLY the changed fields on the View are returned back to the client.


Additional information on starting a new project is available here: Project Startup Guide.

Last edited Nov 4, 2012 at 1:01 AM by paulallington, version 2