=============================================== Cerebrus, Can you pl. suggest an alternative to this problem? I resorted to this design considering client updates (one project & one exe for a particular task). Any light on how can it threaten the scalability?
Thanks, Vineet ================================================ On Jul 4, 11:24 am, Cerebrus <[email protected]> wrote: > Gosh! That's a horrible solution to a common enough problem. Do you > realize the scalability implications of this kind of design ? > > On Jul 3, 9:37 pm, Vineet <[email protected]> wrote: > > > > > --------------------------------------------------------------------------------------------------------------- > > 3) The reason as to WHY I maintain separate projects for separate > > forms--- > > This is to simplify client-updates. I distribute only .exe files to my > > clients. > > If there is any bug in my code, I can send only a small .exe file > > pertaining to that Form. This way, customer servicing is very easy.- Hide > > quoted text - > > - Show quoted text -
