|
From: Martin A. <mar...@go...> - 2006-09-14 06:42:12
|
Hi Owen your description is exactly what I meant. Wish I have such a good wording :-) Also it would a little unify both runners (console and service). Martin Aliger > hi martin, > > On 13/09/06, Martin Aliger <mar...@go...> wrote: > > do you think, it is reasonable to add some config to > ccnet.exe.config > > with location of the ccnet.config? > > what do you perceive the benefit to be? > thinking it through a bit: we typically put our ccnet.config > file under version control and set up a ccnet project to > monitor it. this allows any developer to update it and add > new projects, etc. as a result, the ccnet.config file is > generally not stored in the same location as the ccnet > server. we generally use a batch file to start up ccnet > console and point it at the ccnet.config file. putting the > ccnet.config file location in the ccnet.exe.config file would > simply this somewhat and eliminate the need for the batch file. > > > I know there is -config:configfilename console option. Service has > > this option, so I'd like to have the same on console. > > > > <add key="ccnet.config" value="c:\some\path\to\ccnet.config"/> > > > > Or is it there and not documented? > > it's not currently supported. adding support would be > straightforward. > cheers, > owen. |