arackaf

/*
See the readme for detailed guidance, as well as inline comments here.
*/

const Builder = require("systemjs-builder"),
  gulp = require("gulp"),
  gulpIf = require("gulp-if"),
  gulpUglify = require("gulp-uglify"),
  gulpRename = require("gulp-rename"),
  gulpPlumber = require("gulp-plumber"),

adamralph

<Query Kind="Statements">
  <NuGetReference>Humanizer</NuGetReference>
  <NuGetReference>Octokit</NuGetReference>
  <Namespace>Humanizer</Namespace>
  <Namespace>Octokit</Namespace>
  <Namespace>Octokit.Internal</Namespace>
  <Namespace>System.Threading.Tasks</Namespace>
</Query>

// I wrote this script to help me find out where my NuGet packages are being used.

khalidabuhakmeh

There are designers on our team that primarily work on their MacBook Pros. They do their CSS, Js, and HTML work without ever opening Visual Studio. It would be nice if they could at least adopt Razor when developing the views and components. I want to build a utility that can render a snippet / partial view / view without the need to run the application.

> razor-render .

This command would do the following.

1. Figure out a layout if applicable
2. Determine the model of all the views and "stub" it

markrendle

Thoughts on project files

I missed last night's ASP.NET Community Standup on account of being shattered after a long day and falling asleep. Then I checked Twitter on the train this morning and discovered that the .NET world had, apparently, been burned to the ground by marauding Microsofties (again). It seemed to have something to do with project files, JSON vs XML, and suchlike.

Finally, lunchtime happened and I could watch the recording of the standup, and I got to understand what everyone was on about. In case you've missed it:

The TL;DR history

1. In the beginning, there was make, and Gates did not own make, so Gates said "Let there be MSBuild" and there was MSBuild.
2. And MSBuild used the *.*proj files from Visual Studio as its inputs, which were formed of terrible XML, and verily it was impossible to use without a Visual Studio license.