博客园_PetterLiu

Asp.net MVC中的ViewData与ViewBag

2012-01-21T07:48:00Z

在Asp.net MVC 3 web应用程序中，我们会用到ViewData与ViewBag，对比一下：

ViewData	ViewBag
它是Key/Value字典集合	它是dynamic类型对像
从Asp.net MVC 1 就有了	ASP.NET MVC3 才有
基于Asp.net 3.5 framework	基于Asp.net 4.0与.net framework
ViewData比ViewBag快	ViewBag比ViewData慢
在ViewPage中查询数据时需要转换合适的类型	在ViewPage中查询数据时不需要类型转换
有一些类型转换代码	可读性更好

在Controller中使用ViewData:

public ActionResult UsingViewData()
{
    
    ViewData["Title"] = " Using ViewData";
    ViewData["ProjectName"] = "My Test Project";
    ViewData["ProjectDescription"] = "This is Test Project to demo Viewdata and viewbag details";
    ViewData["StartDate"] = new DateTime(2011, 1, 1);
    ViewData["TotalPrice"] = 1000;
    ViewData["TotalDays"] = 100;
    Dictionary<string, string> stackholder = new Dictionary<string, string>();
    stackholder.Add("Client","Mr.  Client");
    stackholder.Add("Manager","Mr. Joy");
    stackholder.Add("Team Leader","Mr.Toy");
    stackholder.Add("Sr. developer", "Mr.dojoy");
    stackholder.Add("developer", "Mr. nodoy");
    ViewData["stackholder"] = stackholder;

    List<string> modules = new List<string>();
    modules.Add("Admin module");
    modules.Add("ShoppingCart module");
    modules.Add("CMS module");
    ViewData["modules"] = modules;
    return View();
}

对应UsingViewData View的cshtml:

<h1>@ViewData["Title"]</h1>
 <div>
   <div>
    <h2>Project Name : @ViewData["ProjectName"]</h2>
   </div>
   <div>
     ProjectDescription :   
     <p>"@ViewData["ProjectDescription"]".</p>
   </div>
   <div>
      Stack Holder :
      <br />

      <ul id="stakholder">
      @foreach ( var stakerholder in ViewData["stackholder"] as Dictionary<string, string> )
      {          
    <li>
        @stakerholder.Key &nbsp; : @stakerholder.Value
    </li>
      }
     </ul>
   </div>
   <div>
     Project Details:<br />
     <div>
       module List  :
       <ul id="modulelist">
      @foreach ( var module in ViewData["modules"] as List<string> )
      {          
    <li>
        @module
    </li>
      }
     </ul>
        
     </div>
     Project StartDate : @ViewData["StartDate"]  <br />
     Project TotalPrice: @ViewData["TotalPrice"] <br />
     Project TotaDays  : @ViewData["TotalDays"] 
   </div>
 </div>

然后是ViewBag:

public ActionResult UsingViewBag()
{

    ViewBag.Title = " Using ViewBag";
    ViewBag.ProjectName = "My Test Project";
    ViewBag.ProjectDescription = "This is Test Project to demo Viewdata and viewbag details";
    ViewBag.StartDate = new DateTime(2011, 1, 1);
    ViewBag.TotalPrice = 1000;
    ViewBag.TotalDays = 100;
    Dictionary<string, string> stackholder = new Dictionary<string, string>();
    stackholder.Add("Client", "Mr.  Client");
    stackholder.Add("Manager", "Mr. Joy");
    stackholder.Add("Team Leader", "Mr.Toy");
    stackholder.Add("Sr. developer", "Mr.dojoy");
    stackholder.Add("developer", "Mr. nodoy");
    ViewBag.stackholder = stackholder;

    List<string> modules = new List<string>();
    modules.Add("Admin module");
    modules.Add("ShoppingCart module");
    modules.Add("CMS module");
    ViewBag.modules = modules;
    return View();
}

对应View UsingViewBag 的cshtml的ViewBag:

<h1>@ViewBag.Title</h1>
 <div>
   <div>
    <h2>Project Name : @ViewBag.ProjectName</h2>
   </div>
   <div>
     ProjectDescription :   
     <p>"@ViewBag.ProjectDescription.</p>
   </div>
   <div>
      Stack Holder :
      <br />

      <ul id="stakholder">
      @foreach ( var stakerholder in ViewBag.stackholder )
      {          
    <li>
        @stakerholder.Key &nbsp; : @stakerholder.Value
    </li>
      }
     </ul>
   </div>
   <div>
     Project Details:<br />
     <div>
       module List  :
       <ul id="modulelist">
      @foreach ( var module in ViewBag.modules )
      {          
    <li>
        @module
    </li>
      }
     </ul>
        
     </div>
     Project StartDate : @ViewBag.StartDate.ToString("dd-MMM-yyyy") <br />
     Project TotalPrice: @ViewBag.TotalPrice  ₹  <br />
     Project TotaDays  : @ViewBag.TotalDays 
   </div>
 </div>

后面是在Controller中使用ViewBag:

public ActionResult UsingViewBagInControlAndViewDataInView()
{

    ViewBag.Title = " Using ViewBag In Control And ViewData In View";
    ViewBag.ProjectName = "My Test Project";
    ViewBag.ProjectDescription = "This is Test Project to demo Viewdata and viewbag details";
    ViewBag.StartDate = new DateTime(2011, 1, 1);
    ViewBag.TotalPrice = 1000;
    ViewBag.TotalDays = 100;
    Dictionary<string, string> stackholder = new Dictionary<string, string>();
    stackholder.Add("Client", "Mr.  Client");
    stackholder.Add("Manager", "Mr. Joy");
    stackholder.Add("Team Leader", "Mr.Toy");
    stackholder.Add("Sr. developer", "Mr.dojoy");
    stackholder.Add("developer", "Mr. nodoy");
    ViewBag.stackholder = stackholder;

    List<string> modules = new List<string>();
    modules.Add("Admin module");
    modules.Add("ShoppingCart module");
    modules.Add("CMS module");
    ViewBag.modules = modules;
    return View();
}

在UsingViewBagInControlAndViewDataInView.cshtml中使用ViewData来取值：

<h1>@ViewData["Title"]</h1>
 <div>
   <div>
    <h2>Project Name : @ViewData["ProjectName"]</h2>
   </div>
   <div>
     ProjectDescription :   
     <p>"@ViewData["ProjectDescription"]".</p>
   </div>
   <div>
      Stack Holder :
      <br />

      <ul id="stakholder">
      @foreach ( var stakerholder in ViewData["stackholder"] as Dictionary<string, string> )
      {          
    <li>
        @stakerholder.Key &nbsp; : @stakerholder.Value
    </li>
      }
     </ul>
   </div>
   <div>
     Project Details:<br />
     <div>
       module List  :
       <ul id="modulelist">
      @foreach ( var module in ViewData["modules"] as List<string> )
      {          
    <li>
        @module
    </li>
      }
     </ul>
        
     </div>
     Project StartDate : @ViewData["StartDate"]  <br />
     Project TotalPrice: @ViewData["TotalPrice"] <br />
     Project TotaDays  : @ViewData["TotalDays"] 
   </div>
 </div>

反过来是这样的:

public ActionResult UsingViewDataInControlAndViewBagInView()
{
    ViewData["Title"] = " Using ViewData In Control And ViewBag In View";
    ViewData["ProjectName"] = "My Test Project";
    ViewData["ProjectDescription"] = "This is Test Project to demo Viewdata and viewbag details";
    ViewData["StartDate"] = new DateTime(2011, 1, 1);
    ViewData["TotalPrice"] = 1000;
    ViewData["TotalDays"] = 100;
    Dictionary<string, string> stackholder = new Dictionary<string, string>();
    stackholder.Add("Client", "Mr.  Client");
    stackholder.Add("Manager", "Mr. Joy");
    stackholder.Add("Team Leader", "Mr.Toy");
    stackholder.Add("Sr. developer", "Mr.dojoy");
    stackholder.Add("developer", "Mr. nodoy");
    ViewData["stackholder"] = stackholder;

    List<string> modules = new List<string>();
    modules.Add("Admin module");
    modules.Add("ShoppingCart module");
    modules.Add("CMS module");
    ViewData["modules"] = modules;
    return View();
}

在UsingViewDataInControlAndViewBagInView.cshtml 的View中使用ViewBag来取值:

<h1>@ViewBag.Title</h1>
 <div>
   <div>
    <h2>Project Name : @ViewBag.ProjectName</h2>
   </div>
   <div>
     ProjectDescription :   
     <p>"@ViewBag.ProjectDescription.</p>
   </div>
   <div>
      Stack Holder :
      <br />

      <ul id="stakholder">
      @foreach ( var stakerholder in ViewBag.stackholder )
      {          
    <li>
        @stakerholder.Key &nbsp; : @stakerholder.Value
    </li>
      }
     </ul>
   </div>
   <div>
     Project Details:<br />
     <div>
       module List  :
       <ul id="modulelist">
      @foreach ( var module in ViewBag.modules )
      {          
    <li>
        @module
    </li>
      }
     </ul>
        
     </div>
     Project StartDate : @ViewBag.StartDate.ToString("dd-MMM-yyyy") <br />
     Project TotalPrice: @ViewBag.TotalPrice  ₹  <br />
     Project TotaDays  : @ViewBag.TotalDays 
   </div>
 </div>

