[AttributeUsage(AttributeTargets.Method | AttributeTargets.Class)]
public sealed class TransactionAttribute : ActionFilterAttribute
{
    private ITransaction transaction;

    public TransactionAttribute()
    {
        this.Order = 0;
    }

    public ISession Session
    {
        get;
        set;
    }

    public override void OnActionExecuted(
        ActionExecutedContext filterContext)
    {
        if (this.Session != null && this.transaction != null)
        {
            try
            {
                if (this.transaction.IsActive)
                {
                    if (filterContext.Exception == null)
                    {
                        this.transaction.Commit();
                    }
                    else
                    {
                        this.transaction.Rollback();
                    }
                }
            }
            finally
            {
                this.transaction.Dispose();
                this.transaction = null;
            }
        }
    }

    public override void OnActionExecuting(
        ActionExecutingContext filterContext)
    {
        if (this.Session != null)
        {
            this.transaction = this.Session.BeginTransaction();
        }
    }
}

太棒了. Seems to be a common pattern.

在ASP.NET MVC 3中,我在“Breaking Changes”(强调我的)下看到了这个小小的模糊：

In prevIoUs versions of ASP.NET MVC,action filters were created per request except in a few cases. This behavior was never a guaranteed behavior but merely an implementation detail and the contract for filters was to consider them stateless. In ASP.NET MVC 3,filters are cached more aggressively. Therefore,any custom action filters which improperly store instance state might be broken.

哎呀.

>这是否意味着如果我升级到MVC 3,我就会被冲洗？
>如果每个请求不再实例化操作过滤器,我们如何将请求范围的依赖项添加到我们的操作过滤器中？

感谢您的任何见解.