Silverlight轮询双工配置错误
我的 web.config 文件中的 system.serviceModel 下有以下内容：
<extensions>
<bindingExtensions>
<add name="pollingDuplex" type="System.ServiceModel.Configuration.PollingDuplexHttpBindingCollectionElement, System.ServiceModel.PollingDuplex, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</bindingExtensions>
</extensions>
当我尝试在浏览器中访问服务时收到的是错误消息：
解析器错误消息：类型的扩展 'System.ServiceModel.Configuration.PollingDuplexElement， 系统.ServiceModel.PollingDuplex, 版本=4.0.0.0，文化=中立， 公钥令牌=31bf3856ad364e35' 已经出现在扩展中 收藏。扩展类型必须是 独一无二。
所以看来 PollingDuplexElement 已经在扩展集合中注册了。我只是不知道在哪里，或者以什么名字。
我尝试查看 machine.config 文件，但没有找到任何对轮询双工程序集的引用。我的 web.config 文件中也没有对该程序集的其他引用，并且 Google 也没有提供太大帮助。
任何想法将不胜感激:)
I have the following in my web.config file under system.serviceModel:
<extensions>
<bindingExtensions>
<add name="pollingDuplex" type="System.ServiceModel.Configuration.PollingDuplexHttpBindingCollectionElement, System.ServiceModel.PollingDuplex, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</bindingExtensions>
</extensions>
And what I get when I try to access a service in the browser is the error message:
Parser Error Message: An extension of type
'System.ServiceModel.Configuration.PollingDuplexElement,
System.ServiceModel.PollingDuplex,
Version=4.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35'
already appears in extension
collection. Extension types must be
unique.
So it seems the PollingDuplexElement has already been registered in the extension collection. I just can't figure out where, or under what name.
I've tried looking through the machine.config file, not finding any references to the polling duplex assembly. There is also no other reference to the assembly in my web.config file, and Google has not been of much help.
Any ideas would be much appreciated :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我的 IIS 根目录中有一个旧的 web.config 文件，它也添加了扩展名。删除了，现在可以正常使用了。
There was an old web.config file located on my IIS root that also added the extension. Deleted it, and now it works fine.