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 and the XSP page
15 Tim started work on the Web Services. Although we have a
16 SoapFormatter as part of the remoting infrastructure already
17 (contributed by Jesus), most people will be using the ASP.NET
18 Web Services support. Work for the supporting class libraries
19 just started recently.
21 * Web Forms: The pieces
23 There are a couple of components to the puzzle:
26 * .aspx page parser (converts .aspx to C# code).
28 * System.Web.HttpRuntime support.
30 * Web controls (System.Web.UI.HtmlControls and
31 System.Web.UI.WebControls).
33 * Underlying infrastructure for the controls (System.Web.UI).
35 * HttpRuntime.ProcessRequest is the core of the ASP.NET
40 Gonzalo has been working on an ASP.NET parser that takes .aspx
41 files and generated the code required to run them (the code lives in
42 module `xsp' along with a little web server for testing).
44 Most of the runtime support was written by Patrik Torstensson
45 (now at Intel). This was interesting, because in order to implement
46 some of its features, Patrik had to go into the runtime/JIT engine and
47 he spent a few weeks doing work there.
49 The classes for running ASP.NET are being actively written.
50 Gaurav, Leen and Patrik worked in the core of the classes
51 required to run ASP.NET web application as well as a small
52 embeddable web server.
54 Duncan got our System.Web assembly to compile.
58 Patrik has authored most of the HttpRuntime support (both on
59 the System.Web and on the foundation).
61 He is now working on finishing HttpRuntime and a few needed
66 Currently XSP provides the .aspx compiler to C#.
67 There is also a small web server for testing in module xsp
68 along with a bunch of .aspx pages to test the server.
70 The C# code generator is being moved to System.Web.Compilation.
72 Gonzalo is in charge of the compiler.
76 A lot of work has been put in the various classes that
77 implement the controls (UI.HtmlControls and UI.WebControls),
78 but they have been coded mostly in the dark, and without being
79 able to test them in real life: Gaurav and Leen worked very
80 hard on this namespace.
82 We can now render all HtmlControls and almost all WebControls.
83 DataGrid and DataList controls are being finisehd by Gaurav.
84 Xml control needs some work on System.Xml related to XSL.
88 Currently you have to reference in your ASP.NET the control
89 and all of its properties, which works fine if you have a GUI
90 designer, but is harder for people used to develop using text
93 Since we have a parser, we could extend this parser to allow
94 people to still use ASP.NET controls, using a simpler syntax.
95 For example people doing blogs and editing their templates
96 over the web probably do not want to use direct ASP.NET but a
103 2. Get the parser to generate output compatible with ASP.NET.
105 3. Run the sample output with the real Microsoft runtime
106 but using our generated page.
108 4. Run the sample with our classes with the .NET runtime.
110 5. Run the samples with our classes with the our runtime (without
113 6. Finish HttpRuntime.
116 7. Running our sample code with our classes with our runtime.
120 Testing and fixing HtmlControls, WebControls and validators is an
123 In the CVS module XSP you can find the aspx to C# page parser,
124 a little web server used for testing and a directory containing
127 You have some documentation under doc directory and in the README
128 file of each directory. They explain how to test our System.Web.
129 Testing is really easy!