Ok, so here is the scenario. First, this app is not installed on any end user machine. This is the progression of events:
1) The user has a problem
2) They call the help desk
3) The helpdesk tries to correct the problem but cannot figure it out
4) The helpdesk calls my group
5) We ask them to collect certain data from the end user's machine
6) They either copy the app directly to the user's machine or they email it to them
7) They tell the user to double click the app
8) The app collects the data that we typically need and zips it all up into a file
9) The user emails the file back or the tech pulls it directly from the user's machine
10) The file is given to us and we do our thing
That is the way it works for 99% of the uses. What I am working on is the other 1%. Let's say that from the nature of the issue we suspect that we know the cause of the problem. To be sure though we need them to collect the contents of a specific registry key that we don't normally collect by default. Here is how I would like that to go:
Steps 1-6 are the same then:
7) The helpdesk tech takes remote control of the machine
8) The tech runs the app while holding the shift key down
9) the config dialog opens and they enter the path to the registry key that we need in a text field
10) They click ok
11) the data is collected along with the extra key.
Distributing a config shortcut is not really valid since the app is never distributed in the traditional sense. If it is not possible to do what I want, that is fine, but I would just like to know one way or the other.
[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]