.NET 4.0 Web服务和IPv6

我在IIS 7.0中部署了一个Web服务。 如果我使用IPv4绑定访问该Web服务，它就会工作，并且我可以看到WSDL。但是，使用IPv6绑定访问它会返回System.UriFormatException:无效URI:无法解析主机名

[UriFormatException: Invalid URI: The hostname could not be parsed.]
   System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) +7955439
   System.Web.Services.Protocols.DocumentationServerType..ctor(Type type, String uri) +75
   System.Web.Services.Protocols.DocumentationServerProtocol.Initialize() +322
   System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) +160

[InvalidOperationException: Unable to handle request.]
   System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) +800924
   System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) +302

[InvalidOperationException: Failed to handle request.]
   System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) +731240
   System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath) +308
   System.Web.Script.Services.ScriptHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String pathTranslated) +89
   System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +608
   System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +193
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +371

如果我访问一个普通的ASP页面，它就会工作

有什么建议吗

---

谢谢

尝试将.Net Framework升级到4.6

我们面临同样的问题，我们可以使用“IPv6 url”访问web服务目录级别，但在访问.asmx时引发了异常

http://[fe11:：b111:327b:28ef:ee9e]/WebServicePath//Works

http://[fe11:：b111:327b:28ef:ee9e]/webservicecepath/MyService.asmx//引发异常

在将.net framework 4.5.1升级到4.6RC后，此问题现已得到修复