* 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.
+ ASP.NET support is divided in two pieces:
+ <ul>
+ * Web Forms (Web Applications infrastructure).
- There are a couple of components to the puzzle:
+ * Web Services (the SOAP-based rpc system).
+ </ul>
- <ul>
- * .aspx page parser (converts .aspx to C# code).
+ Both are fully functional at this point.
- * System.Web.HttpRuntime support.
+ Publicly available applications such as <a
+ href="http://www.asp.net/Default.aspx?tabindex=5&tabid=42">
+ IBuySpy</a>, <a href="http://www.ngallery.org/">nGallery</a> and
+ many others are known to work.
+
+ Web Services stack is being used for commercial applications
+ such as <a
+ href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">
+ SourceGear</a>'s <a
+ href="http://www.sourcegear.com/vault/index.asp">Vault</a>. They
+ even funded the development of our Web Services classes back in
+ 2002. Another example is OpenLink's
+ <a href="http://www.openlinksw.com/virtuoso/">Virtuoso</a>. People
+ from OpenLink also contributed to Mono.
- * 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>
+* Hosting ASP.NET
- 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).
+ Using ASP.NET System.Web.Hosting namespace classes you can make
+ your own ASP.NET enabled server.
- 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
+ However, if you want to take the easy path, we provide two
+ different mechanisms for hosting ASP.NET applications:
+ <ul>
+ * <a href="#xsp">XSP</a>: A light-weight web server
+ written in C#.
- 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.
+ * <a href="#mod_mono">mod_mono</a>: An <a
+ href="http://httpd.apache.org">Apache</a> module that
+ works with both 1.3 and 2.0 versions.
+ </ul>
+<a name="xsp">
** 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.
+ XSP is a simple web server written in C# that can be used to
+ run your ASP.NET applications. The code is available from our
+ <a href="download.html">download page</a> or from the <a
+ href="anoncvs.html">Anonymous CVS</a> repository (module name:
+ xsp).
+
+ A couple of classes of this new server can be reused/extended
+ to make an apache module/cgi using mono (MonoWorkerRequest and
+ MonoApplicationHost). This server also uses a couple of
+ plugins distributed with Mono to support gzip HTTP transfers.
- 4. Run the sample with our classes with the .NET runtime.
- <b>We are here</b>.
+ There is also a set of pages, controls and web services that you
+ can use to test the server and see how ASP.NET looks like.
- 5. Finish HttpRuntime.
+ As XSP is written in C# and uses System.Web classes to perform
+ its job, it also works under MS runtime.
- 6. Running our sample code with our classes with our runtime.
-
-** How to Help
+<a name="mod_mono">
+** mod_mono
- Currently we are testing and fixing HtmlControls, WebControls and
- validators.
+ This Apache module is available from our <a
+ href="download.html">download page</a>. The <a href="anoncvs.html">
+ cvs</a> module name is mod_mono.
- 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.
+ It allows apache to serve ASP.NET pages by proxying the requests
+ to a slightly modified version of our XSP called mod-mono-server
+ that is installed along with XSP.
- 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!
+ It does not work on Windows.
+<div align="bottom">
+<small>Last updated: Sat, 12 Jun 2004 05:07:31 GMT</small>
+</div>
projects / mono.git / blobdiff