这样对比看上去会比较清楚一些。在源代码中的ViewBag是这样的属性:

public dynamic ViewBag {
    get {
        if (_dynamicViewData == null) {
            _dynamicViewData = new DynamicViewDataDictionary(() => ViewData);
        }
        return _dynamicViewData;
    }
}

ViewData是：

public ViewDataDictionary ViewData {
    get {
        if (_viewData == null) {
            SetViewData(new ViewDataDictionary());
        }
        return _viewData;
    }
    set {
        SetViewData(value);
    }
}

具体细节在这儿不深入了，这里只是抛砖引玉。希望对您Asp.net MVC开发有帮助。

作者：Petter Liu
出处：http://www.cnblogs.com/wintersun/
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。
该文章也同时发布在我的独立博客中-Petter Liu Blog。

本文链接

Asp.net MVC中使用Razor Generator实现View的单元测试

2012-01-21T02:41:00Z

Asp.net MVC 3 应用程序中，单元测试对项目的质量意义重大。除了对Model，Controller进行单元测试，有时还需要对View也进行。对View进行测试目前并不容易做，大多数情况下可能做的是BlackBox测试。现在可以使用Razor Generator简化对Razor View单元测试。你可以从这里安装 VS2010的扩展。

然后在VIEW上右键属性，对Custom Tool 使用Razor Generator，如下图，它就生成一个对应名称的Class, 文件与View在同一位置。

然后我们看这个Class是这样的:

[System.CodeDom.Compiler.GeneratedCodeAttribute("RazorGenerator", "1.3.0.0")]
    [System.Web.WebPages.PageVirtualPathAttribute("~/Views/Home/TestViewInOutTime.cshtml")]
    public class TestViewInOutTime : System.Web.Mvc.WebViewPage<dynamic>
    {
        public TestViewInOutTime()
        {
        }
        public override void Execute()
        {

            
            #line 1 "..\..\Views\Home\TestViewInOutTime.cshtml"
  
    Layout = null;


            
            #line default
            #line hidden
WriteLiteral("\r\n<!DOCTYPE html>\r\n\r\n<html>\r\n<head>\r\n    <title>TestViewInOutTime</title>\r\n</head" +
">\r\n<body>\r\n    <div>\r\n        <h1 id=\"titleOne\">This is your life</h1>\r\n    </di" +
"v>\r\n</body>\r\n</html>\r\n");


        }
    }

这个View的内容是:

@{
    Layout = null;
}

<!DOCTYPE html>

<html>
<head>
    <title>TestViewInOutTime</title>
</head>
<body>
    <div>
        <h1 id="titleOne">This is your life</h1>
    </div>
</body>
</html>

好的，接下来在你的单元测试项目中使用NuGet安装RazorGenerator.Testing, 它有下面的依赖组件同是安装:

HtmlAgilityPack

Moq

ReflectionMagic

接着我们就可以写这样的单元测试代码。

[TestMethod]
public void TestGetGivenIdInnerHtmlFromViews()
{
    //arrange
    var views = new TestViewInOutTime();

    //act
    HtmlDocument doc = views.RenderAsHtml();
    HtmlNode node = doc.GetElementbyId("titleOne");

    //assert
    Assert.IsNotNull(node);
    Assert.AreEqual("This is your life", node.InnerHtml.Trim());
}

上面的代码您可能看到把当前View Render以后是一个HtmlDocument，这是HtmlAgilityPack中的类。HtmlAgilityPack是一个解析HTML的类库。

然后我们找到titleOne的结点比较的它的InnerHtml。那么对PartialView同样也可以：

Tel.cshtml内容是这样的:
021-77677878

代码是这样的:

[TestMethod]
public void TestPartialView()
{
    //arrange
    var views = new Tel();

    //act
    HtmlDocument doc = views.RenderAsHtml();

    //assert
    Assert.IsNotNull(doc);
    Assert.AreEqual("021-77677878", doc.DocumentNode.InnerText);
}

对Views的UnitTest本来就是棘手的事儿，因为View是在运行时编译的。但 Razor Generator 直接生成View类以方便我们测试它。那什么样产景下我们需要对View进行单元测试呢？有时我们没有必要比较整个输出的Html, 只需要比较是关键的某一段Html即可。

希望对您开发有帮助。

本文链接

使用Moles框架实现HttpWebRequest与HttpWebResponse的单元测试

2012-01-07T03:15:00Z

有时程序使用HttpWebRequest与HttpWebResponse实现HTTP的访问，但我们想测试它们不太容易实现。现在我们可以使用Moles框架来实现对它的单元测试。如果您还不了解Moles，可以先到官方网站看这个文档。下面我们来看片段代码:

[TestMethod]
[HostType("Moles")]
[Description("Testing with moles assemblies")]
public void Get_KnownUrl_ReturnsExpectedValue()
{
    var mockedWebResponse = new MHttpWebResponse();
    MHttpWebRequest.AllInstances.GetResponse = (x) =>
    {
        return mockedWebResponse;
    };

    var googleUri = new Uri("http://www.google.com");
    mockedWebResponse.StatusCodeGet = () => { return HttpStatusCode.OK; };
    mockedWebResponse.ResponseUriGet = () => { return googleUri; };
    mockedWebResponse.ContentTypeGet = () => { return "testHttpResponse"; };

    string mockedResponseStr = @"<html> \r\n" +
                         "  <head></head> \r\n" +
                         "  <body> \r\n" +
                         "     <h1>Hello World</h1> \r\n" +
                         "  </body> \r\n" +
                         "</html>";

    mockedWebResponse.ContentLengthGet = () => { return mockedResponseStr.Length; };

    using (var memoryStream = new MemoryStream())
    {
        using (var sw = new StreamWriter(memoryStream))
        {
            sw.Write(mockedResponseStr);
            sw.Flush();

            memoryStream.Seek(0, SeekOrigin.Begin);
            mockedWebResponse.GetResponseStream = () => memoryStream;


            //act
            var request = WebRequest.Create("http://www.google.com");
            var response = (HttpWebResponse)request.GetResponse();


            // Assert
            string htmlContent = null;
            using (var streamReader = new StreamReader(response.GetResponseStream()))
            {
                htmlContent = streamReader.ReadToEnd();
            }

            Assert.AreEqual(HttpStatusCode.OK, response.StatusCode);
            Assert.AreEqual(mockedResponseStr.Length, response.ContentLength);
            Assert.AreEqual(mockedResponseStr, htmlContent);
            Assert.AreEqual(googleUri, response.ResponseUri);

        }
    }
}

上面的基于MsTest的代码引用Moles生成的System.Moles.dll，HttpWebRequest与HttpWebResponse是在System.dll里的所以生成它。一开始对一些属性与方法的Mock操作，引用的是那些生成的MolesAssembiles，看字面意思可以了解代码的意图。接着模拟请求Google网站，返回我们遇先设置好返回的HtmlString，最后在验证中验证Stream,HttpStatusCode和Length是否一致。当然您也可以测试其它属性成方法。注意最后请求的类是真实的类，可以演示我们把它们写在一起了。实际中可能是某个真实环境的API之类的方法。

希望对您开发有帮助。

您可以感兴趣的文章:

使用Moles对静态方法做UnitTest

本文链接

.net中用Action等委托向外传递参数

2011-12-27T10:16:00Z

一般我们可以使用ref,out达到向外传递参数目的。 Action<T>是一个特殊的委托，除了常规应用。我们还可以用它来实现简单地向外传递参数。直接看下面的UnitTest代码:

   1: [TestMethod]

   2: public void PassOutParametersUsingDelegate()

   3: {

   4:     int i = 0;

   5:     string messgae = string.Empty;

   6:     int? addedNumber = 1;

7:

   8:     //It is pass parameter by Action<T1,T2>

   9:     Foo1((a, b) =>

  10:     {

  11:         i = a;

  12:         messgae = b;

  13:     });

14:

  15:     //It is pass parameter by Func<T1,T2,TResult>

  16:     Foo2((a, b) =>

  17:     {

  18:         i = a;

  19:         messgae = b;

  20:         return addedNumber;

  21:     });

22:

  23:     Foo2((a, b) =>

  24:     {

  25:         return a+100;

  26:     });

27:

  28:     Assert.AreEqual("i=15,message=fifteen", string.Format("i={0},message={1}", i, messgae));

29:

30:

  31: }

32:

  33: private void Foo1(Action<int, string> action)

  34: {

  35:     int number = 15;

  36:     string msg = "fifteen";

37:

  38:     action(number, msg);

  39: }

40:

  41: private void Foo2(Func<int, string, int?> func)

  42: {

  43:     int number = 15;

  44:     string msg = "fifteen";

45:

  46:     int? tempInt = func(number, msg);

  47: }

