471,605 Members | 1,503 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,605 software developers and data experts.

designing an application in winforms ????

I'm into designing an application in winforms but in near future my client may request the same thing in webforms. so

(1) what are all the design guidelines and ways are there to migrate easily in future (winforms -> weforms)...?

(2) how can i design my application which can be accessed in both winforms and webforms by not writing much of code for the same business logic. ?

(3) which is the cost effective method ?

Please guide me to design in such way that (1) I can migrate easily (2) I can run winforms and webforms parallely
Thanks,

Maheshkumar.R
http://spaces.msn.com/members/cyberiafreak
Dec 10 '05 #1
2 1974
The basic concept is to separate out the presentation logic from the
business
logic. The key is that the business logic knows nothing of the
presentation
implementation. eg don't pass a textbox to the business logic.

http://www.geocities.com/Jeff_Louie/OOP/oop3.htm

Regards,
Jeff

*** Sent via Developersdex http://www.developersdex.com ***
Dec 10 '05 #2

If you use an n-tier architecture, using well established design
patterns (look up Gang of Four, Patterns of Enterprise Application
Architecture - Martin Folwer). You can use an architecture which will
allow you to completly seperate business and data logic from the
presentation. If your client wants a web front end all you need to
develop is a the front-end your back end should be completly re-usable.
When you are developing the windows form application you could use web
services to allow the client to communicate with the server making the
backend code web-enabled and ready for developing the web front end at
a later date.
Hope this helps.
Mahesh Kumar.R wrote:
I'm into designing an application in winforms but in near future my client may request the same thing in webforms. so

(1) what are all the design guidelines and ways are there to migrate easily in future (winforms -> weforms)...?

(2) how can i design my application which can be accessed in both winforms and webforms by not writing much of code for the same business logic. ?

(3) which is the cost effective method ?

Please guide me to design in such way that (1) I can migrate easily (2) I can run winforms and webforms parallely
Thanks,

Maheshkumar.R
http://spaces.msn.com/members/cyberiafreak


Dec 10 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

12 posts views Thread by Seth Bourne | last post: by
1 post views Thread by XIAOLAOHU | last post: by
reply views Thread by leo001 | last post: by
reply views Thread by MichaelMortimer | last post: by
reply views Thread by CCCYYYY | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.