blocks|key|3116439|text|为了引用像HttpContext对象这样的ASP.NET特性，你需要在ASP.NET兼容模式下运行你的WCF。这个article解释了如何做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3116440|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/wenlong/archive/2006/01/23/516041.aspx^0|1L|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

In order to reference ASP.NET features like the HttpContext object, you need to run your WCF app in ASP.NET compatibility mode. This <a href="http://blogs.msdn.com/wenlong/archive/2006/01/23/516041.aspx" rel="nofollow noreferrer">article</a> explains how to do this.

blocks|key|343462|text|请看下面宋乐的回答。它比这个好多了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|343463|更多信息后更新|343464|下面的方法对我很有效。我通过Service1.svc在IIS上托管了一个新的WCF服务，对它进行了测试。|343465|343466|将<serviceHostingEnvironment+aspNetCompatibilityEnabled="true"/>添加到web配置。<system.serviceModel>..</+..>已存在。|ordered-list-item|CODE|343467|将AspNetCompatibilityRequirementsAttribute添加到具有允许模式的服务。|343468|使用HttpContext.Current.Server.MapPath(".");获取根目录。|343469|343470|下面是服务类的完整代码。我没有在IService1界面中做任何更改。|343471|[AspNetCompatibilityRequirements(RequirementsMode=AspNetCompatibilityRequirementsMode.Allowed)]
public+class+Service1+:+IService1
{
++++public+void+DoWork()
++++{
++++++++HttpContext.Current.Server.MapPath(".");
++++}
}|code-block|syntax|javascript|343472|下面是web.config的摘录。|343473|<system.serviceModel>
++++
++++<serviceHostingEnvironment+aspNetCompatibilityEnabled="true"/>

++++
++++<behaviors>
++++++++
++++</behaviors>
++++<services>
++++++++
++++</services>
</system.serviceModel>|343474|旧答案|343475|你所说的工作文件夹是什么意思？WCF服务可以通过几种不同的方式和不同的端点进行托管，因此工作文件夹有点模棱两可。|343476|您可以通过调用Directory.GetCurrentDirectory()来检索普通的“工作文件夹”。|343477|HttpContext是一个ASP.Net对象。即使WCF可以托管在IIS上，它仍然不是ASP.Net，因此大多数ASP.Net技术在默认情况下都不起作用。OperationContext是HttpContext的等价物。OperationContext包含有关传入请求、传出响应以及其他内容的信息。|343478|不过，最简单的方法可能是通过在web.config中切换来在ASP.Net+compatibility+mode中运行该服务。这将使您能够访问ASP.Net+HttpContext。它将限制您只能使用*HttpBindings和IIS托管。要切换兼容模式，请将以下内容添加到web.config。|343479|<system.serviceModel>
++++<serviceHostingEnvironment+aspNetCompatibilityEnabled="true"/>
</system.serviceModel>|343480|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.io.directory.getcurrentdirectory.aspx|1|http://blogs.msdn.com/wenlong/archive/2006/01/23/516041.aspx^0|0|I|0|0|0|0|1|1Q|20|T|0|1|14|0|2|14|0|0|0|0|0|0|0|3|0|0|7|V|0|0|0|U|Q|1|0|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1T|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1U|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1W|8|@$9|1X|A|1Y|B|N]|$9|1Z|A|20|B|N]]|D|@]|E|$]]|$1|O|3|P|5|M|7|21|8|@$9|22|A|23|B|N]]|D|@]|E|$]]|$1|Q|3|R|5|M|7|24|8|@$9|25|A|26|B|N]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|27|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|28|8|@]|D|@]|E|$]]|$1|V|3|W|5|X|7|29|8|@]|D|@]|E|$Y|Z]]|$1|10|3|11|5|6|7|2A|8|@]|D|@]|E|$]]|$1|12|3|13|5|X|7|2B|8|@]|D|@]|E|$Y|Z]]|$1|14|3|15|5|6|7|2C|8|@$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|16|3|17|5|6|7|2F|8|@]|D|@]|E|$]]|$1|18|3|19|5|6|7|2G|8|@]|D|@$9|2H|A|2I|1|2J]]|E|$]]|$1|1A|3|1B|5|6|7|2K|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|2L|8|@]|D|@$9|2M|A|2N|1|2O]]|E|$]]|$1|1E|3|1F|5|X|7|2P|8|@]|D|@]|E|$Y|Z]]|$1|1G|3|-4|5|6|7|2Q|8|@]|D|@]|E|$]]]|1H|$1I|$5|1J|1K|1L|E|$1M|1N]]|1O|$5|1J|1K|1L|E|$1M|1P]]]]

Please see ongle's answer below. It is much better than this one.

Updated after more information

The following worked for me. I tested it with a new WCF Service I hosted on IIS through a Service1.svc.

<ol>
<li>Add <code>&lt;serviceHostingEnvironment aspNetCompatibilityEnabled="true"/&gt;</code> to web config. <code>&lt;system.serviceModel&gt;..&lt;/ ..&gt;</code> existed already.</li>
<li>Add <code>AspNetCompatibilityRequirementsAttribute</code> to the service with Mode Allowed.</li>
<li>Use <code>HttpContext.Current.Server.MapPath(".");</code> to get the root directory.</li>
</ol>

Below is the full code for the service class. I made no changes in the IService1 interface.

