blocks|key|505759|text|不要忘了检查与绑定相关的代码。因此，如果你写道：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|505760|BasicHttpBinding+binding+=+new+BasicHttpBinding();|code-block|syntax|javascript|505761|确保您的所有app.config文件都包含|offset|length|style|CODE|505762|<endpoint+address="..."
++++++++++binding="basicHttpBinding"+...|505763|不是|505764|<endpoint+address="..."
++++++++++binding="wsHttpBinding"+...|505765|大概是这样。|505766|entityMap^0|0|0|6|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

Do not forget check the bindings-related code too.
So if you wrote:

<pre><code>BasicHttpBinding binding = new BasicHttpBinding();
</code></pre>

Be sure that all your <code>app.config</code> files contains

<pre><code>&lt;endpoint address="..."
 binding="basicHttpBinding" ...
</code></pre>

not the

<pre><code>&lt;endpoint address="..."
 binding="wsHttpBinding" ...
</code></pre>

or so.

blocks|key|721869|text|我今天看到了这种行为，当|type|unstyled|depth|inlineStyleRanges|entityRanges|data|721870|+++<service+name="A.B.C.D"+behaviorConfiguration="returnFaults">
++++++++<endpoint+contract="A.B.C.ID"+binding="basicHttpBinding"+address=""/>
++++</service>|code-block|syntax|javascript|721871|从web.config中消失了。service.svc文件就在那里，并得到了服务。我花了一段时间才意识到问题不在绑定配置本身……|offset|length|style|CODE|721872|entityMap^0|0|0|G|B|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I've seen this behavior today when the 

<pre><code> &lt;service name="A.B.C.D" behaviorConfiguration="returnFaults"&gt;
 &lt;endpoint contract="A.B.C.ID" binding="basicHttpBinding" address=""/&gt;
 &lt;/service&gt;
</code></pre>

was missing from the web.config. The <code>service.svc</code> file was there and got served. It took a while to realize that the problem was not in the binding configuration it self...

blocks|key|721949|text|我今天在尝试使用VS2010和svcutil创建WCF服务代理时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|721950|我所做的一切都是使用basicHttpBinding+(所以wsHttpBinding没有问题)。|offset|length|style|CODE|721951|在我的记忆中，MSDN第一次为我提供了解决方案，链接如下How+to:+Publish+Metadata+for+a+Service+Using+a+Configuration+File。我需要更改的行在我的服务app.config文件的MEX服务行为元素内的behavior元素内。我把它从|721952|<serviceMetadata+httpGetEnabled="true"/>++|code-block|syntax|javascript|721953|至|721954|<serviceMetadata+httpGetEnabled="true"+policyVersion="Policy15"/>|721955|就像魔术一样，错误消失了，我能够创建服务代理了。请注意，有一个对应的MSDN条目用于使用代码而不是配置文件：How+to:+Publish+Metadata+for+a+Service+Using+Code.。|721956|(当然，Policy15+-我怎么可能忽视这一点？)|721957|还有一个“问题”：我的服务需要公开3个不同的端点，每个端点都支持一个不同的契约。对于我需要构建的每个代理，我必须注释掉其他两个端点，否则svcutil会抱怨它无法解析基本URL地址。|721958|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/ms734765.aspx|1|https://msdn.microsoft.com/en-us/library/aa738489%2528v=vs.100%2529.aspx^0|0|A|G|U|D|0|S|1T|0|0|0|0|0|1I|1E|1|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1E|8|@]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|J|3|K|5|L|7|1I|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1K|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1L|8|@]|9|@$D|1M|E|1N|1|1O]]|A|$]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]]]

I saw this problem today when trying to create a WCF service proxy, both using VS2010 and svcutil.
Everything I'm doing is with <code>basicHttpBinding</code> (so no issue with <code>wsHttpBinding</code>).
For the first time in my recollection MSDN actually provided me with the solution, at the following link <a href="https://msdn.microsoft.com/en-us/library/ms734765.aspx" rel="nofollow noreferrer">How to: Publish Metadata for a Service Using a Configuration File</a>. The line I needed to change was inside the behavior element inside the MEX service behavior element inside my service app.config file. I changed it from
<pre><code>&lt;serviceMetadata httpGetEnabled=&quot;true&quot;/&gt; 
</code></pre>
to
<pre><code>&lt;serviceMetadata httpGetEnabled=&quot;true&quot; policyVersion=&quot;Policy15&quot;/&gt;
</code></pre>
and like magic the error went away and I was able to create the service proxy. Note that there is a corresponding MSDN entry for using code instead of a config file: <a href="https://msdn.microsoft.com/en-us/library/aa738489%28v=vs.100%29.aspx" rel="nofollow noreferrer">How to: Publish Metadata for a Service Using Code.</a>
(Of course, Policy15 - how could I possibly have overlooked that???)
One more &quot;gotcha&quot;: my service needs to expose 3 different endpoints, each supporting a different contract. For each proxy that I needed to build, I had to comment out the other 2 endpoints, otherwise svcutil would complain that it could not resolve the base URL address.

blocks|key|505932|text|我最近也面临着同样的问题。经过几个小时的努力，终于有了一个解决方案，除了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|505933|Factory="System.ServiceModel.Activation.WebServiceHostFactory"
to+your+SVC+markup+file.+e.g.
ServiceHost+Language="C#"+Debug="true"+Service="QuiznetOnline.Web.UI.WebServices.LogService"+
Factory="System.ServiceModel.Activation.WebServiceHostFactory"+|code-block|syntax|javascript|505934|现在你可以成功编译和运行你的应用程序了。|505935|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 was also facing the same problem recently. after struggling a couple of hours,finally a solution came out by addition to 

<pre><code>Factory="System.ServiceModel.Activation.WebServiceHostFactory"
to your SVC markup file. e.g.
ServiceHost Language="C#" Debug="true" Service="QuiznetOnline.Web.UI.WebServices.LogService" 
Factory="System.ServiceModel.Activation.WebServiceHostFactory" 
</code></pre>

and now you can compile &amp; run your application successfully.

blocks|key|722089|text|我在使用Channel+Factory时遇到了类似的问题。这实际上是由于在终结点中指定了错误的协定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|722090|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|$]]

I was facing the similar issue when using the Channel Factory. it was actually due to wrong Contract specified in the endpoint.

I have a problem with a WCF service.
I have a console application and I need to consume the service without using app.config, so I had to set the endpoint, etc. by code.
I do have a service reference to the svc, but I can't use the app.config.
Here's my code:

<pre><code>BasicHttpBinding binding = new BasicHttpBinding();

EndpointAddress address = new EndpointAddress("http://localhost:8731/WcfServicio/MiServicio");

MiServicioClient svc = new MiServicioClient(binding, address);
object ob = svc.PaisesObtener();
</code></pre>

At the last line when I do <code>svc.PaisesObtener()</code> I get the error:

<pre class="lang-none prettyprint-override"><code>Content Type text/xml; charset=utf-8 was not supported by service
http://localhost:8731/WcfServicio/MiServicio. The client and service bindings may be mismatched.
</code></pre>

Content Type text/xml; charset=utf-8 was not supported by service

我有一个WCF服务的问题。我有一个控制台应用程序，并且我需要在不使用app.config的情况下使用服务，所以我必须通过代码设置端点等。我确实有一个对svc的服务引用，但我不能使用app.config。下面是我的代码：BasicHttpBinding binding = new BasicHttpBinding();E...

问内容类型text/xml；服务不支持字符集=utf-8
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问内容类型text/xml；服务不支持字符集=utf-8EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问内容类型text/xml；服务不支持字符集=utf-8
EN