[MonoDevelop] what's your top ten resharper features.

Pedro Ignacio Guridi pedro.guridi at gmail.com
Sun Mar 22 14:42:33 EDT 2009


Another feature from eclipse:
When cursor over variable/method, pressing "Ctrl" turns the text into a
hyperlink, and clicking goes to declaration.
I found quit annoying the "long" way with the current contextual menu, takes
about 3 clicks. ( perhaps there's already a shorcut.., anybody knows? )


Regards,
Pedro




On Sun, Mar 22, 2009 at 3:18 PM, Vadim Chekan <kot.begemot at gmail.com> wrote:

> Feature from Eclipse: when set cursor at variable, highlight all
> references to this var in the code.
> Also each such highlight is reflected on the side bar (and is
> clickable) so finding usage of variable is easy visually.
>
> Vadim.
>
> 2009/3/19 Kris Ray <kray at landmarkdigital.com>:
> >
> > Mine:
> > #1 - extract method
> > #2 - rename (for all references to the property/method/class everywhere
> in
> > the project)
> >
> > thanks,
> > Kris
> >
> >
> > -----Original Message-----
> > From: monodevelop-list-bounces at lists.ximian.com on behalf of Oliver
> Stieber
> > Sent: Wed 3/18/2009 10:46 AM
> > To: monodevelop-list at lists.ximian.com
> > Subject: [MonoDevelop] what's your top ten resharper features.
> >
> > I'm still working on a resharper like addin and I would like to know what
> > are your top ten resharper features that you like. Well, maybe not all
> ten
> > but the things you like the most and the things it doesn't do that maybe
> it
> > should.
> >
> > Here's my list, let me know if you like it. Have any additions extensions
> to
> > it or any other ideas of things that you would like a resharper like
> addin
> > to do.
> >
> > Things I like in resharper aree.
> >
> > Compiler Warnings and Errors.
> > Tidying up / Creating using declarations.
> > Extract Method.
> > Could be declared in inner scope.
> > Unused static
> > Could be declared static.
> > Some of the code generation for inline construction and classes and field
> > setting.
> > Implement interface
> > Declare a variable at it's first assignment.
> >
> > And maybe a few others I forgotten.
> >
> > (things I hate are invert if statement, tried it once, was a bit of a
> fiddle
> > to undo and made my code really unflexable when it came to wanting to do
> > things in the future)
> >
> >
> > *****************************
> > Some things I would like to add that it doesn't do:
> > *****************************
> >
> > Suggest using an interface or base class when possible to use it instead
> of
> > the declared class (I think later version of resharper than I'm using do
> > this but I haven't come across it doing it yet).
> >
> > Show scope of a variable, and in the case of a variable being used before
> > it's assigned show the scopes that it wasn't assigned in.
> >
> > Move the variable to the inner scope it could have been declared in.
> >
> > Wrap a class, i.e. have a class as a private member and wrap all it's
> > methods for when you don't want to inherit it. (this may also be nice to
> do
> > with with event's when a method is hit too)
> >
> > *****************************
> > Some sudo-python features.
> > *****************************
> >
> > Based on the usage of a variable:
> >
> > declare it in the class, as a function parameter or as a variable in the
> > function. And suggest it as a variable name in code completion if the
> type
> > is correct.
> >
> > Create a new Class / Interface / Struct for the variable with members
> based
> > on the functions and fields / properties used on that variable.
> >
> > Create a new function based on how it's called.
> >
> >
> > *****************************
> >         Coding standards checks probably as an additional addin.
> > *****************************
> > Some basic, but hopefully extensible coding standards.
> >
> > Like using GetString, String.Format for strings and other (as defined by
> the
> > user) best practices, don't declare members public use properties. I'll
> > probably start with some of the IDesign list and see what can be
> automated.
> > Enforcing naming conventions as much as possible
> > Spell checking comments
> > Spell checking variables, function, class etc.. names (so long as Pascal,
> > Camel or C&R type naming conventions have been used)
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Automatically
> >
> >
> > _______________________________________________
> > Monodevelop-list mailing list
> > Monodevelop-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/monodevelop-list
> >
> >
> > _______________________________________________
> > Monodevelop-list mailing list
> > Monodevelop-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/monodevelop-list
> >
> >
>
>
>
> --
> >From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT
> is explicitly specified
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20090322/02c63960/attachment.html 


More information about the Monodevelop-list mailing list