上面的代码我们演示使用Action<T>, 有注意到我们把a,b两个值传递给方法外面的变量。同样的，我们用Func<TResult>可以实现。为什么会有这样的代码产生呢？源于这样的场景，有一个方法只有一个输入参数，返回void 。我们为了不改变原来这个方法参数签名，增加新的子方法，使用Action<T>向外传递参数。然后再用原方法Wrap新的子方法。
关于Action<T>还有很多精彩的运用，Builder模式与Fluent接口。
希望对您开发有帮助。

本文链接

Asp.net MVC3扩展之Ajax异常处理特性

2011-12-18T07:33:00Z

在Asp.net MVC 3 Web开发中，我们会大量使用各种ajax请求，针对ajax请求如何结何server端如何做异常处理呢？我们可以扩展ActionFilterAttribute，实现一个Ajax异常处理特性。假设您是使用JQuery脚本开发来实现Ajax，看代码:

   1: #region AjaxExceptionAttribute

   2: /// <summary>

   3: /// Ajax Exception Handle Attribute

   4: /// </summary>

   5: [AttributeUsage(AttributeTargets.Method | AttributeTargets.Class)]

   6: public class AjaxExceptionAttribute : ActionFilterAttribute, IExceptionFilter

   7: {

   8:     /// <summary>

   9:     /// Called when an exception occurs.

  10:     /// </summary>

  11:     /// <param name="filterContext">The filter context.</param>

  12:     public void OnException(ExceptionContext filterContext)

  13:     {

  14:         if (!filterContext.HttpContext.Request.IsAjaxRequest())

  15:             return;

16:

  17:         filterContext.Result = AjaxError(filterContext.Exception.Message, filterContext);

18:

  19:         //Let the system know that the exception has been handled

  20:         filterContext.ExceptionHandled = true;

  21:     }

22:

  23:     /// <summary>

  24:     /// Ajaxes the error.

  25:     /// </summary>

  26:     /// <param name="message">The message.</param>

  27:     /// <param name="filterContext">The filter context.</param>

  28:     /// <returns>JsonResult</returns>

  29:     protected JsonResult AjaxError(string message, ExceptionContext filterContext)

  30:     {

  31:         //If message is null or empty, then fill with generic message

  32:         if (String.IsNullOrEmpty(message))

  33:             message = "Something went wrong while processing your request. Please refresh the page and try again.";

34:

  35:         //Set the response status code to 500

  36:         filterContext.HttpContext.Response.StatusCode = (int)HttpStatusCode.InternalServerError;

37:

  38:         //Needed for IIS7.0

  39:         filterContext.HttpContext.Response.TrySkipIisCustomErrors = true;

40:

  41:         return new JsonResult

  42:         {

  43:             //can extend more properties

  44:             Data = new AjaxExceptionModel () { ErrorMessage = message },

  45:             ContentEncoding = System.Text.Encoding.UTF8,

  46:             JsonRequestBehavior = JsonRequestBehavior.DenyGet

  47:         };

  48:     }

  49: }

  50: #endregion

51:

  52: /// <summary>

  53: /// AjaxExceptionModel

  54: /// </summary>

  55: public class AjaxExceptionModel

  56: {

  57:     /// <summary>

  58:     /// Gets or sets the error message.

  59:     /// </summary>

  60:     /// <value>

  61:     /// The error message.

  62:     /// </value>

  63:     public string ErrorMessage { get; set; }

  64: }

代码已有相关注释。AjaxExceptionModel您完全可以自定义更多的属性，然后在Controller或Action上增加这个特性。像下面这个HomeController有一个YouKnow的Action，这里为演示我们故意throw一个Exception:

[AjaxException]

public class HomeController : BaseController

[HttpPost]

public ActionResult YouKnow(FormCollection fc)

throw new ArgumentNullException("YouKnow method: fc should not be null");

接下来看HTML与JQuery:

<h4 id="lblMethodError">

</h4>

<br />

<h4 id="lblMethodSuccess">

</h4>

<br />

<h2>ajax post</h2>

<input type="button" value="Post method" id="inputajax1" />

<br />

<input type="button" value="Ajax method with error section" id="inputajax2" />

<p>

<input type="button" value="Post method for undefined Url" id="inputajax3" />

</p>

<p>

<input type="button" value="Post method to get Json Result" id="inputajax4" />

</p>

<br />

<h3 id="errorh3info">

</h3>

JQuery的全局AjaxError配置，可参考官方

