Recomended way to set end user defaults
Posted: Mon Nov 28, 2005 2:50 pm
Hello,
Is there a recommended way to create a setup that allows the end user to customize defaults?
For example my applications needs a SQL Server connection string. The IT departments that are deploying the software would like to be able to set that information before telling the users were the setup is located on the network. I don't want to prompt each user for the connection string. I just want a hook for Sys Admins to add that information to the setup if it is already known.
It does not really matter where the end result is located. I can move everything around once I can find the information. For example could the setup copy a external file called defaults.txt to the target directory when the setup is run? Where defaults.txt may or may not exist in the same directory as the setup?
Thanks,
Mark
Is there a recommended way to create a setup that allows the end user to customize defaults?
For example my applications needs a SQL Server connection string. The IT departments that are deploying the software would like to be able to set that information before telling the users were the setup is located on the network. I don't want to prompt each user for the connection string. I just want a hook for Sys Admins to add that information to the setup if it is already known.
It does not really matter where the end result is located. I can move everything around once I can find the information. For example could the setup copy a external file called defaults.txt to the target directory when the setup is run? Where defaults.txt may or may not exist in the same directory as the setup?
Thanks,
Mark