Proposals

From $1
    Table of contents

    This is a list of features and changes that have been proposed to include in MonoDevelop. Those proposals need further refinement and discussion, so feel free to provide your feedback in each proposal page or through the mailing list. Thanks for your help!

    Project Model

    Status Imp. Compl. Ver. Owner
    Auto-population (and hiding) of AssemblyInfo.cs Proposal Normal Low
    NAnt integration Proposal Low Medium

    Tools

    Status Imp. Compl. Ver. Owner
    Translation          
    Proposal Low Medium

    Tag page
    • No tags

    Files (0)

     
    Viewing 5 of 5 comments: view all
    Curious if it would be possible / worthwhile to port MonoDevelop as a MoonLight application.
    Posted 11:44, 6 Oct 2009
    What would be extremely helpful was a way to have a MD plugin to create Addins.
    Like Eclipse, where you can edit the foo.addin.xml file "graphically", so you don't have th write xml by hand.
    This could be a template like a C# file, with an special editor window.
    It would help really to make creating of mono.addins apps easier.
    Posted 20:42, 11 Jul 2010
    can Mono open Visual studio sln files and update them so that these sln and project files still work for Visual studio ?
    Posted 10:38, 18 Jan 2011
    Is there something like the Visual Studios Class Designer, which allows graphical design of code
    Posted 18:49, 10 May 2011
    Hello - This a request.

    Could you please add a tool or algorithm to obfuscate C# source level code. I use Unity Indie Version and I like to hide the readability of the code.

    - Renaming:
    Renaming scripts, classes, methods, fields into a set of meaningless or unreadable characters;
    Supporting obfuscation control attributes...

    - Removing events and properties:
    This method comes down to removing the metadata of events and properties from the assembly, which makes it impossible to recover or use these properties from high-level languages....

    - Renaming methods, variables, etc. into a set of unreadable characters:
    It comes down to replacing names with unreadable characters, for example, Japanese characters. Though .Net works with the UTF8 encoding, not all decompilers correctly process its characters. Some change names with such characters for more understandable, some replace unreadable character....

    - Source code level if not at the compiler level

    Thanks Mage
    Posted 02:13, 7 Jun 2011
    Viewing 5 of 5 comments: view all
    You must login to post a comment.
    Page last modified 12:02, 27 Oct 2009 by Lluis