asp-net 2.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. * ASP.NET
  2. The classes for running ASP.NET are being actively written.
  3. Gaurav, Leen and Patrik have been building the classes
  4. required to run ASP.NET web application as well as a small
  5. embeddable web server.
  6. Currently ASP.NET does not work, but work is underway. If you
  7. are interested in helping the effort please contact the
  8. mono-list mailing list.
  9. There are a couple of components to the puzzle:
  10. <ul>
  11. * .aspx page parser (converts .aspx to C# code).
  12. * System.Web.HttpRuntime support.
  13. * Web controls (System.Web.UI.HtmlControls and
  14. System.Web.UI.WebControls).
  15. * Underlying infrastrcture for the controls (System.Web.UI).
  16. * HttpRuntime.ProcessRequest is the core of the ASP.NET
  17. implementation.
  18. </ul>
  19. Gonzalo has been working on an ASP.NET parser that takes .aspx
  20. files and generated the code required to run them (the code lives in
  21. module `xsp').
  22. Most of the runtime support was mostly written by Patrik Torstensson
  23. (now at Intel). This was interesting, because in order to implement
  24. some of its features, Patrik had to go into the runtime/JIT engine and
  25. he spent a few weeks doing work there.
  26. Duncan last week got our System.Web assembly to compile, and he is in
  27. the process of getting the generated output to compile and link with our
  28. System.Web classes, but so far, most of the work has been in stubbing
  29. out the classes, just so we can get a clean compilation of the
  30. code.
  31. ** HttpRuntime
  32. Patrik has authored most of the HttpRuntime support (both on
  33. the System.Web and on the foundation) but it is still not
  34. ready to run.
  35. ** XSP
  36. Currently XSP provides the .aspx compiler to C#. It would be
  37. interesting to see if it makes sense to extend the ASP.NET
  38. syntax to make it simpler to develop applications.
  39. Gonzalo is in charge of the compil.er
  40. ** Controls
  41. A lot of work has been put in the various classes that
  42. implement the controls (UI.HtmlControls and UI.WebControls),
  43. but they have been coded mostly in the dark, and without being
  44. able to test them in real life: Gaurav and Leen worked very
  45. hard on this namespace, but needs to be finished.
  46. ** Extending ASP.NET
  47. Currently you have to reference in your ASP.NET the control
  48. and all of its properties, which works fine if you have a GUI
  49. designer, but is harder for people used to develop using text
  50. editors.
  51. Since we have a parser, we could extend this parser to allow
  52. people to still use ASP.NET controls, using a simpler syntax.
  53. For example people doing blogs and editing their templates
  54. over the web probably do not want to use direct ASP.NET but a
  55. wrapper around it.