问题描述
我们开始在几个月前收到下面的错误，它看起来像MAC OS 6。有人可以帮助我阐明了跌破发行一些轻？我们有很多在我们的网站部分呈现，但它似乎asp.net认为iPad的6_0_1无法处理。
We started to receive the below error a few months ago, it looks like mac os 6. Can someone help me shed some light on the below issue? We have a lot of partial rendering on our site, but it seems asp.net thinks ipad 6_0_1 cannot handle it.
事件目标：ctl00 $ ScriptManager1
Event Target: ctl00$ScriptManager1
例外：System.Web.HttpUnhandledException（0X80004005）：类型System.Web.HttpUnhandledException引发的异常。 ---> System.InvalidOperationException：页面正在执行异步回发，但ScriptManager.SupportsPartialRendering属性设置为false。确保财产在异步回发设置为true。在System.Web.UI.ScriptManager.OnPageInitComplete（对象发件人，EventArgs e）上System.EventHandler.Invoke（对象发件人，EventArgs e）上System.Web.UI.Page.ProcessRequestMain（布尔includeStagesBeforeAsyncPoint，布尔includeStagesAfterAsyncPoint）的系统。 Web.UI.Page.HandleError（例外五）在System.Web.UI.Page.ProcessRequestMain（布尔includeStagesBeforeAsyncPoint，布尔includeStagesAfterAsyncPoint）在System.Web.UI.Page.ProcessRequest（布尔includeStagesBeforeAsyncPoint，布尔includeStagesAfterAsyncPoint）在System.Web程序。 UI.Page.ProcessRequest（）在System.Web.UI.Page.ProcessRequest（HttpContext的背景下），在System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()在System.Web.HttpApplication.ExecuteStep（IExecutionStep步骤，布尔和放大器; completedSynchronously）
Exception: System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: The page is performing an async postback but the ScriptManager.SupportsPartialRendering property is set to false. Ensure that the property is set to true during an async postback. at System.Web.UI.ScriptManager.OnPageInitComplete(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
用户代理：Mozilla的/ 5.0（iPad版，CPU的操作系统6_0_1喜欢Mac OS X）为AppleWebKit / 536.26（KHTML，像壁虎）版本/ 6.0移动/ 10A523 Safari浏览器/ 8536.25
User Agent: Mozilla/5.0 (iPad; CPU OS 6_0_1 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A523 Safari/8536.25
推荐答案
由于我一直在这一整天，我想我会发布什么，我终于实现了，除了我的上述评论。它看起来像重要的浏览器功能是
Since I've been working on this all day I thought I'd post what I ended up doing in addition to my above comments. It looks like the important browser capabilities are
ecmascriptversion=1.5
w3cdomversion=1.0
supportscallback=true
如果其中任何一项都没有present的Sys.WebForms对象还没有生成。
If any one of these aren't present the Sys.WebForms object won't get created.
我结束了创建在App_Browsers文件文件夹中的自定义浏览器文件：
I ended up creating a custom browser file in the App_Browsers folder:
<browsers>
<gateway id="IPad" parentID="Safari">
<identification>
<userAgent match="iPad" />
</identification>
<capabilities>
<capability name="ecmascriptversion" value="1.5" />
<capability name="w3cdomversion" value="1.0" />
<capability name="supportscallback" value="true" />
<capability name="supportsxmlhttp" value="true" />
</capabilities>
</gateway>
</browsers>
然而
最后一个功能是没有必要的创建Sys.WebForms的对象，我不太清楚阿贾克斯是如何工作的没有的一个XMLHtt prequest对象。
The last capability is not necessary for creation of the Sys.WebForms object however I'm not quite sure how Ajax is supposed to work without an XMLHttpRequest object.
这篇关于iPad的6_0_1 ScriptManager.SupportsPartialRendering ASP.Net的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！