"maya" wrote...
Thomas gave you excellent suggestion to where to begin, but I will anyway
answer some of the specific questions you had as well.
> it says on top of Acme.cs "namespace Acme" I assume this means
> Acme.cs has to be in a dir called 'Acme'? (am assuming namespace
> is equiv to Java's packages; is this right?)
Not quite. Java's packages are used for both logical and physical
structuring, but in .NET it's "only" the logical structure.
You can have the source code anywhere you like, and the MSIL (roughly
corresponding to Java's bytecode) is put into an assembly.
> public class Calendar : Control, IPostBackEventHandler,
> IPostBackDataHandler
>
> but Control is a class, not an interface (can u implement classes?)
Here it's actually similar to Java, that a class can extend only one
superclass, but implement many interfaces.
However, the syntax for extending and implementing is the same in C#, the
colon (

, which means that if it would have been Java, it would have looked
like:
public class Calendar
extends Control
implements IPostBackEventHandler, IPostBackDataHandler
/// Bjorn A