VS 2003 Tip #7: Implementing interface stubs automatically

re: VS 2003 Tip #7: Implementing interface stubs automatically

Matt Berther — Thu, 11 Mar 2004 00:38:00 GMT

You can always right click on the interface in the class browser and click Add | Implement interface.

ie:

ClassName
-- Bases and Interfaces
- IInterfaceName (Right click on this one and select Add | Implement Interface

re: VS 2003 Tip #7: Implementing interface stubs automatically

Omer van Kloeten — Thu, 11 Mar 2004 20:04:00 GMT

Please, oh please(!), stop placing the implementation stubs in a region... Or at least give me an option to disable it... It's pretty annoying... :/

re: VS 2003 Tip #7: Implementing interface stubs automatically

Shaykat — Thu, 11 Mar 2004 20:43:00 GMT

Hi Omar - you can disable the region getting collapsed (I think thats what you want) by turning the option off in Tools.Options.Text Editor.C#.Formatting.Outlining.Collapse # region blocks when files open.

re: VS 2003 Tip #7: Implementing interface stubs automatically

JuanC — Fri, 12 Mar 2004 21:40:00 GMT

It would be nice if whibey could support "shift-tab" to force an "explicit" interface implementation.

e.g.

void ITest.Foo1()
{
}

void ITest.Foo2()
{
}

Implement interface in Whidbey

Anson Horton's Blog — Sun, 14 Mar 2004 02:36:00 GMT

Shaykat's Visual Studio 2003 Tips

Code/Tea/Etc... — Sun, 14 Mar 2004 12:00:00 GMT

Shaykat's Visual Studio 2003 Tips

Code/Tea/Etc... — Sun, 14 Mar 2004 12:03:00 GMT

Implement interface in Whidbey

Anson Horton's Blog — Mon, 15 Mar 2004 01:54:00 GMT

re: VS 2003 Tip #7: Implementing interface stubs automatically

Omer van Kloeten — Wed, 17 Mar 2004 16:15:00 GMT

Hey Shaykat,

I was referring to not placing a region at all on the section.
And anyway, the "Tools.Options.Text Editor.C#.Formatting.Outlining.Collapse # region blocks when files open" option is too generic. I want it turned on, but I just want the #region pp-directive not written for interface implementations.

Omer

re: VS 2003 Tip #7: Implementing interface stubs automatically

Blake Ryan — Fri, 19 Mar 2004 09:08:00 GMT

I've noticed that an easier way to get the completion tooltip again is to type a comma after then interface name and then backspace it away. The implement interface tooltip will appear.

re: VS 2003 Tip #7: Implementing interface stubs automatically

Oskar Austegard — Mon, 22 Mar 2004 12:55:00 GMT

Have a look at what the JetBrains folks are planning for ReSharper regarding this: http://www.intellij.net/forums/thread.jsp?forum=37&thread=78680&tstart=0&trange=15#852024

Oskar

re: VS 2003 Tip #7: Implementing interface stubs automatically

Brian Morearty — Tue, 30 Mar 2004 16:48:00 GMT

My 2 cents: I love that it creates a #region around the methods.

I agree with the suggestion to provide a way to put the interface name on the methods. E.g., IDisposable.Dispose instead of just Dispose.

Awesome feature, by the way. Easy, useful, and discoverable.

re: VS 2003 Tip #7: Implementing interface stubs automatically

Kiwidude — Mon, 14 Jun 2004 16:19:00 GMT

A nice feature in theory, apart from one hugely awful bug. If your interface defines two methods with the same name overloaded, the "stubs" are only correct for one of the overloads. You end up with a mess of uncompilable code, which you have to manually edit by adding back in the 'public' modifier and removing the fully qualified namespace that it puts on the method name... a pretty crappy effort imho. Does anyone have a justification for why it does this or how on earth it got through "quality control"???

interface stubs

bonkey — Thu, 12 Aug 2004 17:44:00 GMT

interface stubs

bonkey — Thu, 12 Aug 2004 21:05:00 GMT

Shaykat's Visual Studio 2003 Tips

Code/Tea/Etc. — Wed, 25 Aug 2004 13:17:00 GMT