If I have two apps (one is a standard VB.Net EXE, the other is a VB.Net
Windows Service).

The EXE is just a UI to configure the settings for the Service. But, each
one has their own App.Config.

What is the best way to "share" a file so one can write the configuration
information and the other read it?

I hope this made sense.

--
Thanks,

Scott

the registry is a very simple solution and is commonly used for this type of
functionality. it only get more complicated from there...i've known people
to even use named pipes for background communication. anyway, hth.

steve


"SQLScott" <(E-Mail Removed)> wrote in message
news943AF66-5EFD-4487-AF39-(E-Mail Removed)...
| If I have two apps (one is a standard VB.Net EXE, the other is a VB.Net
| Windows Service).
|
| The EXE is just a UI to configure the settings for the Service. But, each
| one has their own App.Config.
|
| What is the best way to "share" a file so one can write the configuration
| information and the other read it?
|
| I hope this made sense.
|
| --
| Thanks,
|
| Scott

Why not use a notification icon (like SQL Server Agent) that brings up the
UI and talks to it. 1 application then. no need for the second one or a
second config file..

-CJ

"SQLScott" <(E-Mail Removed)> wrote in message
news943AF66-5EFD-4487-AF39-(E-Mail Removed)...
> If I have two apps (one is a standard VB.Net EXE, the other is a VB.Net
> Windows Service).
>
> The EXE is just a UI to configure the settings for the Service. But, each
> one has their own App.Config.
>
> What is the best way to "share" a file so one can write the configuration
> information and the other read it?
>
> I hope this made sense.
>
> --
> Thanks,
>
> Scott

Scott,
I normally have the UI simply open the service's app.config file
(myservice.exe.config) as an XMLDocument, make any changes, then save it.

My UI then will restart the Service, so the service has a chance to reload
its settings.

My install project installs the UI & the service to the same folder under
\Program Files...

Hope this helps
Jay

"SQLScott" <(E-Mail Removed)> wrote in message
news943AF66-5EFD-4487-AF39-(E-Mail Removed)...
> If I have two apps (one is a standard VB.Net EXE, the other is a VB.Net
> Windows Service).
>
> The EXE is just a UI to configure the settings for the Service. But, each
> one has their own App.Config.
>
> What is the best way to "share" a file so one can write the configuration
> information and the other read it?
>
> I hope this made sense.
>
> --
> Thanks,
>
> Scott

Jay,

Excellent idea. Thanks for the feedback. Very much appreciated.

Scott

"Jay B. Harlow [MVP - Outlook]" wrote:

> Scott,
> I normally have the UI simply open the service's app.config file
> (myservice.exe.config) as an XMLDocument, make any changes, then save it.
>
> My UI then will restart the Service, so the service has a chance to reload
> its settings.
>
> My install project installs the UI & the service to the same folder under
> \Program Files...
>
> Hope this helps
> Jay
>
> "SQLScott" <(E-Mail Removed)> wrote in message
> news943AF66-5EFD-4487-AF39-(E-Mail Removed)...
> > If I have two apps (one is a standard VB.Net EXE, the other is a VB.Net
> > Windows Service).
> >
> > The EXE is just a UI to configure the settings for the Service. But, each
> > one has their own App.Config.
> >
> > What is the best way to "share" a file so one can write the configuration
> > information and the other read it?
> >
> > I hope this made sense.
> >
> > --
> > Thanks,
> >
> > Scott
>
>
>