On Thu, Oct 14, 2010 at 7:06 AM, Danny <[email protected]> wrote: > Hi, > > Environment: VB.Net (2008) windows application. > > When developing an generic application, it might be that some features > are different depending the target customer. > Also, each of the published setups should reside on a different ftp- > location. > > How to manage this: > - having (allmost) all source files common > - having some different resources (client logo, ...) (can be done/ > required to do explicitly) > - haning some menus different (more or less entrys) > > Having different behaviour can be steered by using some public > variable, even a debug variable: > Const CLIENTID=x .... If CLIENTID=x Then ... > # Const CLIENTID=x # If CLIENTID=x Then... > Nice would be that when started or compiled, there would be a prompt > for the client-id. > > During development, all source-files should be accessible, but when > compiling one setting (CLIENTID=x) should result in the corresponding > setup, being publisched on the corresponding FTP-location. ----------------
You have to drive all of this via metadata and not "Const CLIENTID=x .... If CLIENTID=x Then ..." The query of metadata uses the Where ClientID == oApp.ClientID -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell
