

My current implementation relies on my own custom formatting rules. The project can be broken down as: 1) Improve Formatting in the ClassPad Component 2) Show Project References in the ClassPad Component 3) Show Base Types in the ClassPad Component 4) Create an Assembly Browser Component 5) Create Separate Assembly Browser Application 6) Create New Class Wizard 7) AssemblyInfo Front-EndĬlassPad Component: Firstly, the ClassPad should include support for formatting of members in a user-defined way. It should also ideally launch XSP on demand to test drive the pages. The add-in can take inspiration from both WebMatrix and the new VS.NET 2005 development style for applications. We would like to see a MonoDevelop Add-in that would allow developers to maintain web sites with it. Last summer Michael Hutchinson and Blagovest Dachev created a GUI editor for ASP.NET pages. It should also be possible to fine-tune the result, by manually listing classes and members that must be extracted. Then the linker could be used on the resulting EcmaBasic.dll to produce a minimal set of libraries for mscorlib.dll, System.dll,. The Mark and Sweep needs to be very inclusive and should be possible to augment it with flags or extra work to do, so the behavior of the program can be customized.įor example, if we were to define an ECMA-basic profile (no Math, Reflection or anything like that, we would create a sample EcmaBasic.cs file that references all the methods in the ECMA basic profile.


Visit the new documentation for updated content.

This page is likely outdated (last edited on ).
