There is work underway for both systems. The Web Forms
support is more advanced at this point, and various ".aspx"
- programs can be run using the Mono runtime and the XSP page
- parser.
+ programs can be run using the Mono runtime, including IBuySpy.
- Tim started work on the Web Services early this week.
- Although we have a SoapFormatter as part of the remoting
- infrastructure already (contributed by Jesus), most people
- will be using the ASP.NET Web-services support. Work for the
- supporting class libraries just started recently.
+ ASP.NET works either embedded into
+ our XSP server test server or the mod_mono Apache module.
-* Web Forms: The pieces
+ We are now working bug fixing and adding missing features
+ after making the whole pipeline compatible with MS.
+
+ Tim started work on the Web Services. Although we have a
+ SoapFormatter as part of the remoting infrastructure already
+ (contributed by Jesus), most people will be using the ASP.NET
+ Web Services support. Work for the supporting class libraries
+ just started recently.
+
+ The major missing element is a complete XmlSerializer.
+
+** HttpRuntime
+
+ Patrik has authored most of the HttpRuntime support (both on
+ the System.Web and on the foundation).
+
+** XSP
+
+ This is where initial development of the .aspx/.ascx/.asax compiler
+ to C# took place. That compiler is now integrated in System.Web classes
+ mostly under System.Web.Compilation namespace.
+
+ We added a new web server that works with mono and MS runtime and is
+ being used to debug our classes. It resides in xsp/server. A couple of
+ classes of this new server can be reused/extended to make an apache
+ module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
+
+ There is also a set of .aspx pages to test the server along with
+ a few user controls under xsp/test.
+
+ You can check it out from CVS and run 'make install' to test it.
+
+** 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.
+
+ We can now render all HtmlControls and all WebControls.
+
+ Help in making the controls better is appreciated.
+
+** ASP.NET and free controls.
+
+ We want to encourage developers to create open source controls
+ that can be used both on Mono's ASP.NET and Microsoft's ASP.NET.
+
+* Web Forms: The pieces (historical)
There are a couple of components to the puzzle:
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
+ Most of the runtime support was 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.
+ Testing and fixing HtmlControls, WebControls and validators is an
+ easy way to help.
- 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.
+ In the CVS module XSP you can find a small 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!
+ As the server also works with MS runtime, you can use it to check
+ what the expected results are.
+
projects / mono.git / blobdiff