A couple years back, I outlined how you could get Sitefinity running on an Azure VM. However, with a new dev environment to setup, more advancements in hosting platforms, I went back to see if I could get my Sitefinity site running through the typical Azure App and Database services. Good news is you can and it’s quite simple. Continue reading “Running Sitefinity in Azure Services”
PowerShell to the rescue once again! A week back I needed to create an archive of all of the video content processed by Azure Media Services (AMS). While I have used my trusty Azure Storage Explorer tool in the past, it only allowed me to deal with one container at a time. AMS is structured so that each new job that was created stored it’s files in a new container, which made manually grabbing 250+ containers named with GUIDs rather difficult. Continue reading “How to Download All Containers and Blobs in Azure with PowerShell”
Sometimes you just have to stick with older code…
I ran into a problem a while back when deploying an application to Azure that was using the DNX / .Net Core RC1 Framework. I started seeing errors such as:
Unable to resolve dependency Microsoft.Extensions.Options 1.0.0-rc2-final
Similarly when I would attempt to compile I would see an error such as:
The dependency Microsoft.Extensions.Options 1.0.0 in project ZZZ does not support framework DNX,Version=v4.5.1.
Something strange was going on… Continue reading “Quick Tip: Maintaining .Net Core RC1 Project References in Azure”
TL;DR; – When using multiple project solutions, make sure you database context and configuration connection strings are named the same across all projects. Continue reading “Azure Tip – Check Cross Project Connection Strings”
This is probably a fringe case, but here’s the scenario. I have a site for a client that is actually broken down into several projects, but not in a single solution. The layout looks something like this:
- Root Folder
- index.html (basic home page with links to project roots)
By default, if you were to have your root folder checked into source control, and had Azure deploy from the root folder, you’d either have only Project A deployed on the site, or most likely, the deployment would fail with a message that it doesn’t know what project to deploy.
There was nothing I could do to get around this situation, but I did come up with a way to make it work.
I’ve been doing a lot of coding with Windows Azure as the hosted platform lately. I’ve really been impressed by the power and flexibility that is avaialable. One thing I recently did was create a tool that imports data from a mainframe system into our database using the new WebJobs feature available. This leverages the Azure storage containers to save the data files and logs for easy retrieval and prevents them from being removed.
While Azure storage does provide automatic cleaning of it’s internal logs, it doesn’t provide a way to automatically clean out old files in your containers. Our containers were filling up pretty fast and the policy was to only retain records for 30 days. Fortunately, you can create a simple script (and save it as a WebJob) to keep your containers nice and tidy.
I had a guest post over at my employer’s blog about Azure WebJobs. Check it out!