[MonoDevelop] Stub generation addin for MonoDevelop

Michael Hutchinson m.j.hutchinson at gmail.com
Thu Apr 2 21:25:39 EDT 2009

2009/4/2 Anirudh <anirudh at anirudhsanjeev.org>:
> I just had a few small questions
> What do I set the MONODEVELOP_CONSOLE_LOG_LEVEL environment variable to as
> to ensure maximum verbosity, and force the logs to get printed on stderr?


> Is there any way to enable tracing, so I can see what code is executed as I
> use the IDE itself?
> I'm able to build/debug monodevelop from the project IDE itself, and am able
> to see changes made to the code. Is this the standard procedure that you use
> to develop? Are there any fancy scripts/environment variables which make
> building and debugging the IDE any easier?

This should work, yes, at least for main.

"make run" is pretty handy if you want to build form the command-line.
In main there are also make targets for profiling. It should be pretty
easy to copy one of the profiling targets and alter it to trace
instead (pass --trace to mono). Beware raw tracing is very noisy,
though there are a number of options you can use to control it. It's
probably easier just to ask us where things are :)

> Also, I'm opening main/main.sln because the project on the root of the trunk
> refused to build. Would there be any problems with that?

Some of the extras are often unbuildable, yes, so if you try to build
*everything* it'll choke one one of them. Unless you specifically need
to edit one of them, it's easier just to edit main.

Michael Hutchinson

More information about the Monodevelop-list mailing list