Design pattern for Fat Client - Thin Client to use Common code?
Posted
by kurozakura
on Stack Overflow
See other posts from Stack Overflow
or by kurozakura
Published on 2010-05-14T02:44:03Z
Indexed on
2010/05/14
2:54 UTC
Read the original article
Hit count: 298
Windows-based client application and web-client application(consuming the same code which windows-client uses) what is the preferable pattern for this scenario? Is it ok to have the code in the common place where both the projects and refer it as dll i.e one which is a windows app and other which is going consume the same code which windows client will be exposing.
© Stack Overflow or respective owner