[MonoDevelop] Documentation on hardcore features of Monodevelop

Etienne Fortin etienne.fortin at sympatico.ca
Tue Nov 11 07:28:01 EST 2008



Michael Hutchinson a écrit :
>
>> 2) Add custom commands. I used a pyton script with Visual Studio 2008
>> Express that automated the namespace naming based on the directory source
>> tree (ie where the source file is located in that tree). Right now I need to
>> add the custom command manually after the project is created. I would like
>> it to be put in there by the template. I guess it must go in the <Options>
>> tag of a project, but I can't figure out what value to put in there.
>>     
>
> I don't think custom commands can be added by templates,
> unfortunately. Could you file an enhancement bug?
>
>   
Done

> For this specific thing though, there's a checkbox on the project
> options that sets the namespace for new files based on the directory
> name.
>
>   
In noticed. I really didn't look at it that much so what I'll say may be 
completely off track (and I don't have my Monodevelop nearby to verify, 
it is compiling the latest trunk version of mono right now), but I 
believe it adds the base namespace prefix to the directory structure, 
starting with the base directory of the project. The thing is I like to 
put my source files under a "sources" directory. And I don't want 
"sources" to appear in the namespace. Maybe a setting stating where is 
the root dir of the sources tree would be an interesting addition. 
Enhancement bug? :)

>> 3) Linked to 1), but instead of adding files based on templates, add files
>> residing in the directory of the template. Useful for what I want to do in
>> 1). Something like <File path="myfile.some_extension"/>
>>     
>
> You can currently link other file templates, but not arbitrary files.
> This might be a useful feature. Could you file an enhancement bug?
>
>
>   
Done.

> Thanks!
>
>
>   


More information about the Monodevelop-list mailing list