OJ Develops

Thoughts on software development. .NET | C# | Azure

Building a Deployment Package with Static Content

24 September 2013

Building a Deployment Package with Static Content thumbnail

I was once working on a MVC 3 project. The project included the usual web stuff: controllers, views, models, images, css files, and javascript files. There are also a couple of Excel files that we use.

Come deployment time, I followed the steps in building a deployment package. To my surprise (horror), a lot of the css, javascript, and image files were not loaded! Even the Excel files could not be found. So what happened?

Including Files in the Deployment Package

Class files, which are files that end with .cs, are included and built with no problem. However, special treatment has to be given to non-compiled or static files, such as css, javascript, and other non-compiled content.

There are two steps for static files to get included in the package:

  1. Add them to the solution.
  2. Set the appropriate build action (such as Content).

Adding an item to the solution is fairly simple: just right click on the containing folder, then choose Add > Existing Item, then look for the file you wish to add and add it. Note that even if a css / js file is not added to the solution, it will get loaded during debugging but will not be included in the deployment package. This situation rarely happens, but if it does, it is usually detected late.

In addition to adding to the solution, the appropriate build action should also be specified for the static resource. For static resources, the build action is Content. To change the build action, right click on the file then click Properties. The Build Action is in the Advanced section. Just select Content and you’re set. There are several build actions available, but I found that Content is enough for css, javascript, images, and even Excel files.

content build action

After following those steps, all the needed files will be included in the deployment package.