+ All of these tools should be written using C#.
+
+ For the tools that are typically command line tools: Try to
+ write these as components that could load their input from
+ streams or collections of streams, and implement the command
+ line tools as wrappers around those classes.
+
+ For example, we will be making the C# compiler a component
+ that could be reused by applications that might have a use for
+ the various bits of the compiler (either to embed the
+ compiler, or reuse the code generator part of it).
+
+ This is important so that these components (compiler,
+ assembler, linker, etc) can be integrated later into the
+ visual development environment (hopefully with the help of the
+ SharpDevelop hackers).
+
+TODO=ilasm,IL Assembler
+** IL Assembler.
+
+ This assembler should basically take as input a file
+ containing IL bytecodes as specified in the `Partition II' of
+ the ECMA spec, and produce a binary file.
+
+TODO=al,Assembly Linker
+** Assembly Linker.
+
+ This tool is used to construct assemblies, which are basically
+ deployment units for CLI executables.
+
+TODO=debugger,Debugger