Deploying MVC 3 Site

Legacy Uncategorised
1

Hey,

Okay, so I’m not quite sure if I’m doing this correctly but I’ve done the following:

  • Run nuget spec on a project
  • Checked the project in to TFS
  • Queued it for build, which was successful
  • Run the commands to publish to my nuget server (I’ll put those in as a post build step soon, currently doing it manually)
  • Created a new release for a project in Octopus Deploy (OD), selecting the expected package, etc.
  • Deployed

What I seem to get is my website has the following at the root directory:

  • content <- site is in here
  • lib

Even if I browse to the content subfolder, the site gives me the error Could not load type 'ODProjectTest.MvcApplication' - am I deploying this MVC3 site incorrectly? Are you aware of any “How to deploy MVC3 sites using OD” articles/tutorials? It’s taken me a while to get to this point, and I’m SO SO close to being able to use OD for all my projects.

Please Obi Wan, you’re my only hope,
Kori

2

Hi Kori,

Sorry for the late reply on this one. The following page explains how creating Octopus-compatible packages is different to the standard NuGet packaging process, including the “lib” folder issue:

https://octopus.atlassian.net/wiki/display/help/Packaging

I’d recommend using OctoPack to create a compatible package:

https://octopus.atlassian.net/wiki/display/help/OctoPack

Hope that helps,

Paul

3

Perfect, I’ve been able to get this working since this post.

Also, I’ve just purchased an enterprise license. :slight_smile: