<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<compilation debug="true" />
</system.web>
<!-- When deploying the service library project, the content of the config file must be added to the host's
app.config file. System.Configuration does not support config files for libraries. -->
<system.serviceModel>
<services>
<service name="TestSvc.TestSvc">
<endpoint address="" bindingConfiguration="ITestSvc" binding="basicHttpBinding" contract="TestSvc.ITestSvc">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
<host>
<baseAddresses>
<add baseAddress="http://localhost:8732/Design_Time_Addresses/TestSvc/Service1/" />
</baseAddresses>
</host>
</service>
</services>
<bindings>
<basicHttpBinding>
<binding transferMode="Streamed" name="ITestSvc" maxReceivedMessageSize="2000000000" maxBufferPoolSize="2000000000" maxBufferSize="2000000000" messageEncoding="Mtom" openTimeout="10:00:00" sendTimeout="10:00:00" receiveTimeout="10:00:00">
<readerQuotas maxArrayLength="2000000000" maxBytesPerRead="2000000000" maxStringContentLength="2000000000"/>
</binding>
</basicHttpBinding>
</bindings>
<behaviors>
<serviceBehaviors>
<behavior>
<!-- To avoid disclosing metadata information,
set the value below to false and remove the metadata endpoint above before deployment -->
<serviceMetadata httpGetEnabled="True"/>
<!-- To receive exception details in faults for debugging purposes,
set the value below to true. Set to false before deployment
to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment>
<baseAddressPrefixFilters>
<add prefix="http://www.mysite.com/testwcf/"/>
</baseAddressPrefixFilters>
</serviceHostingEnvironment>
</system.serviceModel>
</configuration>
I mean...the service operations just fine until I add the message encoding to mtom on both sides. I haven't had this issue with adding mtom encoding before...is there something else I'm missing?
Microsoft kills AI-powered history search feature in Edge by Usama Jawad
In June 2025, Microsoft began rolling out AI-powered history search functionality with Edge 138. The idea was simple: allow customers to use natural language phrases and synonyms to find their desired history items rather than matching keywords exactly. Although the company had already rolled out this capability in a phased manner, it has now decided to cancel it.
In an update on its Microsoft 365 Roadmap, Microsoft has announced that it has decided not to move forward with AI-powered history search. The company has not detailed the exact reasoning behind this move, but it has apologized to customers for the inconvenience.
The move is rather interesting as it seemingly could have improved user productivity. Edge users wouldn't have to worry about typos or exact keywords, and just focus on what they were trying to locate in their browser history. Microsoft had also assured users that an on-device AI model would be leveraged for this functionality, and no data would be sent to the cloud. IT admins also had the ability to control its availability through the EdgeHistoryAISearchEnabled policy.
When the feature began rolling out last year, many of our readers called it creepy, noting that they couldn't trust Microsoft to keep their data on their device. Others also questioned its usefulness, saying that it's simply a way for Microsoft to insert more AI bloat into its products.
Although the Redmond tech giant had stated that it will be more mindful about surfacing Copilot features in Windows 11 apps, we later discussed how this is mostly a rebranding exercise rather than an actual axing of AI functionalities. Indeed, a Microsoft executive later emphasized how they want to reshape Windows for the agentic AI era. That said, it does seem like at least AI-powered Edge history search isn't a part of that vision.
Not likely, of course, that we will see routine citizenship checks as they only involve compliance with existing federal voting laws already on the books for decades. This seems a non-issue entirely. Only fools would have the government rush headlong into an AI program few can understand or predict, or even debug...
Question
sathenzar
Ive been toying around with MTOM on other example projects that have worked just fine. I have another example project that calls the service just fine. As soon as I add mtom as the message encoding to both the service and the client I get Content Type multipart/related; type="application/xop+xml";start="<http://tempuri.org/0>";boundary="uuid:cb781f20-b41b-429a-8e2d-de6accd8fbb5+id=1";start-info="text/xml" was not supported by service http://www.mysite.co...cf/TestSvc.svc. The client and service bindings may be mismatched.
Service config:
client config
I mean...the service operations just fine until I add the message encoding to mtom on both sides. I haven't had this issue with adding mtom encoding before...is there something else I'm missing?
Link to comment
https://www.neowin.net/forum/topic/1075995-cwcf-mtom-causes-the-service-call-to-fail/Share on other sites
3 answers to this question
Recommended Posts