* ASP.NET

	The classes for running ASP.NET are being actively written.
	Gaurav, Leen and Patrik have been building the classes
	required to run ASP.NET web application as well as a small
	embeddable web server.

	There are a couple of components to the puzzle:

	<ul>
		* .aspx page parser (converts .aspx to C# code).
	
		* System.Web.HttpRuntime support.
	
		* Web controls (System.Web.UI.HtmlControls and
		  System.Web.UI.WebControls).
	
		* Underlying infrastructure for the controls (System.Web.UI).
	
		* HttpRuntime.ProcessRequest is the core of the ASP.NET
		  implementation.
	</ul>


	Gonzalo has been working on an ASP.NET parser that takes .aspx
	files and generated the code required to run them (the code lives in
	module `xsp' along with a little web server for testing).

	Most of the runtime support was mostly written by Patrik Torstensson
	(now at Intel).  This was interesting, because in order to implement
	some of its features, Patrik had to go into the runtime/JIT engine and
	he spent a few weeks doing work there.

	Duncan got our System.Web assembly to compile.

** HttpRuntime

	Patrik has authored most of the HttpRuntime support (both on
	the System.Web and on the foundation) but it is still not
	ready to run.

** XSP

	Currently XSP provides the .aspx compiler to C#.  It would be
	interesting to see if it makes sense to extend the ASP.NET
	syntax to make it simpler to develop applications.

	Gonzalo is in charge of the compiler.

** Controls

	A lot of work has been put in the various classes that
	implement the controls (UI.HtmlControls and UI.WebControls),
	but they have been coded mostly in the dark, and without being
	able to test them in real life: Gaurav and Leen worked very
	hard on this namespace, but needs to be finished.

	We can now render all HtmlControls and some WebControls. Work is
	ongoing to make all WebControls render HTML.

** Extending ASP.NET

	Currently you have to reference in your ASP.NET the control
	and all of its properties, which works fine if you have a GUI
	designer, but is harder for people used to develop using text
	editors.

	Since we have a parser, we could extend this parser to allow
	people to still use ASP.NET controls, using a simpler syntax.
	For example people doing blogs and editing their templates
	over the web probably do not want to use direct ASP.NET but a
	wrapper around it.

** Roadmap

        1. The Parser.

        2. Get the parser to generate output compatible with ASP.NET.

        3. Run the sample output with the real Microsoft runtime
           but using our generated page.   

        4. Run the sample with our classes with the .NET runtime.
	<b>We are here</b>.

        5. Finish HttpRuntime.
	
        6. Running our sample code with our classes with our runtime.

** How to Help

        Currently we are testing and fixing HtmlControls, WebControls and
        validators.

        In the CVS module XSP you can find the aspx to C# page parser,
        a little web server used for testing and a directory containing
        sample aspx pages.

        You have some documentation under doc directory and in the README
        file of each directory. They explain how to test our System.Web.
        Testing is really easy!