Just looked in the SDK docs. From the VB Language Reference section on the Function keyword
... Overridable Optional. Indicates that this Function procedure can be overridden by an identically named procedure in a derived class. Overridable is the default setting for a procedure that itself overrides a base class procedure. NotOverridable Optional. Indicates that this Function procedure cannot be overridden in a derived class. NotOverridable is the default setting for a procedure that does not itself override a base class procedure. ... So it seems that VB doesn't default to virtual, unless it's overriding an existing method. ______________________________ - David Lanouette - [EMAIL PROTECTED] "Excellence, then, is not an act, but a habit" - Aristotle > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Frans Bouma > Sent: Saturday, July 08, 2006 2:59 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Virtual methods in .NET - was > Implementing an Interface - C# vs. VB.NET > > > Virtual is default in VB.NET, not in C#... > > No, it's not :) > > FB > > > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
