Search Results

If you use Octopusdeploy to deploy your Umbraco sites, you've probably forgotten to increment the Client Dependency version before building and deploying - which leads to old CSS and JavaScript being served.
OctopusDeploy allows you to run custom...['Octopus.Release.Number'])" | Out-File "bin\version.txt"
The script should be run post deployment. Rather than incrementing the client dependency version - it derives an integer from the octopus release version, so the client dependency version is distinct for each release.
If you need some help setting up Octopusdeploy and Umbraco - get in touch with me, via my company website.

- I'll look at how I can render this content as webpages in Umbraco templates. In part 3 I'll look at how to deploy this runtime into production without Umbraco, so I've truly separated my runtime and my CMS.
For those of you still thinking Why

of the Visual Studio solution:
Moriyam.Blog.Umbraco - is Umbraco installed with Nuget
Moriyama.Blog.Site - is my MVC application that I will eventually deploy to Azure websites as the runtime
Moriyama.Blog.Runtime.Umbraco - Stuff to serialise content