I am new to the object oriented design world and to .NET . My company has given me a task to design an application which should work as a client/server application for a limitted time and to be converted to a web app later. From my experience I reached to the conclusion that it is better to go for a fully OO design with MVC architecture where at present I will use the VB.NET Forms as the client and later we can change to ASP.NET as the client.
In order to implement this I want the middle layer to be placed on the server and have to talk to these objects from the client[VB.NET Forms].
I think some one can guide me on this task [if possible with some examples]
Thanks in advance..
Regards
AGK
Client Server Application
Dmitry Shaporenkov
Hi, your approach makes sense. It is important to clearly separate your UI from your business logic as your UI will move from a Windows UI to a Web UI.
The overall MVC pattern will help; what you really want to do is create a set of services exposing your business logic and expose those services via a service interface (service facade); note that it does not necessarly means that you will build web services (WSDL/SOAP etc.) but it is an option you will want to consider.
here is a guide (a few years old) that should help you
http://msdn.microsoft.com/practices/apptype/webapps/default.aspx pull=/library/en-us/dnbda/html/distapp.asp
Fire Fox gug
Hey AGK,
The MVC pattern would be the best suited to the requirements that you have. I have implemented the MVC in a similar requirement. Here is the article that i referred to when i was designing the solution.
http://www.devx.com/dotnet/Article/10186/0/page/1
This provides code to implement and test the scenario.
Regards,
Amit
Sinatra
MVC pattern is implemented by the following application block which is available as source code: http://msdn.microsoft.com/practices/default.aspx pull=/library/en-us/dnpag/html/uipab.asp
Also, the following Smart Client composite application block:http://msdn.microsoft.com/practices/default.aspx pull=/library/en-us/dnpag2/html/cab.asp is laden with disign patterns like Inversion Of Control (or Dependency Injection), Strategy, Factory, etc.
Above blocks combined with clean separation of business logic into services can help you create a clean and resusable component architecture for both web and winform environments.
Hope this helps!
- Hanu