Skip to content

Instantly share code, notes, and snippets.

Cameron Wills CameronWills

  • Sydney, Australia
Block or report user

Report or block CameronWills

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View frontend-checklist.md

Pull Request Checklist

Mark [x] to those completed. Delete sections that don't apply.

Linting
[] Fixed CSS errors? [] Fixed JS errors?

Browsers

@CameronWills
CameronWills / edit-mode.css
Created Mar 26, 2017
EpiServer v10 all properties view - Add a red star (*) to required properties / field labels
View edit-mode.css
/* Add a required star (*) to fields marked as required */
.Sleek .epi-form-container__section__row label span.edit-required {
font-weight: bold;
color: red;
}
@CameronWills
CameronWills / EpiServerImageService.cs
Last active Mar 8, 2017
Implementation of ImageProcessor's IImageService interface for EpiServer - Retrieves EpiServer blobs for processing by ImageProcessor
View EpiServerImageService.cs
/// <summary>
/// EpiServer implementation of an ImageProcessor IImageService - provides the episerver image blobs to ImageProcessor for resizing etc.
/// </summary>
public class EpiServerImageService : IImageService
{
/// <summary>
/// Gets or sets the prefix for the given implementation.
/// <remarks>
/// This value is used as a prefix for any image requests that should use this service.
/// </remarks>
View Git-Branching-Strategy.md

When working on our git repositories, this is the general workflow / branching strategy we follow:

  • Development happens on the master branch (this way new developers can start writing code as soon as they've clone the repository)

  • Long-running development on a features/feature_name branch and then merged into master

  • Work to be done by vendors happen on a vendors/vendor_name branch and merged into master after being checked over (use pull requests).

  • Merge master into deploy/production or deploy/qa to trigger the respective deployment in the CI/CD tool.

@CameronWills
CameronWills / AzureBlobLog.cs
Last active Oct 5, 2016
A utility class to 'query' the application logs (System.Diagnostics.Trace) stored in Azure Blob storage - recursively descends log folder structure to find log files that match the requested date range and returns the nested log (.csv) files
View AzureBlobLog.cs
/*
You will need to get install these two nuget libraries:
WindowsAzure.Storage
CsvHelper
*/
using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
@CameronWills
CameronWills / FormsPersistence.cs
Last active Aug 23, 2016
Persists and restores umbraco form files to and from the media IFileSystem storage (Amazon S3 or Azure Blob Storage)
View FormsPersistence.cs
/*
IMPORTANT:
To enable the persist operation, you need to add an AppSetting in your web.config file:
<add key="persistFormsOnChange" value="true" />
This should only be set to true on the Admin/BackOffice server.
@CameronWills
CameronWills / blog-may-3th-2016.md
Last active May 3, 2016
Blog May 3th 2016 - Convenient Wisdom
View blog-may-3th-2016.md

Micro-blog - Convenient Wisdom!

For months (years) now, I've been thinking of creating a small blog to share some less-common .NET development and DevOps problems I come across at work, and in particular those that are uncommon or have less-documented solutions. I figure I cant possibly be the only one coming across these problems - so why not share my solutions. Some of these probably belong in Stack Overflow, but then sometimes the question doesn't exist, and answering your own questions to comply with their guidelines seems awkward. So, what simpler micro-blogging platform than Github Gist? It seems fitting for a developer. So here goes!

You can’t perform that action at this time.