hishamco/webforms

ASP.NET Core Web Forms is MVC alternative that use event-driven programming model for building dynamic web application

WebForms

AppVeyor:

Travis:

ASP.NET Core Web Forms is MVC alternative that use event-driven programming model for building dynamic web application

What is this?

This is just a prototype for building a new programming model for ASP.NET Core (alternative for MVC), that use event-driven programming. It's simillar to previous ASP.NET Web Forms that we know and love, with new flavour

What are the plans for this project?

The project is still in the early stages, but I have some points in my mind to share:

• Building a basic infrastructure for Web Forms on top new Http pipline using Middleware
• Page Lifecycle is not like the previous ASP.NET WebForms
• Provide a set of rich server controls that render a clean HTML markup, without wired IDs
• No ViewState anymore
• No Page Directives
• No View Engine yet!! it's a pure HTML page with rich server controls, perhaps we can use Razor or any other view engine later on, but I'm thinking to use sort of client-side template language like Mustache

Why are Web Forms using .htm, .htm.cs instead of .aspx, .aspx.cs?

There's no primary reason for that, but I want to take the advantages for VS intellisense while I'm using HTML views for now. For the release may I use the .aspx or .aspc while we're using ASP.NET Core.

Can I use it in Production?

Short answer is Not Yet, because the project is still a prototype, and it's under development. All of you 're welcome to contribute to the source code, to bring ASP.NET WebForms back.

webforms's Issues

Add Templating Syntax

Thinking about a simple, clean & compact templating syntax

Generate .designer files

Make pages location folder configurable

It would be nice to change the pages location as the following:

services.AddWebForms(options => options.PagesLocation = "WebForms");

PRG Pattern

It would be nice if we prevents some duplicate form submissions using Post/Redirect/Get Pattern

Control Rendering issue

The control parser should be improved, if you look to this:

<span class="label label-info">
    <asp:Literal Name="litPostBack" Text="IsPostBack: False"></asp:Literal>
</span>

it will work fine, but if we change it to:

<span class="label label-info"><asp:Literal Name="litPostBack" Text="IsPostBack: False"></asp:Literal>
</span>

it will not work 😞

Seems we figure out the beginning of the tag controls where ever is it

Add Postback property to the Page

Allow Pages to be rooted by default

Use Logging APIs

We should use Logging APIs whenever it is possible

Inject ILogger to Page

Add Logger property to the Page by injecting ILogger<PageClass>

Add designer file for the pages

Prettify the page by moving the controls setup code into a .designer.cs file. This should created by the IDE and it's responsible for sync it with the view. While there's no IDE surface for drag and drop we should do it ourselves

Add IsPostBack into PageLoadEventArgs

While the intend of IsPostBack is to check the Request.Method if it's POST or not, and this is common happen in PageLoad event. It would be nice if we add this property into PageLoadEventArgs