WCF: where to host the configuration and how to resolve relative paths without an HTTPContext

Question

I recently decided to migrate existing asmx services to WCF. Now I have created a new solution that contains the WCF services library (it will eventually be a link to the WCF website).

My old code was heavily based on HTTPContext, but my understanding of this defeats the WCF Services point, which by its nature can be launched from any context, whether it be something from a console application into the MS Outlook plugin (fine, a bit extreme, but you get the idea).

Before I set my configuration in web.config, now I still save my configuration there, or more, to the WCF Libraries App.Config service.

Does the WCF website now have a more general way of referencing paths, not HTTPContext, but the application implementation path, so that I can write code once that works anywhere? (Note: In the past, the bin directory was in the asmx application startup path).

So, to summarize the following questions here:

• Where is the best place to store configuration values ​​in the web.config of the WCF website or in the app.config of the WCF service library?
• How can I avoid using HTTPContext for relative file locations and implement a more general approach to better take advantage of WCF services running anywhere.

Answer 1

• , WCF. , , WCF web.config -, . unit test, app.config .

• . , :

  Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
  

Answer 2

•   
• ,    web.config - WCF app.config WCF-?  

:

• WCF IIS, web.config
• , . WCF NT, - , WCF - app.config

( DLL) - .

2.   
3. HTTPContext    ,    , WCF .  

(, web.config/app.config) " ", , ,

<appSettings>
  <add key="BaseDirectory" value="D:\MyFiles" />
</appSettings>

- , HttpContext: -)

Answer 3

1

Marc_s:

• (IIS, VSDS, WAS ..), web.config.
• (WinForms, WPF, Service, Console ..), app.config.

, WCF , , . , , ( ) -.

2

- . HttpRuntime , IIS, HttpContext.

static string GetDataFilePath() {
    string path;
    if(HttpRuntime.AppDomainAppVirtualPath != null) {
        // We are hosted in IIS, so the data files are in the virtual directory data folder.
        path = Path.Combine(HttpRuntime.AppDomainAppPath, "App_Data");
    } else {
        // We are hosted in an application, so the data files are in the same directory as the assembly.
        path = Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
    }
    return path ?? string.Empty;
}

• If your host is a virtual directory, then put your data files in the App_Datahost project folder and set CopyToOutputDirectory = DoNotCopy.
• If your host is an application, then put your data files in the root of the host project and set CopyToOutputDirectory = CopyAlways.