X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fasp-net;h=562c7e411f933f1432ea6b84ac770e76097ca1c1;hb=6d244cc6a029eb048a31840c7e89ea477a08c80b;hp=f94d81b104da9184ea7a10b95342f2dcf98ee2c3;hpb=bd03a71eccbe12ba720475e727da9dce1e68a8f5;p=mono.git
diff --git a/web/asp-net b/web/asp-net
index f94d81b104d..562c7e411f9 100755
--- a/web/asp-net
+++ b/web/asp-net
@@ -7,116 +7,73 @@
* Web Services (the SOAP-based rpc system).
- 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.
-
- 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.
-
-* Web Forms: The pieces
-
- There are a couple of components to the puzzle:
-
-
- * .aspx page parser (converts .aspx to C# code).
-
- * System.Web.HttpRuntime support.
-
- * Web controls (System.Web.UI.HtmlControls and
- System.Web.UI.WebControls).
+ Both are fully functional at this point.
- * Underlying infrastructure for the controls (System.Web.UI).
+ Publicly available applications such as
+ IBuySpy, nGallery and
+ many others are known to work.
+
+ Web Services stack is being used for commercial applications
+ such as
+ SourceGear's Vault. They
+ even funded the development of our Web Services classes back in
+ 2002. Another example is OpenLink's
+ Virtuoso. People
+ from OpenLink also contributed to Mono.
- * HttpRuntime.ProcessRequest is the core of the ASP.NET
- implementation.
-
-
-
- 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.
+* Hosting ASP.NET
- The classes for running ASP.NET are being actively written.
- Gaurav, Leen and Patrik worked in the core of the classes
- required to run ASP.NET web application as well as a small
- embeddable web server.
+ Using ASP.NET System.Web.Hosting namespace classes you can make
+ your own ASP.NET enabled server.
- 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:
+
+ * XSP: 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.
+ * mod_mono: An Apache module that
+ works with both 1.3 and 2.0 versions.
+
+
** 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
+ download page or from the Anonymous CVS 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.
- We are here.
+ 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
+
+** mod_mono
- Currently we are testing and fixing HtmlControls, WebControls and
- validators.
+ This Apache module is available from our download page. The
+ cvs 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.
+
+Last updated: Sat, 12 Jun 2004 05:07:31 GMT
+