<pre><code>[AspNetCompatibilityRequirements(RequirementsMode=AspNetCompatibilityRequirementsMode.Allowed)]
public class Service1 : IService1
{
 public void DoWork()
 {
 HttpContext.Current.Server.MapPath(".");
 }
}
</code></pre>

And below is an excerpt from the web.config.

<pre><code>&lt;system.serviceModel&gt;
 &lt;!-- Added only the one line below --&gt;
 &lt;serviceHostingEnvironment aspNetCompatibilityEnabled="true"/&gt;

 &lt;!-- Everything else was left intact --&gt;
 &lt;behaviors&gt;
 &lt;!-- ... --&gt;
 &lt;/behaviors&gt;
 &lt;services&gt;
 &lt;!-- ... --&gt;
 &lt;/services&gt;
&lt;/system.serviceModel&gt;
</code></pre>

Old answer

What do you mean by the Working Folder? WCF services can be hosted in several different ways and with different endpoints so working folder is slightly ambiguous.

You can retrieve the normal "Working folder" with a call to <a href="http://msdn.microsoft.com/en-us/library/system.io.directory.getcurrentdirectory.aspx" rel="noreferrer">Directory.GetCurrentDirectory()</a>.

HttpContext is an ASP.Net object. Even if WCF can be hosted on IIS, it's still not ASP.Net and for that reason most of the ASP.Net techniques do not work by default. OperationContext is the WCF's equivalent of HttpContext. The OperationContext contains information on the incoming request, outgoing response among other things.

Though the easiest way might be to run the service in <a href="http://blogs.msdn.com/wenlong/archive/2006/01/23/516041.aspx" rel="noreferrer">ASP.Net compatibility mode</a> by toggling it in the web.config. This should give you access to the ASP.Net HttpContext. It will limit you to the *HttpBindings and IIS hosting though. To toggle the compatibility mode, add the following to the web.config.

<pre><code>&lt;system.serviceModel&gt;
 &lt;serviceHostingEnvironment aspNetCompatibilityEnabled="true"/&gt;
&lt;/system.serviceModel&gt;
</code></pre>

blocks|key|3116470|text|aspNetCompatibilityEnabled="true“应该已经解决了我的问题，但是我得到了这个错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3116471|3116472|服务器未提供有意义的回复；这可能是由于约定不匹配、会话过早关闭或内部服务器错误造成的。|blockquote|3116473|3116474|3116475|我解决了从当前应用程序域获取正在运行的WCF服务的物理路径的问题：|3116476|AppDomain.CurrentDomain.BaseDirectory|code-block|syntax|javascript|3116477|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|W|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

The aspNetCompatibilityEnabled="true" should have resolved my problem, but I got this error:

<blockquote>
 The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
</blockquote>

I resolved my problem with getting the physical path of my running WCF service by getting it from my current app domain:

<pre><code>AppDomain.CurrentDomain.BaseDirectory
</code></pre>

blocks|key|3329339|text|我需要为我的IIS6托管的WCF应用程序提供相同的信息，我发现这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3329340|string+apPath+=+System.Web.Hosting.HostingEnvironment.ApplicationPhysicalPath;|code-block|syntax|javascript|3329341|和往常一样，YMMV。|3329342|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I needed the same information for my IIS6 hosted WCF application and I found that this worked for me:

<pre><code>string apPath = System.Web.Hosting.HostingEnvironment.ApplicationPhysicalPath;
</code></pre>

As always, YMMV.

blocks|key|3116641|text|这取决于你想要什么。我通常想解析一个像“~/文件夹/文件”这样的url。这就是有效的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3116642|System.Web.Hosting.HostingEnvironment.MapPath("~/folder/file");|code-block|syntax|javascript|3116643|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Depending on what you want. I usually want to resolve a url like "~/folder/file". This is what worked.

<pre><code>System.Web.Hosting.HostingEnvironment.MapPath("~/folder/file");
</code></pre>

blocks|key|3116654|text|在WCF中使用HostingEnvironment.ApplicationPhysicalPath来查找应用程序的物理路径。通过System.Web.Hosting使用命名空间；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3116655|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Use HostingEnvironment.ApplicationPhysicalPath in WCF to find your application physical path.
Use namespace 
using System.Web.Hosting;

blocks|key|346959|text|更一般地说，我使用的是这个|type|unstyled|depth|inlineStyleRanges|entityRanges|data|346960|AppDomain.CurrentDomain.BaseDirectory|code-block|syntax|javascript|346961|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

More general, I am using this one

<pre><code>AppDomain.CurrentDomain.BaseDirectory
</code></pre>

I want to get the working folder of a WCF application. How can I get it? 

If I try

<pre><code>HttpContext.Current.Request.MapPath(HttpContext.Current.Request.ApplicationPath)
</code></pre>

I get a null reference exception (the Http.Current object is null).

<hr>

What I meant with the working folder was the folder where my WCF service is running. If I set <code>aspNetCompatibilityEnabled="true"</code>, I get this error:

<blockquote>
 The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
</blockquote>

How to get working path of a wcf application?

我想获取WCF应用程序的工作文件夹。我怎么才能得到它呢？如果我尝试HttpContext.Current.Request.MapPath(HttpContext.Current.Request.ApplicationPath)我得到一个空引用异常( Http.Current对象为空)。我所说的工作文件夹就是我的WCF服...

问如何获取wcf应用程序的工作路径？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何获取wcf应用程序的工作路径？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何获取wcf应用程序的工作路径？
EN