<behaviors>
<serviceBehaviors>
<!--注:name=随意命名,但要与service的behaviorConfiguration值对应-->
<behavior name="AAAAA">
<serviceMetadata httpGetEnabled="true" />
<serviceDeBUG includeExceptionDetailinFaults="false" />
<dataContractSerializer maxItemsInObjectGraph="2147483647"/>
</behavior>
</serviceBehaviors>
</behaviors>
<services>
<!--注1:此处的name值不能随便修改,命名格式为:完全命名空间+类名 -->
<!--注2:此处的behaviorConfiguration值要与behavior的name值对应-->
<service name="SLfileUpload.Web.fileService" behaviorConfiguration="AAAAA" >
<!--注1:此处的contract值不能随便修改,命名格式为:完全命名空间+接口名 -->
<!--注2:此处的bindingConfiguration值要与binding中的name值对应-->
<endpoint contract="SLfileUpload.Web.IfileService" binding="basichttpBinding" bindingConfiguration="BBBBB" address="" >
</endpoint>
<endpoint address="mex" binding="mexhttpBinding" contract="IMetadataExchange" />
</service>
</services>
<bindings>
<basichttpBinding>
<!--name=随意命名,但要与service的bindingConfiguration值对应 -->
<binding name="BBBBB" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">
<readerQuotas maxStringContentLength="2147483647" maxArrayLength="2147483647"/>
<security mode="None"></security>
</binding>
</basichttpBinding>
</bindings>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
</system.serviceModel> 2,Silverlight端 <bindings> <basichttpBinding> <binding name="BasichttpBinding_IfileService" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"> <security mode="None" /> </binding> </basichttpBinding> </bindings> 转自:http://www.cnblogs.com/gavinyao/archive/2012/04/17/2454495.HTML 总结
以上是内存溢出为你收集整理的Silverlight在调用wcf时传输数据过大返回Not Found的解决办法全部内容,希望文章能够帮你解决Silverlight在调用wcf时传输数据过大返回Not Found的解决办法所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)