异步等待针对4.0的部署要求 [英] Async Await targeting 4.0 deployment requirements

问题描述

微软已经更新了异步/计谋目标为.NET 4.0，现在建议使用<一个href="http://blogs.msdn.com/b/bclteam/archive/2012/10/22/using-async-await-without-net-framework-4-5.aspx"相对=nofollow> Microsoft.Bcl.Async 库可在的NuGet 。

在发行说明，它指出.NET 4 KB 2468871 是必需的。

1. 是KB2468871构建要求或部署要求？
2. 使得它需要什么方面KB2468871的？

解决方案

从 HTTP引用： //support.microsoft.com/kb/2468871/en-us

  

功能5更改为支持便携式库。这些变化   包括API更新和粘合剂的修改。此更新启用   CLR成功地结合到便携式存储库的单个DLL   可以在.NET Framework 4，Silverlight的，在Xbox，或在运行   微软手机。此更新增加了公众的Silverlight API到.NET   在相同的位置的框架4。该API签名将保持   在整个平台一致。所有的修改是100％的   兼容，并且不会破坏任何现有的code。

事实证明，如果没有这个KB安装Microsoft.Bcl崩溃（它试图绑定到Silverlight的 System.Core程序库，是不是系统上）

Microsoft has updated the async/await targeting for .net 4.0 and now suggests using the Microsoft.Bcl.Async library available on nuget.

In the release notes, it states that .net 4 with KB 2468871 is required.

1. Is KB2468871 a build requirement or a deployment requirement?
2. What aspect of KB2468871 makes it required?

解决方案

Quoting from http://support.microsoft.com/kb/2468871/en-us

Feature 5 Changes to the support portable libraries. These changes include API updates and binder modifications. This update enables the CLR to bind successfully to portable libraries so that a single DLL can run on the .NET Framework 4, on Silverlight, on Xbox, or on the Windows Phone. This update adds public Silverlight APIs to the .NET Framework 4 in the same location. The API signatures will remain consistent across the platform. All modifications are 100 percent compatible and will not break any existing code.

It turns out that without this kb installed Microsoft.Bcl crashes (it tries to bind to silverlight System.Core library which is not on the system)

这篇关于异步等待针对4.0的部署要求的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！