Design and Architecture

bugal wrote:

What is the best approach for client-server application?

bugal wrote:

or hard&complex ?

public abstract class MovableObject
{
  // Add base implementation
}

public class Legs : MovableObject
{
  // Do something
}

public class Wheels : MovableObject
{
  // Do something
}

public abstract MovableEgg
{
  public void Move();
}

public abstract EggWithLegs : MovableEgg
{
  public virtual void Move()
  {
    Console.WriteLine("I'm walking");
  }
}

public abstract EggWithWings : MovableEgg
{
  public virtual void Move()
  {
    Console.WriteLine("I'm flying");
  }
}

Interface IMovementMethod
{
    public void Move(Egg AnEgg,...);
}
Class Egg
{
    public IMovementMethod MovementMethod {get; set;}
    public void Move(...)
    {
        MovementMethod.Move(this,...)
    }
}

VuNic wrote:

Should I design it like this:

Member 8385949 wrote:

If all these other firms don't have Access, what other type of database should I
use?

Mycroft Holmes wrote:

the client will potentially need the exact version of office you are using.

devvvy wrote:

I just want to know "what's going to happen"

Richard MacCutchan wrote:

And why do you believe that developers are any better at foretelling the future than astrologers?

devvvy wrote:

However, is this a hint that .NET is legacy?

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
They hate us for our freedom![^]

Eddy Vluggen wrote:

Why is it that with each new thing, something else "needs to become legacy"?

Eddy Vluggen wrote:

WinRT is unmanaged, and will not replace the unmanaged environments.

Eddy Vluggen wrote:

WPF looks definitely looks like something worth investigating. No, WinForms isn't going away either

devvvy wrote:

I do both so no bias here but you can't deny most new jobs requires WPF not winform.

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
They hate us for our freedom![^]