andrewabest

echo off

:: download OpenSSL if you don't have it for the below

:: Conver the p7b into PEM format
openssl pkcs7 -in mydomain.p7b -print_certs -out mydomain.pem

:: Combine this with the crt server certificate and private key into a PFX
openssl pkcs12 -export -in mydomain.crt -inkey mydomain.key -certfile mydomain.pem -out mydomain.pfx

andrewabest

public abstract class NancyIntegrationScenario
    {
        private IContainer integrationTestContainer;
        private readonly ContainerBuilder containerOverrides = new ContainerBuilder();

        [TestFixtureSetUp]
        public void TestFixtureStart()
        {
            integrationTestContainer = CreateIntegrationContainer();
            BuildTestDatabase();

andrewabest

echo off

:: download OpenSSL if you don't have it for the below

:: Extract the private key from the pfx, and convert it to rsa format
openssl pkcs12 -in wildcard_mydomain_com.pfx -nocerts -nodes -passin pass:eb | openssl rsa -out wildcard_mydomain_com.key

:: Extract the public key from the pfx, and convert it to x509
openssl pkcs12 -in wildcard_mydomain_com.pfx -clcerts -nokeys -passin pass:eb | openssl x509 -out wildcard_mydomain_com.cer

andrewabest

Setting up TeamCity and Octopus with GitVersion

Assumptions

• You are using GitFlow
• You want to deploy a new version of your software every time a commit is made to the develop branch
• You are using Octopack to package your application for deployment

Instructions

andrewabest

<rewrite>
  <rules>
      <rule name="HTTPS_AlwaysOn" patternSyntax="Wildcard">
          <match url="*" />
          <serverVariables>
              <set name="HTTPS" value="on" />
          </serverVariables>
          <action type="None" />
          <conditions>
              <add input="{HTTP_X_FORWARDED_PROTO}" pattern="https" />

andrewabest

Import-Module WebAdministration
Set-WebConfigurationProperty system.webServer/proxy -Name enabled -Value "True"

Add-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST'  -filter "system.webServer/rewrite/globalRules" -name "." -value @{name='Stores';stopProcessing='True'}
Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST'  -filter "system.webServer/rewrite/globalRules/rule[@name='Stores']/match" -name "url" -value "^Stores/?(.*)/?$"
Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST'  -filter "system.webServer/rewrite/globalRules/rule[@name='Stores']/action" -name "type" -value "Rewrite"
Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST'  -filter "system.webServer/rewrite/globalRules/rule[@name='Stores']/action" -name "url" -value "http://localhost:10003/Stores/{R:1}"

andrewabest

“Done” has a special meaning in agile projects. It’s not “done but…” or “done except…” but “Done” with a capital D. This means that a story or task has satisfied all of its acceptance criteria and our global done criteria.

• Acceptance criteria satisfied.
• All code written.
• All tests pass.
• There are (at least some) tests for new code.
• Tests (at least one) added when touching existing code.
• Build is green.
• Code merged to refs/heads/develop via PR
• Deployed to CI

andrewabest

using System;
using System.Runtime.InteropServices;

namespace Things
{
    public static class LandLordExtensions
    {
        public static LandLord<TWrapped> AsDisposable<TWrapped>(this TWrapped tenant)
        {
            return new LandLord<TWrapped>(tenant);

andrewabest

First

• Download Git-Tfs from https://github.com/git-tfs/git-tfs/releases and extract the zip to c:\GitTfs
• Add ;c:\GitTfs to your path. Now you have a git-tfs bridge!

Then

To clone the main branch of your TFS project as a git repo (aka get the codez):

• Create a new directory to store your git projects, seperate from your 'standard' TFS source directory**. (For example, use c:\projects.git instead of c:\projects)
• Open a command prompt and navigate to your git source directory.

andrewabest

Same-Origin Policy

Each browser has it's own Same-Origin policy (https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) that it enforces to avoid certain types of CSRF attacks.

If a browser's SOP is triggered when attempting to send a request, it will either refuse to send the request*, or trigger an OPTIONS request to be sent, which the server must respond to with a list of Access-Control headers (http://www.w3.org/TR/cors/#syntax). The browser can then inspect these to determine whether it is good to go ahead and send the request or not.

IE Gotchas