$("#errorh3info").ajaxError(function (event, request, settings) {

$(this).append("<li>settings.url:" + settings.url + "</li>");

$(this).append("<li>request.status:" + request.status + "</li>");

$(this).append("<li>request.statusText:" + request.statusText + "</li>");

//request.responseText

if (request.responseText != "") {

var jsonValue = jQuery.parseJSON(request.responseText);

$(this).append("<li>ErrorMessage:" + jsonValue.ErrorMessage + "</li>");

});

给button增加一个Post请求：

$('#inputajax1').click(function () {

$.post('/Home/YouKnow/'

, { id: 1 }

, function (data) {

$('div#right-box.data').html(data);

});

});

这时View上将显示, 我们将看到ErrorMessage是JSON对象的属性：

settings.url:/Home/YouKnow/

request.status:500

request.statusText:error

ErrorMessage:Value cannot be null. Parameter name: YouKnow method: fc should not be null

当然也可以这样:

//ajax post when throw an exception at server side

$('#inputajax2').click(function () {

$.ajax({

type: "POST",

url: "/Home/YouKnow2",

data: "fail=1",

dataType: "json",

error: function (xhr, status, error) {

// Show the error

$('#lblMethodError').append(xhr.responseText);

$('#lblMethodError').show();

},

success: function (data, textSuccess) {

// show the success message

$('#lblMethodSuccess').show();

}

});

});

这时View上，比上面那个请求多显示一条信息, 这是因为我们这里定义了自己error处理callback.

{"ErrorMessage":"Value cannot be null.\r\nParameter name: YouKnow method: fc should not be null"}

当我们请求一个不存在Action时呢:

//request undefined url

$('#inputajax3').click(function () {

$.post('/Home/YouKnow2233/'

, { id: 1 }

, function (data) {

$('div#right-box.data').html(data);

});

});

页面上将显示：

settings.url:/Home/YouKnow2233/

request.status:0

request.statusText:error

最后我们来看这个ActionFilter的单元测试，这里使用Moq类库:

[TestMethod]

public void Test_Native_AjaxExceptionAttribute()

//arrange

var header = new System.Collections.Specialized.NameValueCollection();

header.Add("X-Requested-With", "XMLHttpRequest");

var mockRequest = new Mock<HttpRequestBase>();

mockRequest.SetupGet(http => http.Headers).Returns(header);

var mockResponse = new Mock<HttpResponseBase>();

var mockHttpContext = new Mock<HttpContextBase>();

mockHttpContext.SetupGet(c => c.Request).Returns(mockRequest.Object);

mockHttpContext.SetupGet(c => c.Response).Returns(mockResponse.Object);

var context = mockHttpContext.Object;

var exceptonContextMock = new Mock<ExceptionContext>();

exceptonContextMock.SetupGet(ac => ac.HttpContext).Returns(context);

string errorStr="error";

exceptonContextMock.SetupGet(ec => ec.Exception).Returns(new AggregateException(errorStr));

//act

var ajaxAttribute = new AjaxExceptionAttribute();

var exceptionContext = exceptonContextMock.Object;

ajaxAttribute.OnException(exceptionContext);

//verify

mockRequest.VerifyAll();

mockResponse.VerifyAll();

mockHttpContext.VerifyAll();

exceptonContextMock.VerifyAll();

//assert

var jsonResult = exceptionContext.Result as JsonResult;

Assert.IsNotNull(jsonResult.Data);

Assert.IsTrue(exceptionContext.HttpContext.Request.IsAjaxRequest());

Assert.AreEqual((jsonResult.Data as AjaxExceptionModel).ErrorMessage, errorStr);

Assert.AreEqual(JsonRequestBehavior.DenyGet, jsonResult.JsonRequestBehavior);

Assert.AreEqual(typeof(AggregateException), exceptionContext.Exception.GetType());

上面的UnitTest我们Mock HttpContext,HttpRequest,HttpResponse来实现对ActionFilter的测试。
希望您Web开发有帮助。

本文链接

Asp.net MVC 3 防止 Cross-Site Request Forgery (CSRF)原理及扩展

2011-12-09T12:23:00Z

Cross-Site Request Forgery (CSRF) 是我们Web站点中常见的安全隐患。下面我们在Asp.net MVC3 来演示一下。例如我们有一个HomeContoller中一个Submit Action，我们标记了Http Post

[HttpPost]

public ActionResult Submit(FormCollection fc)

{

if (!string.IsNullOrEmpty(fc["Title"]))

{

ViewBag.Message = "Submit success!";

return View("Index");

}

return View("Error");

}

在View 使用Razor 简单提交是这样：

@using (Html.BeginForm("Submit", "Home"))

{

@Html.TextBox("Title","text");

<input type="submit" value="Submit" id="sb1" />

}

点击这个Button我们就提交表单了，接下来我们轻易使用Fiddler来伪造这个Http Post请求:

然后提交，成功了，返回 OK.

POST http://localhost:55181/Home/Submit HTTP/1.1
User-Agent: Fiddler
Host: localhost:55181
Content-Length: 10

Title=text

那在Asp.net MVC 3 Web Application中如何防止呢？在View中使用

@Html.AntiForgeryToken()

这时当Web应用程序运行时，查看生成HTML，你会看到form标签后有一个hidden input标签

<form action="/Home/Submit2" method="post">

<input name="__RequestVerificationToken" type="hidden"

value="WiB+H5TNp6V27ALYB3z/1nkD9BLaZIBbWQOBEllj2R/+MkGZqOjLbIof2MJeEoyUJV2ljujNR4etYV6idzji

G4+JL77P9qmeewc4Erh8LnMBHX6zLas2L67GDhvCom0dpiDZl0cH+PykIC/R+HYzEIUTK/thXuF8OUtLwIfKdly0650U

3I7MD6/cIc5aersJBMZ/p6gv76gc6nvKJDt2w0eMy3tkEfAcnNPTdeWr59Ns+48gsGpZ2GSh6G+Uh7rb" />

<input id="Title" name="Title" type="text" value="text" />

<br /> <input type="submit" value="Submit" id="sb1" />

看源代码是GetHtml方法序列化相应值生成的，

public HtmlString GetHtml(HttpContextBase httpContext, string salt, string domain, string path)

{

Debug.Assert(httpContext != null);

string formValue = GetAntiForgeryTokenAndSetCookie(httpContext, salt, domain, path);

string fieldName = AntiForgeryData.GetAntiForgeryTokenName(null);

TagBuilder builder = new TagBuilder("input");

builder.Attributes["type"] = "hidden";

builder.Attributes["name"] = fieldName;

builder.Attributes["value"] = formValue;

return new HtmlString(builder.ToString(TagRenderMode.SelfClosing));

}

同时还写Cookies

__RequestVerificationToken_Lw__=T37bfAdCkz0o1iXbAvH4v0bdpGQxfZP2PI5aTJgLL/Yhr3128FUY+fvUPApBqz7CGd2uxPiW+lsZ5tvRbeLSetARbHGxPRqiw4LZiPpWrpU9XY8NO4aZzNAdMe+l3q5EMw2iIFB/6UfriWxD7X7n/8P43LJ4tkGgv6BbrGWmKFo= 更多细节，请查询源代码。然后在Action上增加 [ValidateAntiForgeryToken] 就可以了，它是这样工作的:

1: public void Validate(HttpContextBase context, string salt) {

2: Debug.Assert(context != null);

3:

4: string fieldName = AntiForgeryData.GetAntiForgeryTokenName(null);

5: string cookieName = AntiForgeryData.GetAntiForgeryTokenName(context.Request.ApplicationPath);

6:

7: HttpCookie cookie = context.Request.Cookies[cookieName];

8: if (cookie == null || String.IsNullOrEmpty(cookie.Value)) {

9: // error: cookie token is missing

10: throw CreateValidationException();

11: }

12: AntiForgeryData cookieToken = Serializer.Deserialize(cookie.Value);

13:

14: string formValue = context.Request.Form[fieldName];

15: if (String.IsNullOrEmpty(formValue)) {

16: // error: form token is missing

17: throw CreateValidationException();

18: }

19: AntiForgeryData formToken = Serializer.Deserialize(formValue);

20:

21: if (!String.Equals(cookieToken.Value, formToken.Value, StringComparison.Ordinal)) {

22: // error: form token does not match cookie token

23: throw CreateValidationException();

24: }

25:

26: string currentUsername = AntiForgeryData.GetUsername(context.User);

27: if (!String.Equals(formToken.Username, currentUsername, StringComparison.OrdinalIgnoreCase)) {

28: // error: form token is not valid for this user

29: // (don't care about cookie token)

30: throw CreateValidationException();

31: }

32:

33: if (!String.Equals(salt ?? String.Empty, formToken.Salt, StringComparison.Ordinal)) {

34: // error: custom validation failed

35: throw CreateValidationException();

36: }

37: }

从Cookie中获得之前序列化存入的Token，然后反序列化与表单提交的Token进行对比。接着，又对当前请求的用户认证进行确认。最后看有没有设置Salt，有的话再进行比较。其中有一步验证没有通过，则throw异常。
有时的需求是这样的，我们需要使用Session验证用户，那么我们可在上面方法修改增加下面的代码块,意图是对比之前Session值是否与当前认证后Session值相等：

//verify session

if (!String.Equals(formToken.SessionId, AntiForgeryData.GetGUIDString(), StringComparison.Ordinal))

{

throw CreateValidationException();

}

在修改AntiForgeryDataSerializer类，它负责序列化，这里我们增加了SessionId属性:

1: internal class AntiForgeryDataSerializer

2: {

3: [SuppressMessage("Microsoft.Usage", "CA2202:Do not dispose objects multiple times", Justification = "MemoryStream is resilient to double-Dispose")]

4: public virtual AntiForgeryData Deserialize(string serializedToken)

5: {

6: if (String.IsNullOrEmpty(serializedToken))

7: {

8: throw new ArgumentException("Argument_Cannot_Be_Null_Or_Empty", "serializedToken");

9: }

10:

11: try

12: {

13: using (MemoryStream stream = new MemoryStream(Decoder(serializedToken)))

14: using (BinaryReader reader = new BinaryReader(stream))

15: {

16: return new AntiForgeryData

17: {

18: Salt = reader.ReadString(),

19: Value = reader.ReadString(),

20: CreationDate = new DateTime(reader.ReadInt64()),

21: Username = reader.ReadString(),

22: SessionId=reader.ReadString()

23: };

24: }

25: }

26: catch (Exception ex)

27: {

28: throw new System.Web.Mvc.HttpAntiForgeryException("AntiForgeryToken_ValidationFailed", ex);

29: }

30: }

31:

32: [SuppressMessage("Microsoft.Usage", "CA2202:Do not dispose objects multiple times", Justification = "MemoryStream is resilient to double-Dispose")]

33: public virtual string Serialize(AntiForgeryData token)

34: {

35: if (token == null)

36: {

37: throw new ArgumentNullException("token");

38: }

39:

40: using (MemoryStream stream = new MemoryStream())

41: using (BinaryWriter writer = new BinaryWriter(stream))

42: {

43: writer.Write(token.Salt);

44: writer.Write(token.Value);

45: writer.Write(token.CreationDate.Ticks);

46: writer.Write(token.Username);

47: writer.Write(token.SessionId);

48:

49: return Encoder(stream.ToArray());

50: }

51: }

52: }

在View这样使用,并引入Salt，这使得我们安全机制又提升了一点儿。

@using (Html.BeginForm("Submit2", "Home"))

{

@Html.AntiForgeryToken(DebugMvc.Controllers.Config.SALT);

@Html.TextBox("Title","text");

<br />

<input type="submit" value="Submit" id="sb1" />

}

Action的特性上，我们也配置对应的Salt字符串:

[HttpPost]

[ValidateAntiForgeryToken(Salt = Config.SALT)]

public ActionResult Submit2(FormCollection fc)

{

if (!string.IsNullOrEmpty(fc["Title"]))

{

ViewBag.Message = "Submit success!";

return View("Index");

}

return View("Error");

}

配置类:
public class Config

{

public const string SALT = "Why you are here";

}

这个实现一个简单的Session在HttpModule中,

public class MySessionModule:IHttpModule

{

#region IHttpModule Members

public void Dispose(){}

public void Init(HttpApplication context)

{

context.AcquireRequestState += new EventHandler(this.AcquireRequestState);

}

#endregion

protected void AcquireRequestState(object sender, EventArgs e)

{

HttpApplication httpApp = (HttpApplication)sender;

if (httpApp.Context.CurrentHandler is IRequiresSessionState)

{

if (httpApp.Session.IsNewSession)

{

httpApp.Session["GUID"] = Guid.NewGuid();

}

}

}

}

这时我们再使用Fiddler模拟请求POST到这个Action,后得到下面的结果，这个异常信息也是可以修改的:

AntiForgeryToken_ValidationFailed

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Mvc.HttpAntiForgeryException: AntiForgeryToken_ValidationFailed

最后让我们来看单元测试的代码:

1: namespace DebugMvc.Ut

2: {

3: using System;

4: using System.Collections.Generic;

5: using System.Linq;

6: using System.Web;

7: using Microsoft.VisualStudio.TestTools.UnitTesting;

8: using DebugMvc.Controllers;

9: using System.Web.Mvc;

10: using Moq;

11: using System.Collections.Specialized;

12: using Match = System.Text.RegularExpressions.Match;

13: using System.Text.RegularExpressions;

14: using System.Globalization;

15:

16: [TestClass]

17: public class UnitTestForAll

18: {

19: private static string _antiForgeryTokenCookieName = AntiForgeryData.GetAntiForgeryTokenName("/SomeAppPath");

20: private const string _serializedValuePrefix = @"<input name=""__RequestVerificationToken"" type=""hidden"" value=""Creation: ";

21: private const string _someValueSuffix = @", Value: some value, Salt: some other salt, Username: username"" />";

22: private readonly Regex _randomFormValueSuffixRegex = new Regex(@", Value: (?<value>[A-Za-z0-9/\+=]{24}), Salt: some other salt, Username: username"" />$");

23: private readonly Regex _randomCookieValueSuffixRegex = new Regex(@", Value: (?<value>[A-Za-z0-9/\+=]{24}), Salt: ");

24:

25: [TestMethod]

26: public void TestValidateAntiForgeryToken2Attribute()

27: {

28: //arrange

29: var mockHttpContext = new Mock<HttpContextBase>();

30:

31: var context = mockHttpContext.Object;

32: var authorizationContextMock = new Mock<AuthorizationContext>();

33: authorizationContextMock.SetupGet(ac => ac.HttpContext).Returns(context);

34:

35: bool validateCalled = false;

36: Action<HttpContextBase, string> validateMethod = (c, s) =>

37: {

38: Assert.AreSame(context, c);

39: Assert.AreEqual("some salt", s);

40: validateCalled = true;

41: };

42: var attribute = new ValidateAntiForgeryToken2Attribute(validateMethod)

43: {

44: Salt = "some salt"

45: };

46:

47: // Act

48: attribute.OnAuthorization(authorizationContextMock.Object);

49:

50: // Assert

51: Assert.IsTrue(validateCalled);

52: }

53:

54: [TestMethod]

55: public void GetHtml_ReturnsFormFieldAndSetsCookieValueIfDoesNotExist()

56: {

57: // Arrange

58: AntiForgeryWorker worker = new AntiForgeryWorker()

59: {

60: Serializer = new DummyAntiForgeryTokenSerializer()

61: };

62: var context = CreateContext();

63:

64: // Act

65: string formValue = worker.GetHtml(context, "some other salt", null, null).ToHtmlString();

66:

67: // Assert

68: Assert.IsTrue(formValue.StartsWith(_serializedValuePrefix), "Form value prefix did not match.");

69:

70: Match formMatch = _randomFormValueSuffixRegex.Match(formValue);

71: string formTokenValue = formMatch.Groups["value"].Value;

72:

73: HttpCookie cookie = context.Response.Cookies[_antiForgeryTokenCookieName];

74: Assert.IsNotNull(cookie, "Cookie was not set correctly.");

75: Assert.IsTrue(cookie.HttpOnly, "Cookie should have HTTP-only flag set.");

76: Assert.IsTrue(String.IsNullOrEmpty(cookie.Domain), "Domain should not have been set.");

77: Assert.AreEqual("/", cookie.Path, "Path should have remained at '/' by default.");

78:

79: Match cookieMatch = _randomCookieValueSuffixRegex.Match(cookie.Value);

80: string cookieTokenValue = cookieMatch.Groups["value"].Value;

81:

82: Assert.AreEqual(formTokenValue, cookieTokenValue, "Form and cookie token values did not match.");

83: }

84:

85: private static HttpContextBase CreateContext(string cookieValue = null, string formValue = null, string username = "username")

86: {

87: HttpCookieCollection requestCookies = new HttpCookieCollection();

88: if (!String.IsNullOrEmpty(cookieValue))

89: {

90: requestCookies.Set(new HttpCookie(_antiForgeryTokenCookieName, cookieValue));

91: }

92: NameValueCollection formCollection = new NameValueCollection();

93: if (!String.IsNullOrEmpty(formValue))

94: {

95: formCollection.Set(AntiForgeryData.GetAntiForgeryTokenName(null), formValue);

96: }

97:

98: Mock<HttpContextBase> mockContext = new Mock<HttpContextBase>();

99: mockContext.Setup(c => c.Request.ApplicationPath).Returns("/SomeAppPath");

100: mockContext.Setup(c => c.Request.Cookies).Returns(requestCookies);

101: mockContext.Setup(c => c.Request.Form).Returns(formCollection);

102: mockContext.Setup(c => c.Response.Cookies).Returns(new HttpCookieCollection());

103: mockContext.Setup(c => c.User.Identity.IsAuthenticated).Returns(true);

104: mockContext.Setup(c => c.User.Identity.Name).Returns(username);

105:

106: var sessionmock = new Mock<HttpSessionStateBase>();

107: sessionmock.Setup(s => s["GUID"]).Returns(Guid.NewGuid().ToString());

108:

109: mockContext.Setup(c => c.Session).Returns(sessionmock.Object);

110:

111: return mockContext.Object;

112: }

113: }

114:

115: internal class DummyAntiForgeryTokenSerializer : AntiForgeryDataSerializer

116: {

117: public override string Serialize(AntiForgeryData token)

118: {

119: return String.Format(CultureInfo.InvariantCulture, "Creation: {0}, Value: {1}, Salt: {2}, Username: {3}",

120: token.CreationDate, token.Value, token.Salt, token.Username);

121: }

122: public override AntiForgeryData Deserialize(string serializedToken)

123: {

124: if (serializedToken == "invalid")

125: {

126: throw new HttpAntiForgeryException();

127: }

128: string[] parts = serializedToken.Split(':');

129: return new AntiForgeryData()

130: {

131: CreationDate = DateTime.Parse(parts[0], CultureInfo.InvariantCulture),

132: Value = parts[1],

133: Salt = parts[2],

134: Username = parts[3]

135: };

136: }

137: }

138: }

这里只是UnitTest的一部分，使用Moq来实现Mock HttpContext，从而实现对HttpContext的单元测试。

小结： Web站点的安全问题，不可轻视。特别现在Ajax大量应用，做好安全检测很重要。

希望对您Web开发有帮助。

作者：Petter Liu
出处：http://www.cnblogs.com/wintersun/
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。
该文章也同时发布在我的独立博客中-Petter Liu Blog。

本文链接

Asp.net MVC3 RTM的源代调试

2011-12-02T10:50:00Z

       首先，从CodePlex下载源码。解压后编译一下，然后在我们要调试的Solution中开发那下面的项目：

System.Web.Mvc

System.Web.Helpers

System.Web.WebPages

System.Web.Razor

System.Web.WebPages.Razor

       同时也删除原来以上程序集原来的引用。接下来是修改web.config，assemblies节，删除version,culture,PublicKeyToken信息,一个简单方法搜索

, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35

       替换为空，最后效果如下：

<assemblies>

<add assembly="System.Web.Abstractions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

<add assembly="System.Web.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

<add assembly="System.Web.Helpers" />

<add assembly="System.Web.Mvc " />

<add assembly="System.Web.WebPages" />

</assemblies>

       还有View文件夹下的web.config需要修改，也是删除对应此用version,culture,PublicKeyToken信息，结果如下：

<configSections>

<sectionGroup name="system.web.webPages.razor" type="System.Web.WebPages.Razor.Configuration.RazorWebSectionGroup, System.Web.WebPages.Razor ">

<section name="host" type="System.Web.WebPages.Razor.Configuration.HostSection, System.Web.WebPages.Razor " requirePermission="false" />

<section name="pages" type="System.Web.WebPages.Razor.Configuration.RazorPagesSection, System.Web.WebPages.Razor " requirePermission="false" />

</sectionGroup>

</configSections>

       好了，到这儿我们修改两个web.config的某个配置节，删除原来对GAC的引用，而引用我们下来的源代码项目。我们就可以调试到ASP.NET MVC3 RTM 源码中了。
希望对您Web开发有帮助。

作者：Petter Liu
出处：http://www.cnblogs.com/wintersun/
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。
该文章也同时发布在我的独立博客中-Petter Liu Blog。

本文链接

Lazy<T>的应用之类内部字段与C#延迟加载

2011-11-27T14:54:00Z

延迟加载主要应用在以下场景:

数据层 – ADO.NET或Entity Framework等ORM
反射 – 加载assemblies, types, MEF
缓存对象,领域实体

下面以领域实体为例, 在实体中我们经常检查某个属性下字段是否为空引用. 如果是空的话,计算或填充这个字段. 像这样:

1: /// <summary>
2: /// Order
3: /// </summary>
4: public class Order
5: {
6: private Customer _customer;
7: /// <summary>
8: /// Gets the customer.
9: /// </summary>
10: public Customer Customer
11: {
12: get
13: {
14: if (_customer == null)
15: {
16: _customer = new Customer();
17: } return _customer;
18: }
19: }
20: /// <summary>
21: /// Prints the label.
22: /// </summary>
23: /// <returns></returns>
24: public string PrintLabel()
25: {
26: return Customer.CompanyName + "\n" + Customer.Address;
27: }
28: }

如果PrintLabel方法写成这样:

1: public string PrintLabel()
2: {
3: string result = _customer.CompanyName; // probably results in a NullReferenceException
4: return result + "\n" + Customer.Address; // ok to access Customer
5: }

注意上面第4行代码,可能有空引用异常. 下面我们使用Lazy<T>来解决这个问题:

1: /// <summary>
2: /// Order
3: /// </summary>
4: public class Order
5: {
6: /// <summary>
7: /// _customerInitializer
8: /// </summary>
9: private Lazy<Customer> _customerInitializer;
10:
11: /// <summary>
12: /// Initializes a new instance of the <see cref="Order"/> class.
13: /// </summary>
14: public Order()
15: {
16: _customerInitializer = new Lazy<Customer>(() => new Customer(),isThreadSafe:true);
17: }
18:
19: /// <summary>
20: /// Gets the customer.
21: /// </summary>
22: public Customer Customer
23: {
24: get{ return _customerInitializer.Value;}
25: }
26:
27: /// <summary>
28: /// Prints the label.
29: /// </summary>
30: /// <returns></returns>
31: public string PrintLabel()
32: {
33: string result = Customer.CompanyName; // ok to access Customer
34: return result + "\n" + _customerInitializer.Value.Address; // ok to access via .Value
35: }
36: }

上面的代码16行,我们延迟初始化对像实例,并且设置线程安全. Lazy<T>内部是使用Func<T>来实现的,看下面其中构造器的源代码:

1: public Lazy(Func<T> valueFactory, LazyThreadSafetyMode mode)
2: {
3: if (valueFactory == null) throw new ArgumentNullException("valueFactory");
4: this.m_threadSafeObj = Lazy<T>.GetObjectFromMode(mode);
5: this.m_valueFactory = valueFactory;
6: }

有兴趣请自行查看.net framework中的源码. 我们还可以扩展一个LazyNotNull<T>

1: /// <summary>
2: /// LazyNotNull
3: /// </summary>
4: /// <typeparam name="T">Type</typeparam>
5: public class LazyNotNull<T>
6: {
7: private Lazy<T> _lazyValue = null;
8: private Func<T> _valueFactory = null;
9:
10: /// <summary>
11: /// Initializes a new instance of the <see cref="LazyNotNull<T>"/> class.
12: /// </summary>
13: /// <param name="valueFactory">The value factory.</param>
14: public LazyNotNull(Func<T> valueFactory)
15: {
16: _lazyValue = new Lazy<T>(valueFactory);
17: _valueFactory = valueFactory;
18: }
19:
20: /// <summary>
21: /// Gets T value.
22: /// </summary>
23: public T Value
24: {
25: get
26: {
27: var lazyValue = _lazyValue;
28: if (lazyValue.Value != null)
29: {
30: return lazyValue.Value;
31: }
32: _lazyValue = new Lazy<T>(_valueFactory);
33: return default(T);
34: }
35: }
36: }

希望这篇POST对您开发有帮助.
您可能感兴趣的文章:

.net4.0下的Lazy<T>类型简单应用
 .net3.5下使用LINQ递归算法实现简洁代码

作者：Petter Liu
出处：http://www.cnblogs.com/wintersun/
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。
该文章也同时发布在我的独立博客中-Petter Liu Blog。
本文链接

数据访问层的单元测试

2011-11-19T15:05:00Z

数据访问层在分层结构,比较常见. 有时可能是数据访问模块. 假设数据访问层后端是数据库,那我们如何测试他们的呢? 有时实际这种测试是集成测试了.
有时数据库里还有一些逻辑,触发器,约束等. 个人十分不建议把业务逻辑放在数据库里实现. 最常见的数据库表的操作create, read, update和delete(简称CRUD)
, 例如我们需要测试某个Add方法,在这个测试方法完成后, 希望这条测试数据清除掉. 这样做是为了不影响其它的测试方法也访问同一数据库对象.
    首先,我们可以使用.net 2.0中提供的TransactionScope类, 下面的代码基于MsTest的单元测试:

1: [TestClass]
2: public class DbTestBase
3: {
4: private TransactionScope scope;
5:
6: [TestInitialize]
7: public void SetUp()
8: {
9: this.scope = new TransactionScope();
10: }
11:
12: [TestCleanup]
13: public void TearDown()
14: {
15: this.scope.Dispose();
16: }
17: }

上面代码我们看到在标记TestInitialize特性SetUp方法中创建TransactionScope的实例,在TestCleanup特性TearDown方法中调用TransactionScope的Dispose方法. 然后我们继承这个测试基类:

1: [TestClass]
2: public class DateBaseTesting : DbTestBase
3: {
4: /// <summary>
5: /// Test Insert record to database
6: /// </summary>
7: /// <seealso cref="http://www.cnblogs.com/wintersun"/>
8: /// <remarks>Any database modification will be roll back</remarks>
9: [TestMethod]
10: public void TestAddWithEmployeeRepository()
11: {
12: //arrange
13: var employee = this.CreateNewEmployee();
14: var employRepository = RepositoryHelper.GetEmployeeRepository();
15:
16: //act
17: employRepository.Add(employee);
18: employRepository.Save();
19:
20: //assert
21: var employeelist =
22: employRepository.Repository.Find(e => e.EmployeeID == employee.EmployeeID);
23: Assert.IsNotNull(employeelist);
24: CollectionAssert.AreEqual(new List<Employee>() { employee }, employeelist.ToList());
25: }
26:
27:
28: private Employee CreateNewEmployee()
29: {
30: var employee = new Employee
31: {
32: ManagerID = 2,
33: ContactID = 3,
34: Title = "Developer",
35: BirthDate = new DateTime(1965, 1, 1, 0, 0, 0),
36: HireDate = DateTime.Now,
37: Gender = "M",
38: MaritalStatus = "M",
39: ModifiedDate = DateTime.Now,
40: NationalIDNumber = "2",
41: rowguid = new Guid(),
42: CurrentFlag = true,
43: VacationHours = 2,
44: SickLeaveHours = 3,
45: SalariedFlag = false,
46: LoginID = "myworkbase\\peter"
47: };
48: return employee;
49: }
50:
51: }

上面的TestAddWithEmployeeRepository中场景是数据访问层基于EntityFramework的Repository模式, 这里的操作是先是创建实体,然后是提交. 实际中可以是您的任何代码块,ADO.NET或其他的数据访问组件. 当我们执行这个单元测试后,这个TransactionScope将被释放. 之前插入的那条记录将被清除.
      假设你不想用基类, 只是简单在某个方法中, 可以这样做:

1: [TestMethod]
2: public void TestWrapTransactionScope()
3: {
4: WrapTransactionScope(() => TestAddWithEmployeeRepository());
5: }
6:
7: /// <summary>
8: /// Wraps the transaction scope for unit testing
9: /// </summary>
10: /// <param name="action">The action method</param>
11: /// <remarks>author http://www.cnblogs.com/wintersun </remarks>
12: public void WrapTransactionScope(Action action)
13: {
14: using (var scope = new TransactionScope())
15: {
16: action();
17: }
18: }

上面的代码演示了, 我们用Action委托实现另一个方法包装一下目标方法使其在TransactionScope块中.
      我们还可以使用xUnit 类库这实现同样的操作, 这里使用是xUnit 1.8版本. 还有MbUnit,NUnit的[RollBack]特性与这个类似. 如果您还不熟悉怎么使用xUnit请先看这里介绍. 下面的代码使用 xUnit 代码变得更加简洁:

1: /// <summary>
2: /// Database unit testing with xUnit demo
3: /// </summary>
4: /// <remarks>http://wintersun.cnblogs.com </remarks>
5: public class TestDbWithxUnit
6: {
7: [Fact]
8: [AutoRollback]
9: public void Test_Add_One_Enity()
10: {
11: //arrange
12: var employee = this.CreateNewEmployee();
13: var employRepository = RepositoryHelper.GetEmployeeRepository();
14:
15: //act
16: employRepository.Add(employee);
17: employRepository.Save();
18:
19: //assert
20: var employeelist =
21: employRepository.Repository.Find(e => e.EmployeeID == employee.EmployeeID);
22: Assert.NotNull(employeelist);
23: Assert.Equal(new List<Employee> { employee }, employeelist.ToList());
24: }
25: }

上面的代码我们只需在方法上加一个AutoRollback的Attribute就可以了, 注意你先需要引用xunit.extensions.dll
当然,最标准的单元测试我们完全隔离数据库, 数据访问组件在单元测试中不应该访问数据库. 我们使用Mock框架来实现对数据库的隔离, 如下代码演示了我们使用Moq v4.0.20926 和 xUnit 来实现的单元测试:

1: [Fact]
2: public void TestWithMoq()
3: {
4: //arrange
5: var mock = new Mock<IRepository<Employee>>();
6: Employee employee = this.CreateNewEmployee();
7: var list = new List<Employee>() { employee };
8:
9: mock.Setup(ep => ep.Add(It.IsAny<Employee>()))
10: .Callback(()=>Console.WriteLine("Add()"));
11: mock.Setup(ep => ep.Find(It.IsAny<Expression<Func<Employee, bool>>>()))
12: .Returns(list);
13: mock.Setup(ep => ep.Save())
14: .Callback(() => Console.WriteLine("Save()"));
15: var employeeRespository = mock.Object;
16:
17: //act
18: employeeRespository.Add(employee);
19: employeeRespository.Save();
20:
21: //verify method
22: mock.Verify(ep => ep.Add(It.IsAny<Employee>()));
23: mock.Verify(ep => ep.Save());
24:
25: //assert
26: var employeelist =
27: employeeRespository.Find(e => e.EmployeeID == employee.EmployeeID);
28: Assert.NotNull(employeelist);
29: Assert.Equal(new List<Employee> { employee }, employeelist.ToList());
30: }

Employee是实体类, IRepository<T>是一个统一数据访问interface, 实现martinfowler的Repository模式; 上面的代码Mock了其中的Add,Save方法, 在调用后并做了Verify,确认之前Mock的方法有被调用到, 最后的部分才是Assert语句块. 代码很简单.

除了使用Mock框架, 我们还可以使用依赖注入容器来注入一个具体的Fake对象实现对访问数据库的隔离, 我们使用Unity 2.1 来实现:

1: [Fact]
2: public void TestWithDIContainer()
3: {
4: //arrange
5: var employee = this.CreateNewEmployee();
6: var list = new List<Employee>() { employee };
7: var employeeRespository = GetRepositoryInstance("for testing");
8:
9: //act
10: employeeRespository.Add(employee);
11: employeeRespository.Save();
12:
13: //assert
14: var employeelist =
15: employeeRespository.Find(e => e.EmployeeID == employee.EmployeeID);
16: Assert.NotNull(employeelist);
17: Assert.Equal(new List<Employee> { employee }, employeelist.ToList());
18: }
19:
20: private IRepository<Employee> GetRepositoryInstance(string name)
21: {
22: //Initial container
23: var container = new UnityContainer();
24: container.RegisterType<IRepository<Employee>, EFRepository<Employee>>();
25: container.RegisterType<IRepository<Employee>, FakeRepository<Employee>>("for testing");
26: //....
27: return container.Resolve<IRepository<Employee>>(name);
28: }

上面的代码为了演示的简便, 我们实现创建容器注册对象在一个private方法中; 您也可以使用其它IOC/DI的容器. FakeRepository<Employee>是一个实现了IRepository<T>的具体类, 在其内部可以在内存中操作实体,或是其它方式. 具体看您的需求了.

以上所有是我们介绍对数据访问层或数据库进行单元测试的解决方法:

1. 使用TransactionScope类实现测试方法回滚
2. 使用xUnit类库的AutoRollback特性实现自动回滚
3. 使用Moq框架来实现隔离数据库的访问
4. 使用Unity容器注入Fake对象来实现隔离数据库的访问

希望这篇文章对您做开发与单元测试有帮助.
您可以感兴趣的文章:

使用Moq来Mock多个接口
 MsTest中实现类似NUnit中Assert.Throws
Repository Factory介绍
 Unity在Xml配制文件使用泛型

作者：Petter Liu
出处：http://www.cnblogs.com/wintersun/
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。
该文章也同时发布在我的独立博客中-Petter Liu Blog。
本文链接

Asp.net Web Applicatoin实现自定义HttpModule拦截异常处理

2011-11-12T08:55:00Z

Asp.net的NamePipe机制给我们提供了很多扩展性. 使用HttpModule我们可能实现的有:

强制站点范围的Cookie策略

集中化监控与日志

编写设置与删除HTTP头

控制response输出,如删除多余空白字符

Session管理

认证与受权

下面我们来看如何实现自定义异常处理:

1: public class ErrorModule:IHttpModule
2: {
3: #region IHttpModule Members
4:
5: /// <summary>
6: /// Disposes of the resources (other than memory) used by the module that implements <see cref="T:System.Web.IHttpModule"/>.
7: /// </summary>
8: public void Dispose()
9: {
10: //do nothing
11: }
12:
13: /// <summary>
14: /// Initializes a module and prepares it to handle requests.
15: /// </summary>
16: /// <param name="context">An <see cref="T:System.Web.HttpApplication"/> that provides access to the methods, properties, and events common to all application objects within an ASP.NET application</param>
17: public void Init(HttpApplication context)
18: {
19: context.Error += new EventHandler(customcontext_Error);
20: }
21:
22: private void customcontext_Error(object sender, EventArgs e)
23: {
24: HttpContext ctx = HttpContext.Current;
25: HttpResponse response = ctx.Response;
26: HttpRequest request = ctx.Request;
27:
28: Exception exception = ctx.Server.GetLastError();
29:
30: var sboutput = new StringBuilder();
31: sboutput.Append("Querystring:<p/>");
32: //Get out the query string
33: int count = request.QueryString.Count;
34: for (int i = 0; i < count; i++)
35: {
36: sboutput.AppendFormat("<br/> {0}:-- {1} ", request.QueryString.Keys[i], request.QueryString[i]);
37: }
38: //Get out the form collection info
39: sboutput.Append("<p>-------------------------<p/>Form:<p/>");
40: count = request.Form.Count;
41: for (int i = 0; i < count; i++)
42: {
43: sboutput.AppendFormat("<br/> {0}:-- {1} -- <br/>", request.Form.Keys[i], request.Form[i]);
44: }
45: sboutput.Append("<p>-------------------------<p/>ErrorInfo:<p/>");
46: sboutput.AppendFormat(@"Your request could not processed. Please press the back button on your browser and try again.<br/>
47: If the problem persists, please contact technical support<p/>
48: Information below is for technical support:<p/>
49: <p/>URL:{0}<p/>Stacktrace:---<br/>{1}<p/>InnerException:<br/>{2}"
50: , ctx.Request.Url, exception.InnerException.StackTrace, exception.InnerException);
51:
52: response.Write(sboutput.ToString());
53:
54: // To let the page finish running we clear the error
55: ctx.Server.ClearError();
56: }
57:
58: #endregion
59:
60: }

上面的代码实现了IHttpModule接口, 实现基于HttpApplication.Error事件, 接着我们自定义输出了一些信息,包括Form,QueryString. 最后把原来的Error信息清除了,这样你看到以前那个黄页了. 这个自定义的Module可以用于调试Web应用程序使用.

Web.config中配置:

<httpModules>
<add name="ErrorLoggingModule" type="MyWeb.ErrorModule"/>
</httpModules>

实际开发中,我们可以做的事儿很多,对这些信息记日志,发邮件. 如下, 我们演示使用Enterprise Library 做异常处理并日志记录,部分代码如下:

1: /// <summary>
2: /// Handles the Error event of the EntLibLogging control.
3: /// </summary>
4: /// <param name="sender">The source of the event.</param>
5: /// <param name="e">The <see cref="System.EventArgs"/> instance containing the event data.</param>
6: /// <remarks>author Petter Liu http://wintersun.cnblogs.com</remarks>
7: private void EntLibLogging_Error(object sender, EventArgs e)
8: {
9: var builder = new ConfigurationSourceBuilder();
10:
11: builder.ConfigureInstrumentation()
12: .ForApplicationInstance("MyApp")
13: .EnableLogging()
14: .EnablePerformanceCounters();
15:
16: //a single exception handling policy named MyPolicy for exceptions of type ArgumentNullException.
17: //The handler for this exception policy will log the exception to the General category (defined in the Logging Application Block configuration)
18: //as a warning with event ID 9000, wrap the ArgumentNullException with an InvalidOperationException, set the new exception message to MyMessage, and then re-throw the exception.
19: builder.ConfigureExceptionHandling()
20: .GivenPolicyWithName("MyPolicy")
21: .ForExceptionType<ArgumentNullException>()
22: .LogToCategory("Exception")
23: .WithSeverity(System.Diagnostics.TraceEventType.Warning)
24: .UsingEventId(9000)
25: .WrapWith<InvalidOperationException>()
26: .UsingMessage("MyMessage")
27: .ThenNotifyRethrow();
28:
29: //logging application
30: builder.ConfigureLogging()
31: .WithOptions
32: .DoNotRevertImpersonation()
33: .LogToCategoryNamed("Exception")
34: .SendTo.FlatFile("Exception Logging File")
35: .FormatWith(new FormatterBuilder()
36: .TextFormatterNamed("Text Formatter")
37: . UsingTemplate("Timestamp: {timestamp}{newline}Message: {message}{newline}Category: {category}{newline}"))
38: .ToFile("d:\\logs\\ExceptionsLog.log")
39: .SendTo.RollingFile("Rolling Log files")
40: .RollAfterSize(1024)
41: .ToFile("d:\\logs\\Rollinglog.log")
42: .LogToCategoryNamed("General")
43: .WithOptions.SetAsDefaultCategory()
44: .SendTo.SharedListenerNamed("Exception Logging File");
45:
46: var configSource = new DictionaryConfigurationSource();
47: builder.UpdateConfigurationWithReplace(configSource);
48: EnterpriseLibraryContainer.Current = EnterpriseLibraryContainer.CreateDefaultContainer(configSource);
49:
50: var ex = HttpContext.Current.Server.GetLastError();
51: var em = EnterpriseLibraryContainer.Current.GetInstance<ExceptionManager>();
52: em.HandleException(ex.InnerException, "MyPolicy");
53: }

注意上面的代码, 为了运行代码您需要引用以下程序集

Enterprise Library Share Common Library
Microsoft.Practices.ServiceLocation
Logging Application Block
Exception Handling Application Block
Exception Handling Logging Provider

这里我们使用Fluent API配置, 因此没有配置XML文件. 所以不需要Web.Config中配置任何信息. 代码中有注释. 为了测试我们使用一个PAGE故意Throw 一个ArgumentNullException. 通过Server.GetLastError()获取Exception, 这时由名为MyPolicy策略处理异常. 对于ArgumentNullException把它们记录日志到名为Exception分类中,这个日志文件位于d:\\logs\\
ExceptionLog.log.实际开发你完全按照你的需要来自定义策略.

然后这个日志文件中写出的内容是这样的:
---------------------------------------- Timestamp: 2011-11-12 5:57:08 Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aa An exception of type 'System.ArgumentNullException' occurred and was caught. ---------------------------------------------------------------------------- 11/12/2011 13:57:08 Type : System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : Value cannot be null. Parameter name: Demo error Source : MyWeb Help link : ParamName : Demo error Data : System.Collections.ListDictionaryInternal TargetSite : Void Page_Load(System.Object, System.EventArgs) Stack Trace : at MyWeb.About.Page_Load(Object sender, EventArgs e) in H:\My Project\DotNet40\TDD2010\WebHost\MyWeb\About.aspx.cs:line 14 at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Additional Info: MachineName : USER TimeStamp : 2011-11-12 5:57:08 FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 AppDomainName : 3e5cb21e-3-129655510216406250 ThreadIdentity : WindowsIdentity : USER\Petter Category: Exception

由于我们日志模块我们配置还需要写Rollinglog.log文件,内容如下:
---------------------------------------- Exception Warning: 9000 : Timestamp: 2011-11-12 5:57:08 Message: HandlingInstanceID: a99d005d-5f8d-4613-9522-2d60efb089aa An exception of type 'System.ArgumentNullException' occurred and was caught. ---------------------------------------------------------------------------- 11/12/2011 13:57:08 Type : System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : Value cannot be null. Parameter name: Demo error Source : MyWeb Help link : ParamName : Demo error Data : System.Collections.ListDictionaryInternal TargetSite : Void Page_Load(System.Object, System.EventArgs) Stack Trace : at MyWeb.About.Page_Load(Object sender, EventArgs e) in H:\My Project\DotNet40\TDD2010\WebHost\MyWeb\About.aspx.cs:line 14 at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Additional Info: MachineName : USER TimeStamp : 2011-11-12 5:57:08 FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 AppDomainName : 3e5cb21e-3-129655510216406250 ThreadIdentity : WindowsIdentity : USER\Petter Category: Exception Priority: 0 EventId: 9000 Severity: Warning Title:Enterprise Library Exception Handling Machine: USER App Domain: 3e5cb21e-3-129655510216406250 ProcessId: 2444 Process Name: C:\Program Files\Common Files\Microsoft Shared\DevServer\10.0\WebDev.WebServer40.exe Thread Name: Win32 ThreadId:2748 Extended Properties: ----------------------------------------
你可以看到上面的EventId=9000与我们之前在CODE中配置是相同的.
在开源社区有一个组件ELMAH(Error Logging Modules and Handlers for ASP.NET),已实现Error处理发邮件,写DB,发送到SNS等功能. 我们随意来看下它的代码:
它就是基于IHttpModule的扩展,下面代码来ELMAH:

1: /// <summary>
2: /// Provides an abstract base class for <see cref="IHttpModule"/> that
3: /// supports discovery from within partial trust environments.
4: /// </summary>
5: public abstract class HttpModuleBase : IHttpModule
6: {
7: void IHttpModule.Init(HttpApplication context)
8: {
9: if (context == null)
10: throw new ArgumentNullException("context");
11:
12: if (SupportDiscoverability)
13: HttpModuleRegistry.RegisterInPartialTrust(context, this);
14:
15: OnInit(context);
16: }
17:
18: void IHttpModule.Dispose()
19: {
20: OnDispose();
21: }
22:
23: /// <summary>
24: /// Determines whether the module will be registered for discovery
25: /// in partial trust environments or not.
26: /// </summary>
27: protected virtual bool SupportDiscoverability
28: {
29: get { return false; }
30: }
31:
32: /// <summary>
33: /// Initializes the module and prepares it to handle requests.
34: /// </summary>
35: protected virtual void OnInit(HttpApplication application) {}
36:
37: /// <summary>
38: /// Disposes of the resources (other than memory) used by the module.
39: /// </summary>
40: protected virtual void OnDispose() {}
41: }

这是ErrorLogModule实现之前HttpModuleBase:

1: public class ErrorLogModule : HttpModuleBase, IExceptionFiltering
2: {
3: public event ExceptionFilterEventHandler Filtering;
4: public event ErrorLoggedEventHandler Logged;
5:
6: /// <summary>
7: /// Initializes the module and prepares it to handle requests.
8: /// </summary>
9:
10: protected override void OnInit(HttpApplication application)
11: {
12: if (application == null)
13: throw new ArgumentNullException("application");
14:
15: application.Error += new EventHandler(OnError);
16: ErrorSignal.Get(application).Raised += new ErrorSignalEventHandler(OnErrorSignaled);
17: }
18:
19: /// <summary>
20: /// Gets the <see cref="ErrorLog"/> instance to which the module
21: /// will log exceptions.
22: /// </summary>
23: protected virtual ErrorLog GetErrorLog(HttpContext context)
24: {
25: return ErrorLog.GetDefault(context);
26: }
27:
28: /// <summary>
29: /// The handler called when an unhandled exception bubbles up to
30: /// the module.
31: /// </summary>
32: protected virtual void OnError(object sender, EventArgs args)
33: {
34: HttpApplication application = (HttpApplication) sender;
35: LogException(application.Server.GetLastError(), application.Context);
36: }
37:
38: /// <summary>
39: /// The handler called when an exception is explicitly signaled.
40: /// </summary>
41: protected virtual void OnErrorSignaled(object sender, ErrorSignalEventArgs args)
42: {
43: LogException(args.Exception, args.Context);
44: }
45:
46: /// <summary>
47: /// Logs an exception and its context to the error log.
48: /// </summary>
49: protected virtual void LogException(Exception e, HttpContext context)
50: {
51: if (e == null)
52: throw new ArgumentNullException("e");
53:
54: //
55: // Fire an event to check if listeners want to filter out
56: // logging of the uncaught exception.
57: //
58:
59: ExceptionFilterEventArgs args = new ExceptionFilterEventArgs(e, context);
60: OnFiltering(args);
61:
62: if (args.Dismissed)
63: return;
64:
65: //
66: // Log away...
67: //
68:
69: ErrorLogEntry entry = null;
70:
71: try
72: {
73: Error error = new Error(e, context);
74: ErrorLog log = GetErrorLog(context);
75: string id = log.Log(error);
76: entry = new ErrorLogEntry(log, id, error);
77: }
78: catch (Exception localException)
79: {
80: //
81: // IMPORTANT! We swallow any exception raised during the
82: // logging and send them out to the trace . The idea
83: // here is that logging of exceptions by itself should not
84: // be critical to the overall operation of the application.
85: // The bad thing is that we catch ANY kind of exception,
86: // even system ones and potentially let them slip by.
87: //
88:
89: Trace.WriteLine(localException);
90: }
91:
92: if (entry != null)
93: OnLogged(new ErrorLoggedEventArgs(entry));
94: }
95:
96: /// <summary>
97: /// Raises the <see cref="Logged"/> event.
98: /// </summary>
99: protected virtual void OnLogged(ErrorLoggedEventArgs args)
100: {
101: ErrorLoggedEventHandler handler = Logged;
102:
103: if (handler != null)
104: handler(this, args);
105: }
106:
107: /// <summary>
108: /// Raises the <see cref="Filtering"/> event.
109: /// </summary>
110: protected virtual void OnFiltering(ExceptionFilterEventArgs args)
111: {
112: ExceptionFilterEventHandler handler = Filtering;
113:
114: if (handler != null)
115: handler(this, args);
116: }
117:
118: /// <summary>
119: /// Determines whether the module will be registered for discovery
120: /// in partial trust environments or not.
121: /// </summary>
122: protected override bool SupportDiscoverability
123: {
124: get { return true; }
125: }
126: }

更多的功能等待您去挖掘,我们在实际开发中按需选择.希望这篇POST对您开发有帮助.

你可能感兴趣的文章:
在VS2010中配制Elmah邮件发送到Gmail
HttpModule应用:
使用HttpModules实现Asp.net离线应用程序
 Asp.net使用HttpModule压缩并删除空白Html请求

 Asp.net移除Server, X-Powered-By, 和X-AspNet-Version头
Enterprise Library:

使用Fluent配置API驱动Enterprise Library 5.0
EneterpriseLibrary5的Fluent配制API

作者：Petter Liu
出处：http://www.cnblogs.com/wintersun/
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。
该文章也同时发布在我的独立博客中-Petter Liu Blog。
本文链接