vb net code 128 checksum Deploying to IIS 7 in .NET

Generation Code 128 Code Set C in .NET Deploying to IIS 7

Before we look at automating our deployments, we need to configure our server to host an ASP.NET MVC website.

An MVC website needs a location on the target machine s hard drive. For this book, the location is unimportant, so we ll choose something simple: C:\websites\MVCSample. Our sample application will have no dependencies on a database, but later we ll look at how to incorporate a database into our deployment strategy. Our controller for this sample application will be simple, but it ll incorporate some common routes, as shown in listing 6.1.

public class ProductController : Controller { private static readonly Product[] Products = new[] { new Product {Id = 1, Name = "Basketball", Description = "You bounce it."}, new Product {Id = 2, Name = "Baseball", Description = "You throw it."}, new Product {Id = 3, Name = "Football", Description = "You punt it."}, new Product {Id = 4, Name = "Golf ball", Description = "You hook or slice it."} }; public ActionResult List() { ViewData["Products"] = Products; return View(); }

One parameter,

from RouteData public ActionResult Show(int id) { var product = Products.FirstOrDefault(p => p.Id == id);

ViewData["Product"] = product; return View(); } }

To deploy this ASP.NET MVC application to an IIS 7 box, we first need to create a local folder and move all our deployment files over. For this sample application, the folder structure is as follows:

System.Web.Mvc.dll doesn t need to be in the bin folder if the MVC2 installer has been run on the target server.

When the content is in place, we can configure a new website in the IIS Manager by clicking Add Web Site, as shown in figure 6.2. In the Add Web Site dialog box that comes up, we need to configure the following:

Site Name For this, I chose an arbitrary name that didn t exist: MVCSample. Application Pool Any application pool will suffice, as long as it s configured as either a .NET 2.0 or 4.0 application pool. In IIS 7 or 7.5, you should use Integrated mode, although you can make Classic

mode work with a wildcard mapping. ASP.NET MVC isn t supported to run on lower versions of ASP.NET, but it s forward-compatible and runs on .NET 4 as well. We won t look at application pool strategies, but with IIS 6 onward, IIS supports multiple websites, each with a shared or individual application pool. Physical Path This will point to our C:\Websites\MVCSample directory. Binding I chose simply to bind to port 81 for this website. You can choose any unused port.

Typically in production scenarios, the Host Name field would be configured. The final configuration values are shown in figure 6.3. Now that our website is configured and started, we can navigate to our MVC application, as seen in figure 6.4. Unless we want to configure additional security or bindings, we don t have to perform any additional steps to get our MVC application running under IIS 7. The new managed architecture of IIS 7 allows us to have simple deployments. Additionally, our URLs look exactly the same as they did when running locally out of Visual Studio, without .aspx or other extensions. IIS 7 supports pretty URLs out of the box, with no configuration necessary. In the next section, we ll examine configuration options available in IIS 6 and 5, and see how we can achieve the same effect of pretty URLs.

When we deploy our MVC application to IIS 6 and earlier, we can consider a few options concerning routes. IIS 6 and earlier use ISAPI filters, which map file extension requests to ISAPI handlers. Extensions, such as .aspx and .ascx, map to the ASP.NET ISAPI handler, but extensions in the pretty, extensionless MVC URLs don t. By the time ASP.NET handles the request, IIS has already chosen an ISAPI handler for the request, and the selection may not be ASP.NET. Unfortunately, developing custom ISAPI filters requires C/C++ knowledge. Some open source projects exist for writing managed ISAPI filters, but it isn t as easy as creating a custom IHttpHandler or IHttpModule implementation. Out of the box, ASP.NET MVC applications won t work in IIS 6. Getting an MVC application to run successfully in an IIS 6 environment requires either changes to our routes or extra configuration steps in IIS. We have four choices for deploying to IIS 6:

Configure routes to use the .aspx extension Configure routes to use a custom extension (such as .mvc) Use a wildcard mapping with selective disabling Use URL rewriting