467,116 Members | 1,224 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,116 developers. It's quick & easy.

Windows Service problem

Hi... Im making an instaler for the windows service I've recently
develop, my sevice needs a few config files to be located on the same
path of the executable file of the service, when I install the service
in a folder I put all the config files on this folder but the problem
is that when the service starts it cannot load that files because the
System.Environment.CurrentDirectory property points to windows\system32
and not to the instalation folder of the service where the files really
are... how to fix it...???

thank you

Mar 15 '06 #1
  • viewed: 1296
Share:
3 Replies
Is there any compelling reason you want to use public queues? Its far more
efficient and less error prone to use private queues. Offcourse you need to
know the name and location of the private queue upfront.

Ravi
<al****@gmail.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Hi... Im making an instaler for the windows service I've recently
develop, my sevice needs a few config files to be located on the same
path of the executable file of the service, when I install the service
in a folder I put all the config files on this folder but the problem
is that when the service starts it cannot load that files because the
System.Environment.CurrentDirectory property points to windows\system32
and not to the instalation folder of the service where the files really
are... how to fix it...???

thank you
Mar 15 '06 #2
Where did you see any mention of public or private queue's in this posting?

Willy.

"Ravi" <na********@bogusgmail.com> wrote in message
news:u1**************@TK2MSFTNGP11.phx.gbl...
| Is there any compelling reason you want to use public queues? Its far more
| efficient and less error prone to use private queues. Offcourse you need
to
| know the name and location of the private queue upfront.
|
| Ravi
| <al****@gmail.com> wrote in message
| news:11**********************@z34g2000cwc.googlegr oups.com...
| Hi... Im making an instaler for the windows service I've recently
| develop, my sevice needs a few config files to be located on the same
| path of the executable file of the service, when I install the service
| in a folder I put all the config files on this folder but the problem
| is that when the service starts it cannot load that files because the
| System.Environment.CurrentDirectory property points to windows\system32
| and not to the instalation folder of the service where the files really
| are... how to fix it...???
|
| thank you
|
|
Mar 16 '06 #3
Why are you refering to CurrentDirectory when loading config files? The
CurrentDirectory for a service is always System32.

Willy.

<al****@gmail.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Hi... Im making an instaler for the windows service I've recently
develop, my sevice needs a few config files to be located on the same
path of the executable file of the service, when I install the service
in a folder I put all the config files on this folder but the problem
is that when the service starts it cannot load that files because the
System.Environment.CurrentDirectory property points to windows\system32
and not to the instalation folder of the service where the files really
are... how to fix it...???

thank you
Mar 16 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Kris | last post: by
reply views Thread by Scott Davies | last post: by
10 posts views Thread by Ger | last post: by
reply views Thread by Charles Leonard | last post: by
1 post views Thread by Mahesh Devjibhai Dhola | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.