Home/ Questions/Q 1024725
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T11:49:15+00:00

I’m writing a tool in C#.Net that will be used to generate Catalogs of

  • 0

I’m writing a tool in C#.Net that will be used to generate Catalogs of content which users can browse. Initially I am creating a WinForms based interface, but in the future I’d like to be able to create a web based interface as well. So I’ve been careful to generalize the interface to a Catalog so that it does not depend on a specific UI.

My only experience with web development has been creating my own HTML website back in the early 90’s, and I’ve done a little ASP (not ASP.NET). Now with ASP.NET it seems that I should be able to leverage my existing C#.Net object model, to create a web base interface. But I really hasn’t done anything with ASP.NET beyond a simple hello world example.

Are there any special considerations I should make in designing my object model so that later I can create a web interface to it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here are few things to follow:

    1. You should package your object model
      is separate project (that you need
      to do anyway to share it among
      different projects) and make sure
      that you do not add specific
      references to it (for example, don’t
      add System.Web, WinForms, WPF etc) –
      this will automatically avoid any
      unwanted dependencies.
    2. Try to have your classes as lean as possible. Avoid classes that track change states etc – in web scenario, tracking state over multiple requests is expensive. So it’s best to have to your objects carry data only.
    3. Consider the possibility that your objects may need to be serialized and/or passed over a wire. For example, a middle ware services serving both windows & web client. Or web page storing the object in the view-state.
    • 0