Design Patterns In .net

[jackie999]

Hi all,

Theoretically, the code in VB.Net and ASP.Net are pretty much the same. So I'm thinking of developing a desktop application (using MVC design pattern as it supports code re-usability) and then convert it into a similar Web application ( which will be done using MVC) just like the desktop application .

What design patterns can be helpful in transfering or re-purposing a desktop application to a Web application?

Also if you could enlighten me on the code -reusability in this scenario, it would be really helpful for me.

Thanx.

[TRScheel]

Security is a major issue. A lot of what you can do on the desktop you can not do on a web application.

A good example would be writing a file. Chances are you will not be given that privilege on the web application by default.

Random input will almost happen on a web application as well and although you should code around it on the desktop application, if its going to happen, it will be on the web version of it.

Other things to consider is size. A 300kb snippet for the desktop is fine, and wont slow it up a bit. A 300kb snippet on the web could bring some users to a crawl (especially if it happens often).

[jackie999]

can you suggest me any design patterns for the above issue please??

[jackie999]

any other replies please.

[TRScheel]

An MVC model is a good way of going about it. We do that a lot around here. My suggestion would be to make a seperate library and create objects that you would use in both iterations of your program. For instance, a user object, address object, sql requests, xml requests/deciphering, etc. Then the actual program is just the user interface, and the functionality is pulled from the back end library.