Introduction

CS CODEDOM Parser is utility which parses the C# source code and creates the CODEDOM tree of the code (general classes that represent code, part of .NET Framework - namespace System.CodeDom) .

Current version (0.1) is limited - it parses code down to type members and their parameters, it has very limited support for expressions and it does not parse the statements inside members. There are two main reasons for why I stayed at this level now

First - It was enough for my needs (I wanted to do some code analysis to enforce coding standards)

On the other hand it also parses source code comments, so it can be used to analyze the interdependencies of code and comments.

Also the stability of this version is low - it's kind of alpha version. If anybody wants to help get this thing further he is welcomed.

The parser is based on Mono - CSharp Compiler code. I was looking around little bit around for available C# parser and C# parser building tools (I wanted C# parser in C#) and finally decided for Mono. For more details about exploitation of Mono parser and other possibilities I explored see section C# parser Tools.

At first I thought it is great idea to use language independent syntax tree and CodeDom looks nice. If some code analysis tool is build on it, it can work for any .NET language. Just need to change parser and rest is the same, sounds cool. But, after I've got into the CodeDom, I have found that a lot of language features (and not just C#, basically for any language) is missing and it is not possible to parse the source code fully. The main problem is in expressions and statements, where CodeDom has very limited set of classes - there is for instance no support for unary operation and more more issues.

I decided to continue with CodeDom, even with its limitations, because it was enough for purposes of analyzing code for coding standards (at least what I need now - it also enables to keep comments and code in one tree, which is something I liked), but it is open issue for the future development.

Here is list of issues I've found (and there is more,):

CodeCompile unit does not have space for using directives or ns members, so they are placed now into first default NS

using_alias_directive - no support found

nested namespaces - no support found ( so parser is flattening ns hierarchy)

jb2csharpThis is port of JB Parser and Lexer Generation for Java (which itself is port of bison and flex). But the current version is alpha and I was not able to make work even their calculator example (which authors claim it was working).

I've also looked at the MS Rotor project, the C# parser there is in C++ (and it is not Open Source license).

So finally I decided to use Mono source, I've used their lexer, jay and their jay grammar to generate my parser. It is the jay grammar I've use my code to create CodeDom objects.

Description of package

CS CODEDOM Parser package consist of :

CodeDom parser itself (/ directory)

NUnit tests for the parser (/NUnitTests directory)Contains bunch of tests, I've used to check functionality of the parser - if you want to run then you should have NUnit.

testParser (/testParser directory)Simple command line utility that tests the parser - it parses file (name supplied as cmd line parameter) and write to stdout the code, which is generated by CSharpCodeProvider (class in CodeDom).

CodeTreeView (/CodeTreeView directory)Simple windows application, which opens file and displays CODEDOM tree in left part (treeview control) and original source in right part (textbox control). When you click on tree node, textbox scrolls to show the code. It is something like very very simple source code viewer.

Licence

CS CODEDOM Parser and tools included in this package are distributed under the under GPL licence.

Latest Version

The Future

The basic idea about future development is to extend CodeDom to support all language features, so the sources can be completely parsed. (Alternative is to leave CodeDom and have its own syntax tree, but I still like the idea of the independent language tree structure, which can be used in different tasks).

Also parser should be improved to indicate location of syntax elements more exactly in the source file.

Better separation between the parser and CODEDOM builder is also needed.

If somebody likes the tool and wants to help with its improvements, he is welcome.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.