I forgot to mention, I tested this with ReSharper 4.5.1. build 1284 so it may or may not work with previous builds of ReSharper 4.5 or 4.5.1. The ReSharper 4.5.1 release version on the main ReSharper download page just don't work right so grab the latest (build 1284) from the nightly builds:
http://www.jetbrains.net/confluence/display/ReSharper/ReSharper+4.5+Nightly+Builds From: Lothan Sent: Monday, September 28, 2009 2:14 PM To: fluent-nhibernate@googlegroups.com Subject: Re: [fluent-nhib] Re: Hiding Useless Memembers (like ToString, GetType, etc) In ReSharper 4.x, check "Filter members by [EditorBrowsable] attribute" under Environment, IntelliSense, Completion Appearance. Once that's enabled, you can select whether you want to see members marked Always and/or Advanced. From: Stuart Childs Sent: Monday, September 28, 2009 10:17 AM To: fluent-nhibernate@googlegroups.com Subject: [fluent-nhib] Re: Hiding Useless Memembers (like ToString, GetType, etc) I really like this idea, especially since I can use it on a few "wart" members that have to be public but aren't really supposed to be used by consumers of the class. I can't seem to get it to work with ReSharper though, even if I tell it to filter based on the EditorBrowsable attribute. Works fine if I tell it to use Visual Studio IntelliSense behavior. I'll post a solution if I figure one out (and if anyone else already knows, please let me know!). Thanks, Miguel! On Mon, Sep 28, 2009 at 9:05 AM, Hudson Akridge <hudson.akri...@gmail.com> wrote: We can make it happen. We'll bring it up to James, he'll probably be for it. Right now, trunk is on a freeze until he returns from Australia (which should be very shortly). On Mon, Sep 28, 2009 at 8:42 AM, Miguel <m...@miguelmadero.com> wrote: Cool. I'm glad ppl like the idea (it's coming from here: http://www.clariusconsulting.net/blogs/kzu/archive/2008/03/10/58301.aspx), but can someone make it happen for Fluent NH? Or can they pull the changeset from my repository? I would be happy to do the change myself if someone is willing to review it and pull it if they're happy with it. Something I don't like a lot is that it relies on doing this a tn interface level, so in order to filter what you can see and be able to hide the members from object you'll have to get a reference to return an interface instead of the concrete type (which most objects for the fluent interface don't do at the moment). It's not a big deal, but they might not want to create all this extra interfaces. On Sep 27, 11:13 pm, Mikael Henriksson <mik...@zoolutions.se> wrote: > Very handy, I'll steal that idea and use myself! :) > > On Sep 27, 2009 8:29 AM, "Hudson Akridge" <hudson.akri...@gmail.com> wrote: > > That's not a bad idea. > > On Sun, Sep 27, 2009 at 1:02 AM, Miguel <m...@miguelmadero.com> wrote: > > > > > When designing fluent i... > - Hudsonhttp://www.bestguesstheory.comhttp://twitter.com/HudsonAkridge > > -- - Hudson http://www.bestguesstheory.com http://twitter.com/HudsonAkridge --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
