Hello Vikas,
Do you think Ankit's suggestion on using the
Assembly.GetExecutingAssembly() to get the executing assembly(it is the
windows service's exe image for your windows service case) and use its
"Location" or "CodeBase" property to get the physical path information.
BTW, if the path you want to use is fixed after you installed the windows
service(its assembiles) on the target machine, you can also consider create
a setup program for the windows service and get the installed location of
the application(in programfiles folder...) and write it in your servcie
application's app.config file. Do you think this also workable?
Please feel free to post here if you have any further question on this.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.