Pull Request Checklist
Mark [x] to those completed. Delete sections that don't apply.
 Fixed CSS errors?  Fixed JS errors?
|/// Replacing the logic found in the IndexingService.svc to try and address a bug at where the run-time compiled assembly has a file-change causing the|
|/// App Domain to shutdown/restart. In some cases the shutdown failed, resulting in two AppDomains to be running. More details here:|
|/// EpiServer implementation of an ImageProcessor IImageService - provides the episerver image blobs to ImageProcessor for resizing etc.|
|public class EpiServerImageService : IImageService|
|/// Gets or sets the prefix for the given implementation.|
|/// This value is used as a prefix for any image requests that should use this service.|
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.
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!