[Wrapper-user] Fwd: RE: No args wrapper startup [jredman@ergotech.com]

[Jim R. <ji...@er...>]

Sal,

Beyond the obvious observation that batch files are ugly, we have at 
least on sitution where a batch file will not work.  The OPC standard, 
which we support, mandates that one of the registry keys associated 
with an application is an executable, not a batch file.

In our case, it is the end users choice whether to install a service or 
not.  For some customers the applications will not run as a service, 
the application will grab the executable from the registry and run it 
and check that the application is still alive.  Others want a 
service.   Some want a real user interface, etc. etc. Hence the 
attraction of the wrapper, it does all these things.

> From: Sal Ingrilli <sal@sy...>
> RE: No args wrapper startup
> 2003-09-11 10:26

> i would definitely use the default "wrapper.conf" file name and 
> location if its "../conf/wrapper.conf" and it is relative to wrapper.
> exe.

In this case, you could only have one application per directory.  Might 
not be a restriction in your case, but are you sure you want to impose 
it upon everyone?
> i disagree with you on the default argument because the wrapper is a 
> service wrapper. i think that the default option should be to install 
> and start the service, as in "wrapper -it" i think that if you 
> wantthe default option to be "-c" you should create yourself a batch 
> filetorun your app.

If there's no interest, I'm going to hack this for myself.  If there's 
interest then I don't mind making a more general solution.  For 
example, double-clicking app.exe could read app.conf and find out what 
it's suppose to do next (install as service, run in console, etc.).  
That is, the default command line options could be encoded in the 
configuration file.

However it seems that there's _almost_ a mechanism similar to this in 
the build scripts, and I would want to re-invent something that already 
has a good solution.

Jim
PS There seems to be some disagreement between my mailer (Balsa) and 
the list server as to who I am, so my apologies for the ugly formatting.

> -----Original Message-----
> From: wrapper-user-admin@li...
> [mailto:wrapper-user-admin@li...]On Behalf Of Jim Redman
> Sent: Thursday, September 11, 2003 6:52 AM
> To: wrapper-user@li...
> Subject: [Wrapper-user] No args wrapper startup
> 
> I'd like to use the wrapper to start a console application.  But 
> Ineed a single executable that the user can click on, that is, no 
> argspassed to the application.
> 
> Is this possible without modifications to the c source?
> 
> If not, is anyone else interested in this?  My idea would be to have
> double-clicking on app.exe be the same as "app -c app.conf" if app.
> conf exists.

-- 

Jim Redman
(505) 662 5156 x85
http://www.ergotech.com