Fix an inadvertent 204 in activator tests

On a web server, this test ends up giving back a 204 because of the MVC
behavior when an action is declared to return void. The fix is to use
EmptyResult.
This commit is contained in:
Ryan Nowak 2014-12-10 15:54:06 -08:00
parent ba5712c824
commit 1a617eb533
1 changed files with 5 additions and 2 deletions

View File

@ -1,6 +1,7 @@
// Copyright (c) Microsoft Open Technologies, Inc. All rights reserved. // Copyright (c) Microsoft Open Technologies, Inc. All rights reserved.
// Licensed under the Apache License, Version 2.0. See License.txt in the project root for license information. // Licensed under the Apache License, Version 2.0. See License.txt in the project root for license information.
using System.Threading.Tasks;
using Microsoft.AspNet.Http; using Microsoft.AspNet.Http;
using Microsoft.AspNet.Mvc; using Microsoft.AspNet.Mvc;
@ -8,13 +9,15 @@ namespace ActivatorWebSite
{ {
public class RegularController : Controller public class RegularController : Controller
{ {
public void Index() public async Task<EmptyResult> Index()
{ {
// This verifies that ModelState and Context are activated. // This verifies that ModelState and Context are activated.
if (ModelState.IsValid) if (ModelState.IsValid)
{ {
Context.Response.WriteAsync("Hello world").Wait(); await Context.Response.WriteAsync("Hello world");
} }
return new EmptyResult();
} }
} }
} }