thecodejunkie

        /// <summary>
        /// Creates a per request child/nested container
        /// </summary>
        /// <returns>Request container instance</returns>
        protected override ILifetimeScope CreateRequestContainer()
        {
            return ApplicationContainer.BeginLifetimeScope("AutofacRequestLifetime");
        }

        /// <summary>

markryd

• Start up windbg and attach (F6).
• Make sure you pick the right version (x86/x64) and run as admin if your app is running as admin.
• Make sure you have the microsoft symbol servers turned on in Visual Studio -> tools -> options -> debugging -> symbols

Load

.loadby sos clr

Dump the heap

tathamoddie

[alias]
	st = status
	ci = commit
	br = branch
	co = checkout
	com = checkout master
	fe = fetch origin
	bn = !git for-each-ref --format='%(refname:short)' `git symbolic-ref HEAD`
	rb = rebase
	rbm = rebase master

michaelnoonan

Set-StrictMode -Version Latest

$libPath = (Split-Path -Parent $MyInvocation.MyCommand.Definition)
Import-Module $libPath\SecurityLib.psm1

function New-WindowsService {
  param
	(
		[Parameter(Mandatory=$True,Position=0,HelpMessage="The name of the Windows Service")]
		[string]$serviceName,

jelbourn

/**
 * Example of using an angular provider to build an api service.
 * @author Jeremy Elbourn (@jelbourn)
 */

/** Namespace for the application. */
var app = {};

/******************************************************************************/

CMCDragonkai

AngularJS Directive Attribute Binding Explanation

When using directives, you often need to pass parameters to the directive. This can be done in several ways. The first 3 can be used whether scope is true or false. This is still a WIP, so validate for yourself.

1. Raw Attribute Strings

   <div my-directive="some string" another-param="another string"></div>

17twenty

a simple git branching model

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

The gist

gregoryyoung

namespace crap
{
    using System;
    using System.Collections.Generic;
    using System.Data;
    using System.Data.SqlClient;



    public class PartialAppPlayground

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

OverZealous

//<editor-fold desc="Node Requires, gulp, etc">
var gulp = require('gulp'),
	autoprefixer = require('gulp-autoprefixer'),
	clean = require('gulp-clean'),
	concat = require('gulp-concat'),
	csso = require('gulp-csso'),
	debug = require('gulp-debug'),
	footer = require('gulp-footer'),
	gutil = require('gulp-util'),
	gzip = require('gulp-gzip'),