davidfowl

$/
  artifacts/
  build/
  docs/
  lib/
  packages/
  samples/
  src/
 tests/

trollixx

#!/bin/bash

# Based on http://development.adaptris.net/users/lchan/blog/2013/06/07/signing-windows-installers-on-linux/

openssl pkcs12 -in $1 -nocerts -nodes -out .key.pem
openssl pkcs12 -in $1 -nokeys -nodes -out .cert.pem
openssl rsa -in .key.pem -outform DER -out .authenticode.key
openssl crl2pkcs7 -nocrl -certfile .cert.pem -outform DER -out .authenticode.spc
osslsigncode -spc .authenticode.spc -key .authenticode.key -t http://timestamp.verisign.com/scripts/timstamp.dll -in $2 -out $3
rm .key.pem .cert.pem .authenticode.key .authenticode.spc

macromaniac

module XHR {

	export class Header {
		header: string;
		data: string;
		constructor(header: string, data: string) {
			this.header = header;
			this.data = data;
		}
	}

juanca

javascript:
document.querySelectorAll('.load-diff-button').forEach(node => node.click())

mavasani

Feature Request

dotnet/roslyn#30172: Programmatic suppression of warnings

Provide an ability for platform/library authors to author simple, context-aware compiler extensions to programmatically suppress specific instances of reported analyzer and/or compiler diagnostics, which are always known to be false positives in the context of the platform/library.

Programmatically Suppressible Diagnostic

An analyzer/compiler diagnostic would be considered a candidate for programmatic suppression if all of the following conditions hold:

1. Not an error by default: Diagnostic's DefaultSeverity is not DiagnosticSeverity.Error.

leppie

unsafe class Program
{
    delegate int? bar(int* i);
    static void Main(string[] args)
    {
        int[] ω = {};
        var Ʃ = 42;
        int? Φ = null;
        bar ϼ = default;

okyrylchuk

foreach (int i in 3..5)
{
    Console.WriteLine(i);
}

foreach (int i in ..3)
{
    Console.WriteLine(i);
}