Halide for ASP.NET/MVC
This project uses the newer project file "PackageResource" configuration for NuGet packages. This means that Halide's NuGet packages are downloaded to your user folder, and used much like assemblies in the GAC, so they won't interfere with the /packages folder in the root of your project if you're using the standard (default) packages.config method in your solution.
1. NuGet method
Halide can be installed in several ways, depending on how you want to use it. If you're simply interested in using it as-is to gain the feature benefits, you could simply install the Nuget package. This will provide a simple means to get up and running, and also allow you to stick with specific versions.
2. Download method
You could also download the project and incorporate the files into your project. In the future you would have to update Halide manually, but it would provide a way to use Halide without an additional repository.
3. Cloned repository method
The recommended way to incorporate Halide is to add the Halide repository to your project (solution) folder as a git submodule. In this way you have control over the version of Halide being used, and can pull changes from the master repository.
Currently, Halide is built on .NET CLR 4.5.
NOTE: Turn on 64-bit IIS Express in Visual Studio, or you won't be able to debug unless all projects in the solution are set to x86. This is due to SharpScss detecting which binary is being used based on compilation flags. It will default to x64 for "Any CPU" configurations even though Visual Studio will always prefer x86. This shouldn't affect deployments to IIS, provided the app pool for the site isn't set to use 32-bit mode.