- android - RelativeLayout 背景可绘制重叠内容
- android - 如何链接 cpufeatures lib 以获取 native android 库?
- java - OnItemClickListener 不起作用,但 OnLongItemClickListener 在自定义 ListView 中起作用
- java - Android 文件转字符串
图表 1:将异步(不是 async
!)网络调用包装到 Task
中的一些代码
public static Task<byte[]> GetAsync(IConnection connection, uint id)
{
ReadDataJob jobRDO = new ReadDataJob();
//No overload of FromAsync takes 4 extra parameters, so we have to wrap
// Begin in a Func so that it looks like it takes no parameters except
// callback and state
Func<AsyncCallback, object, IAsyncResult> wrapped = (callback, state) =>
jobRDO.Begin(connection, 0, 0, id, callback, state);
return Task<byte[]>.Factory.FromAsync(wrapped, ar =>
{
ErrorCode errorCode;
UInt32 sError;
UInt32 attribute;
byte[] data = new byte[10];
jobRDO.End(out errorCode, out sError, out attribute, out data);
if(error != ErrorCode.NO_ERROR) throw new Exception(error.ToString());
return data;
}, jobRDO);
}
安装 .Net 4.5(不指向 VS,也不重新编译)会停止此工作。永远不会调用回调。
知道是什么原因造成的吗?否则,我可以做些什么来尝试进一步缩小问题的根本原因或解决问题?
最佳答案
重新编辑:我与Stephen Toub交换了几封电子邮件。 .下面我尝试将我的原始答案和他的答案合并成一个连贯的整体。
tl;dr 要解决此问题,请强制 CompleteSynchronously
始终返回 false(注意非 lector)。
发布这个问题后,我立即点击了 related question , 并结束于 "Application Compatibility in the .NET Framework 4.5" ,其中有关于 FromAsync
的说法:
Change: The
IAsyncResult
implementation must complete synchronously and itsCompletedSynchronously
property must return true for the resulting task to complete.Impact: The resulting task will not complete if an
IAsyncResult
implementation does not complete synchronous execution but itsCompletedSynchronously
property returns True.
具有讽刺意味的是,(或令人气愤的是)CompletedSynchronously
的页面状态:
Notes to Implementers: Most implementers of the
IAsyncResult
interface will not use this property and should return false.
The table at http://msdn.microsoft.com/en-us/library/hh367887%28v=VS.110%29.aspx#core, and specifically the description of the “Change”, is wrong (...).
There was a change in .NET 4.5 to
FromAsync
, but it wasn’t that allIAsyncResult.CompletedSynchronously
implementations must return true: that wouldn’t make any sense. The change was thatFromAsync
actually looks at theIAsyncResult’s CompletedSynchronously
now (it didn’t look at it at all in .NET 4), and thus it expects it to be accurate. As such, if you had a buggyIAsyncResult
implementation,FromAsync
might still have worked in .NET 4, whereas with .NET 4.5, it’s less likely to work with a buggy implementation.Specifically, it’s ok if
IAsyncResult.CompletedSynchronously
returnsfalse
. However, if it returnstrue
, theIAsyncResult
must have in fact completed synchronously. IfCompletedSynchronously
returnstrue
but theIAsyncResult
has not completed, you have a bug that needs to be fixed, and it’s likely that theTask
returned fromFromAsync
will not complete correctly.The change was made for performance reasons.
这是他非常有用的分析,我将其完整包含在内,因为它可能对 IAsyncResult
的其他实现者有用:
The problem appears to be that the library you’re using has a very faulty implementation of
IAsyncResult
; in particular, it’s implementingCompletedSynchronously
incorrectly. Here’s their implementation:public bool CompletedSynchronously
{
get { return _isCompleted; }
}
public bool IsCompleted
{
get { return _isCompleted; }
}Their
_isCompleted
field indicates whether the asynchronous operation has completed, which is fine, and it’s fine to return this fromIsCompleted
, since that property is meant to indicate whether the operation completed or not. ButCompletedSynchronously
can’t just return that same field:CompletedSynchronously
needs to return whether the operation completed synchronously, i.e. whether it completed during the call toBeginXx
, and it must always return the same value for a givenIAsyncResult
instance.Consider the standard pattern for how
IAsyncResult.CompletedSynchronously
is used. Its purpose is to allow the caller ofBeginXx
to continue doing the follow-on work, rather than having the callback due the work. This is particularly important for avoiding stack dives (imagine a long sequence of asynchronous operations that all actually completed synchronously: if the callbacks handled all of the work, then each callback would initiate the next operation, whose callback would initiate the next operation, but because they were completing synchronously, their callbacks would also be invoked synchronously as part of theBeginXx
methods, so each call would get deeper and deeper on the stack, until it potentially overflowed):IAsyncResult ar = BeginXx(…, delegate(IAsyncResult iar) =>
{
if (iar.CompletedSynchronously) return;
… // do the completion work, like calling EndXx and using its result
}, …);
if (ar.CompletedSynchronously)
{
… // do the completion work, like calling EndXx and using its result
}Note that both the caller and the callback use the same
CompletedSynchronously
property to determine which of them runs the callback. As such,CompletedSynchronously
must always return the same value for this particular instance. If it doesn’t, erroneous behavior can easily result. For example, their implementation hasCompletedSynchronously
returning the equivalent ofIsCompleted
. So imagine the following sequence of events:
BeginXx
is called and initiates the async operationBeginXx
returns to its caller, which checksCompletedSynchronously
, which is false, because the operation hasn’t completed yet.- Now the operation completes and the callback is invoked. The callback sees that
CompletedSynchronously
is true, and so doesn’t do any of the subsequent work, because it assumes the caller did it.- And now no one’s run or will run the callback.
In short, the library has a bug. If you changed
CompletedSynchronously
to return true, you masked this problem, but you likely caused another: if the caller (in your case,FromAsync
) thinks that the operation has already completed, it’ll proceed to immediately call theEndXx
method, which will block until the async operation has completed, so you’ve turned your asynchronous operations into synchronous ones. Have you tried just always returning false fromCompletedSynchronously
instead of always returning true?
关于c# - .Net 4.5 杀死了我的 TPL,现在呢?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/14889514/
创建使用.NET框架的asp.net页面时,访问该页面的客户端是否需要在其计算机上安装.NET框架? IE。用户访问www.fakesite.com/default.aspx,如果他们没有安装框架,他
我阅读了很多不同的博客和 StackOverflow 问题,试图找到我的问题的答案,但最后我找不到任何东西,所以我想自己问这个问题。 我正在构建一个应用程序,其中有一个长时间运行的工作线程,它执行一些
已锁定。这个问题及其答案是locked因为这个问题是题外话,但却具有历史意义。目前不接受新的答案或互动。 我一直想知道为什么微软为这样一个伟大的平台选择了一个如此奇怪的、对搜索引擎不友好的名称。他们就
.Net Framework .Net .NET Standard的区别 1、.NET Framework 在未来.NET Framework或许成为过去时,目前还是有很多地方在使用的。这一套
如果有选择的话,您会走哪条路? ASP.NET Webforms + ASP.NET AJAX 或 ASP.NET MVC + JavaScript Framework of your Choice
我有一个 Web 服务,它通过专用连接通过 https 使用第三方 Web 服务,我应用了 ServicePointManager.ServerCertificateValidationCallbac
为什么我应该选择ASP.NET Web Application (.NET Framework)而不是ASP.NET Core Web Application (.NET Framework)? 我在
我在网络上没有找到任何关于包含 .NET Standard、.NET Core 和 .NET Framework 项目的 .NET 解决方案的公认命名约定。 就我而言,我们在 .NET 框架项目中有以
.NET Compact 是 .NET 的完美子集吗? 假设我考虑了屏幕大小和其他限制并避免了 .NET Compact 不支持的类和方法,或者 .NET Compact 是一个不同且不兼容的 GUI
我已经阅读了所有我能找到的关于 connectionManagement 中的 maxconnection 设置的文章:即 http://support.microsoft.com/kb/821268
我现在正在使用asp.net mvc,想知道使用内置的Json或 Json.Net哪个是更好的选择,但我不确定一个人是否比另一个人有优势。 另外,如果我确实选择沿用Json.Net的路线,那么我应该选
在 Visual Studio 中,您至少可以创建三种不同类型的类库: 类库(.NET Framework) 类库(.NET 标准) 类库(.NET Core) 虽然第一个是我们多年来一直使用的,但我
.NET 和 ASP.NET 之间有什么区别?它们有什么关系? 最佳答案 ASP.Net 基于 .Net 框架构建,提供有关 Web 开发的附加功能。 你可以去看看wikipedia article
在安装更高版本(3.0)之前,我需要安装.net框架1.1和2.0吗?或者单独安装 3.0 框架就足够了,并为在早期框架版本上编写的软件提供支持?谢谢 ,丽然 最佳答案 不,您不必安装以前的框架。 我
我正在开发一个项目,人们可以“更新”类别,例如更改类别的名称。我收到以下消息 This is called after clicking update 按钮 with the SQL statemen
.NET 类 System.Net.CookieContainer 线程安全吗? --更新:交 key 答复-- 是否有任何方法可以确保异步请求期间修改的变量(即 HttpWebRequest.Coo
我正在使用 JScript.NET 在我编写的 C# WinForms 应用程序中编写脚本。它工作得很好,但我只是尝试在脚本中放置一些异常处理,但我无法弄清楚如何判断我的 C# 代码抛出了哪种类型的异
我需要你的帮助, 比如我有一个小数类型的变量,我想这样取整。 例如 3.0 = 3 3.1 = 4 3.2 = 4 3.3 = 4 3.4 = 4 3.5 = 4 3.6 = 4 3.7 = 4 3.
我使用过这样的代码:http://msdn.microsoft.com/en-us/library/dw70f090.aspx在 ASP.NET 中工作之前访问数据库(2-3 年前)。我没有意识到我正
自 ConfigurationManager .NET Standard 中不存在,检索正在执行的程序集的应用程序设置的最佳方法是什么,无论是 web.config或 appSettings.{env
我是一名优秀的程序员,十分优秀!