Kron,
Have you tried it and compiled it?
public string Name {get; set;}
The above will not work. The compiler expects an implementation to the
property.
public abstract string Name {get; set;}
The above will work. It will require derived classes to override the
implementation.
If you want to provide a default implementation which can be overriden,
then you can use virtual:
public virtual string Name
{
get
{
return name;
}
set
{
name = value;
}
}
Hope this helps.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> Hi Folks
>
[quoted text clipped - 19 lines]
>
> Kron
kronrn@yahoo.com - 19 Aug 2006 18:17 GMT
Thanks Nicholas, your answer is most helpful :)
I played around with this after I posted and found the results to be
exactly as you say. Next time I'll try it out first ;)
Many Thanks
Kron
> Kron,
>
[quoted text clipped - 54 lines]
> >
> > Kron
Philip Daniels - 19 Aug 2006 19:08 GMT
>Kron,
>
[quoted text clipped - 4 lines]
> The above will not work. The compiler expects an implementation to the
>property.
Yep, but if you drop the "public" it will work in an interface, it's
the syntax for specifying a property member. (I am sure you knew this
but maybe not the O.P...)
--
Philip Daniels
Nicholas Paldino [.NET/C# MVP] - 21 Aug 2006 02:23 GMT
Philip,
If you drop off the public, then it is assumed to be private. You still
get a compiler error. It doesn't assume abstract when there is no public
access modifier.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
>>Kron,
>>
[quoted text clipped - 12 lines]
> --
> Philip Daniels
Carl Daniel [VC++ MVP] - 21 Aug 2006 02:37 GMT
> Philip,
>
> If you drop off the public, then it is assumed to be private. You
> still get a compiler error. It doesn't assume abstract when there is
> no public access modifier.
... unless it's in an interface definition, as the previous poster said.
-cd