可能WebService路径不对,数据编码格式不对,如果还不是,把程序贴出来.
解决方案 »
- wince下用C#如何显示JPG,GIF等图片
- 合并后的FLV文件鼠标拖动进度条正常播放,但直接播放有异常。。。
- .net的程序集签名,如何使用?????
- c# timer 控件
- TableAdapter 的UpdateCommand存储过程该怎么写?
- 十万火急,再次提问!SQL联接多表的问题!
- 问个简单的问题,SQL查询,读取数据库里的第二条记录在页面上显示
- webForm!关于登陆和退出一个程序的问题!!!请教!!!
- 怎样捕获 嵌入的IE浏览器控件中弹出身份认证窗口,然后用代码输入指定的用户名和密码登陆?
- 关于DATAGRID一个功能实现的问题
- 怎么求得这个数字之和?
- c#入门书籍 c#站点 贴就有分
或着用代理类
Q Why did .vsdisco documents stop working with the final release of the Microsoft® .NET Framework? A In the beta releases of the .NET Framework, the .vsdisco HTTP handler was automatically enabled, but for the final release the .NET team decided to disable it by default. If you open machine.config (from a path that looks something like c:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\CONFIG\machine.config) and search for .vsdisco under /configuration/system.web/httpHandler, you'll see that the .vsdisco HTTP handler entry is commented out:<!-- machine.config -->
•••
<httpHandlers>
<!--
<add verb="*" path="*.vsdisco"
type="System.Web.Services.Discovery.DiscoveryRequestHandler,
System.Web.Services, Version=1.0.3300.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
-->
<add verb="*" path="*.aspx"
type="System.Web.UI.PageHandlerFactory"/>
•••If you open the Microsoft Internet Information Services (IIS) management console and inspect the default application mappings that are configured by the .NET Framework installation, you'll see that the application mapping for .vsdisco documents is still in place (see Figure 1). This means that by default HTTP GET requests for .vsdisco documents are going to be handled by the static file handler (System.Web.StaticFileHandler), which returns the contents of the .vsdisco document, not the results of the dynamic discovery algorithm that searches for Web Service descriptions within the given vroot.
Figure 1 Application MappingsTo enable machine-wide dynamic discovery support, uncomment the .vsdisco httpHandler entry. If dynamic discovery should remain disabled at the machine level, you can turn it on at the vroot level by adding .vsdisco to the web.config file of the particular vroot, as shown here:<!-- web.config -->
<configuration>
<system.web>
<httpHandlers>
<add verb="*" path="*.vsdisco"
type="System.Web.Services.Discovery.DiscoveryRequestHandler,
System.Web.Services, Version=1.0.3300.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
</httpHandlers>
</system.web>
</configuration>You can just add this web.config file to any vroot that needs dynamic discovery (assuming the vroot hasn't removed the .vsdisco application mapping).
It's reasonable to have the .vsdisco handler disabled by default since it allows clients to retrieve some of the details of a machine's Web Service configuration. Turning it on forces developers to make a decision before allowing clients to retrieve such information.