File => Attach To Process, pick devenv.exe
.symfix
.reload
.loadby sos clr
| apt-get install -y wget build-essential gettext autoconf automake libtool | |
| wget http://download.mono-project.com/sources/mono/mono-3.2.3.tar.bz2 | |
| bunzip2 -df mono-3.2.3.tar.bz2 | |
| tar -xf mono-3.2.3.tar | |
| cd mono-3.2.3 | |
| ./configure --prefix=/usr/local; make; make install | |
| rm -rf /tmp/* | |
| apt-get remove --purge wget build-essential gettext autoconf automake libtool |
| public class Server | |
| { | |
| private readonly NetMQContext _context; | |
| private readonly string _id; | |
| public Server(NetMQContext context, string id) | |
| { | |
| _context = context; | |
| _id = id; | |
| } |
| using System; | |
| using System.Collections.Generic; | |
| using System.Collections.Specialized; | |
| // As opposed to magic validation libraries that rely on reflection and attributes, | |
| // applicative validation is pure, total, composable, type-safe, works with immutable types, and it's easy to implement. | |
| public abstract class Result<T> { | |
| private Result() { } |
| namespace Topshelf | |
| [<AutoOpen>] | |
| module Topshelf = | |
| open System | |
| open Topshelf.HostConfigurators | |
| open Topshelf.Runtime | |
| let configureTopShelf f = |
| // This F# dojo is directly inspired by the Digit Recognizer | |
| // competition from Kaggle.com: | |
| // http://www.kaggle.com/c/digit-recognizer | |
| // The datasets below are simply shorter versions of | |
| // the training dataset from Kaggle. | |
| // 0. Load data files from the following location: | |
| // http://brandewinder.blob.core.windows.net/public/digitssample.csv | |
| // http://brandewinder.blob.core.windows.net/public/digitscheck.csv |
| namespace PKI | |
| { | |
| class Results : IEquatable<Results> | |
| { | |
| internal static readonly Results NotFound = new Results | |
| { | |
| Directory = "", | |
| KeyName = "" | |
| }; |
Have you ever had to write code that made a complex series of succesive modifications to a single piece of mutable state? (Almost certainly yes.)
Did you ever wish you could make the compiler tell you if a particular operation on the state was illegal at a given point in the modifications? (If you're a fan of static typing, probably yes.)
If that's the case, the indexed state monad can help!
Motivation
| using System; | |
| using System.IO; | |
| using MsgPack.Serialization; | |
| using ZeroMQ_MessagePack_Testbed.Models; | |
| using ZMQ; | |
| namespace ZeroMQ_MessagePack_Testbed | |
| { | |
| class Program | |
| { |
| [TestFixture] | |
| public class SpecificationFixture | |
| { | |
| [Test, TestCaseSource("GetSpecificationTestCases")] | |
| public void Verify(SpecificationToRun spec) | |
| { | |
| var runner = new SpecificationRunner(); | |
| RunResult result = runner.RunSpecifciation(spec); | |
| if (result.Passed) |