3 ASP.NET support is divided in two pieces:
5 * Web Forms (Web Applications infrastructure).
7 * Web Services (the SOAP-based rpc system).
10 There is work underway for both systems. The Web Forms
11 support is more advanced at this point, and various ".aspx"
12 programs can be run using the Mono runtime (embedded into
13 either the XSP server or the mod_mono Apache module).
15 We are now working bug fixing and adding missing features
16 after making the whole pipeline compatible with MS.
18 Tim started work on the Web Services. Although we have a
19 SoapFormatter as part of the remoting infrastructure already
20 (contributed by Jesus), most people will be using the ASP.NET
21 Web Services support. Work for the supporting class libraries
22 just started recently.
26 Patrik has authored most of the HttpRuntime support (both on
27 the System.Web and on the foundation).
29 We are currently working on this.
33 This is where initial development of the .aspx/.ascx/.asax compiler
34 to C# took place. That compiler is now integrated in System.Web classes
35 mostly under System.Web.Compilation namespace.
37 We added a new web server that works with mono and MS runtime and is
38 being used to debug our classes. It resides in xsp/server. A couple of
39 classes of this new server can be reused/extended to make an apache
40 module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
42 There is also a bunch of .aspx pages to test the server along with
43 a few user controls under xsp/test.
45 You can check it out from CVS and run 'make install' to test it.
49 A lot of work has been put in the various classes that
50 implement the controls (UI.HtmlControls and UI.WebControls),
51 but they have been coded mostly in the dark, and without being
52 able to test them in real life: Gaurav and Leen worked very
53 hard on this namespace.
55 We can now render all HtmlControls and almost all WebControls.
56 DataGrid and DataList controls are being finished by Gaurav.
57 Xml control needs some work on System.Xml related to XSL.
61 Currently you have to reference in your ASP.NET the control
62 and all of its properties, which works fine if you have a GUI
63 designer, but is harder for people used to develop using text
66 Since we have a parser, we could extend this parser to allow
67 people to still use ASP.NET controls, using a simpler syntax.
68 For example people doing blogs and editing their templates
69 over the web probably do not want to use direct ASP.NET but a
72 * Web Forms: The pieces (historical)
74 There are a couple of components to the puzzle:
77 * .aspx page parser (converts .aspx to C# code).
79 * System.Web.HttpRuntime support.
81 * Web controls (System.Web.UI.HtmlControls and
82 System.Web.UI.WebControls).
84 * Underlying infrastructure for the controls (System.Web.UI).
86 * HttpRuntime.ProcessRequest is the core of the ASP.NET
91 Gonzalo has been working on an ASP.NET parser that takes .aspx
92 files and generated the code required to run them (the code lives in
93 module `xsp' along with a little web server for testing).
95 Most of the runtime support was written by Patrik Torstensson
96 (now at Intel). This was interesting, because in order to implement
97 some of its features, Patrik had to go into the runtime/JIT engine and
98 he spent a few weeks doing work there.
100 The classes for running ASP.NET are being actively written.
101 Gaurav, Leen and Patrik worked in the core of the classes
102 required to run ASP.NET web application as well as a small
103 embeddable web server.
105 Duncan got our System.Web assembly to compile.
109 Testing and fixing HtmlControls, WebControls and validators is an
112 In the CVS module XSP you can find a small web server used for
113 testing and a directory containing sample aspx pages.
115 You have some documentation under doc directory and in the README
116 file of each directory. They explain how to test our System.Web.
117 Testing is really easy!
119 As the server also works with MS runtime, you can use it to check
120 what the expected results are.