.NET Tips and Tricks Blog by Peter Vogel. Hiding Methods from IntelliSense Believe it or not, there are times when you have a member in your class that you don't want to appear in the class's IntelliSense lists.
Because my method will never be called by a developer, it doesn't make a lot of sense to have that method cluttering up the class's IntelliSense list. To stop that method from appearing in the class's IntelliSense list, I could decorate the method with the EditorBrowsable attribute, passing the enumerated value EditorBrowsableState.Never. Here's the method from that column with the attribute applied to it: <EditorBrowsable(EditorBrowsableState.Never)> Public Function ToString1(format As String, formatProvider As IFormatProvider) As... Ramblings in Valve Time. Coding Horror. My History of Visual Studio (Part 7) - Rico Mariani's Performance Tidbits. [All the other Parts: History of Visual Studio] [I know I promised to talk about “Whidbey” in this installment but I realized I needed a bridge to get there or else I’d totally skip over “Everett” – so this is that bridge.]
In MSN the arrival of the .NET Framework and Visual Studio .NET was like a breath of fresh air. My team was working on (among other things) a COM based object model for a content management system. I once estimated that fully half the code was associated with the implementation of IUnknown in direct or aggregated cases (let’s hear it for punkOuter) or else tricky ref count management – to say nothing of the similar code that was in every client. Using the old code as a reference, just one developer was able to re-implement the entirety of the interfaces – save one class which we chose to wrap with COM interop instead – in about 3 months.