peterdemartini

find `pwd` -type d -maxdepth 3 -name 'node_modules' | xargs -n 1 tmutil addexclusion

juristr

Git Cheat Sheet

Committing and Undoing

Adding file for committing

$ git add <filename>

kraz

@echo off

SET BOOTSTRAP=.\docs\assets\css\bootstrap.css
SET BOOTSTRAP_LESS=.\less\bootstrap.less
SET BOOTSTRAP_RESPONSIVE=.\docs\assets\css\bootstrap-responsive.css
SET BOOTSTRAP_RESPONSIVE_LESS=.\less\responsive.less
SET "CHECK= "
SET HR=##################################################

::Try to use the local build tools, if installed instead of global ones

justinbmeyer

If the users's time was 1970-01-01 and they were shown a page titled "tomorrows reservations", it would show no reservations.

However, this would be correct from the user's computer's perspective, just not from reality (unless maybe they are traveling at light speed).

In my opinion, despite the advantage of always showing reality, no matter what time the user has, it's better to use the client's local time for the following reasons:

• expectations
• accuracy

jstangroome

<!-- Insert this Sequence as one of the last children of the Sequence with DisplayName="Compile and Test" -->
<Sequence>
  <Sequence.Variables>
    <Variable x:TypeArguments="mtbc:IBuildDetail" Name="LastBuildDetail" />
    <Variable x:TypeArguments="x:Int32" Name="LastWarningCount" />
    <Variable x:TypeArguments="x:Int32" Name="WarningCount" />
  </Sequence.Variables>
  <Assign x:TypeArguments="mtbc:IBuildDetail" To="[LastBuildDetail]" Value="[BuildDetail.BuildServer.GetBuild(BuildDetail.BuildDefinition.LastBuildUri)]"  />
  <Assign x:TypeArguments="x:Int32" To="[LastWarningCount]" Value="[Microsoft.TeamFoundation.Build.Client.InformationNodeConverters.GetBuildWarnings(LastBuildDetail).Count]"  />