什么是铁轨堆叠？(What is rails stack?)

 作为一般规则，只要异步操作的区域是自包含且独立的 ，您应该使用ConfigureAwait(false) - 实际上这样做对于减少开销和瓶颈非常重要。 库代码通常不需要知道调用上下文。 但是， 使用代码（例如winforms，MVC等）通常需要返回到适当的上下文 ，因此不应使用ConfigureAwait(false) 。 例如： 
 
async Task SomeUXCodeAsync() {
    var data = await GetSomeDataAsync(); // note no ConfigureAwait(false)
    // not shown: use "data"
}
async Task<Foo> GetSomeDataAsync() {
    using(var conn = CreateConnection()) {
        await conn.OpenAsync().ConfigureAwait(false);
        ...
        int result = await cmd.ExecuteNonQueryAsync().ConfigureAwait(false);
        ...
        return ...
    }
}
 
 上面的场景非常典型和常见， 但它比这更复杂 - 例如，评论中的TransactionScope示例涉及数据相关代码可能需要了解调用上下文的示例。 但细微差别：只要消费代码记住不要忽略呼叫上下文，你通常会回到正确的位置。 对不起，这有点模糊和毛茸茸，但是：遗憾的是，这种情况通常适用于呼叫环境。 

As a general rule, as long as a region of async operations are self contained and independent, you should be fine using ConfigureAwait(false) - and indeed doing so can be important to reduce overheads and bottlenecks. The library code usually doesn't need to know about the call-context. However, consuming code (such as winforms, MVC, etc) usually needs to get back to the appropriate context, so should not use ConfigureAwait(false). For example:
 
async Task SomeUXCodeAsync() {
    var data = await GetSomeDataAsync(); // note no ConfigureAwait(false)
    // not shown: use "data"
}
async Task<Foo> GetSomeDataAsync() {
    using(var conn = CreateConnection()) {
        await conn.OpenAsync().ConfigureAwait(false);
        ...
        int result = await cmd.ExecuteNonQueryAsync().ConfigureAwait(false);
        ...
        return ...
    }
}
 
The above scenario is pretty typical and common, but it is more complex than that - the TransactionScope example from the comments touches on examples where the data related code might need to know about the call context, for example. But nuance aside: as long as the consuming code remembers not to ignore the call context, you'll usually end up back at the right place. Sorry this is a little vague and woolly, but : sadly that's kinda the case generally for the call-context.