Skip to content

Instantly share code, notes, and snippets.

Henrik Lau Eriksson hlaueriksson

Block or report user

Report or block hlaueriksson

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
hlaueriksson / clear.ps1
Last active Aug 4, 2018
Clear all MSMQ queues with PowerShell
View clear.ps1
Get-MsmqQueue | Clear-MsmqQueue
hlaueriksson / clean.ps1
Last active Oct 17, 2018
Delete bin/obj folders with PowerShell (Admin)
View clean.ps1
Get-ChildItem -inc bin,obj -rec | Remove-Item -rec -force
davidfowl / Example1.cs
Last active Nov 19, 2019
How .NET Standard relates to .NET Platforms
View Example1.cs
namespace Analogy
/// <summary>
/// This example shows that a library that needs access to target .NET Standard 1.3
/// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET
/// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library.
/// </summary>INetCoreApp10
class Example1
public void Net45Application(INetFramework45 platform)
davidfowl /
Last active Nov 20, 2019
.NET project structure
stevenkuhn / gist:5062660
Last active May 26, 2019
This PowerShell script generates release notes for Octopus Deploy that contain the GitHub commits and JIRA issues from the current build to the latest production release. It will also create the Octopus release based on the TeamCity build number.
View gist:5062660
# Assumptions
# 1. If you have a Octopus release deployed, say, there is a git
# tag set for that commit in GitHub that is "v1.0.0.73".
# 2. You have TeamCity label each successful build in GitHub with the format
# "v{build number}. Sidenote: it appears that TeamCity only labels the
# default branch, but not feature branches.
You can’t perform that action at this time.