ApplicationPhysicalPath is null?

Question

When my Windows Service(WCF service in selfhost) is starting up(ServiceBase.Main) I got some code that needs to know the ApplicationPhysicalPath.

The problem is that System.Web.Hosting.HostingEnvironment.ApplicationPhysicalPath is always null?

Why? And is there any workaround?

Does http://stackoverflow.com/questions/791468/how-to-get-working-path-of-a-wcf-application help? — Daniel Kelley, Jan 25 '13 at 14:56
No it does not, none of the top 2 answers solves the problem :( — Banshee, Jan 25 '13 at 14:59
Did you check the third answer? Seems to be the best solution according to the community — Thomas Lindvall, Jan 25 '13 at 15:01

score 4 · Accepted Answer · answered Jan 25 '13 at 16:14

4

Its null because a Windows Service has nothing to do with Web hosting (unless you create a WCF ServiceHost inside it that's configured with an http binding).

How about just falling back to System.Environment.CurrentDirectory?

answered Jan 25 '13 at 16:14

ErnieL

5,745
1
21
27

score 1 · Answer 2 · answered Jan 26 '13 at 05:43

1

Have you tried Assembly.CodeBase or Assembly.Location instead?

        Assembly.GetExecutingAssembly().CodeBase
        Assembly.GetExecutingAssembly().Location

answered Jan 26 '13 at 05:43

Simon

32,406
17
127
196

ApplicationPhysicalPath is null?

2 Answers2