The recommended approach is to create an ASP.NET project to serve your initial page (index.html, default.html, or whatever), and possibly to host your web services. Then create another project of type class-library, which will be your Acute client-application project.

The easiest way to install Acute into your solution is via Nuget.

Simply install the Acute nuget package into your client application project. This does a few things:

• A reference is added to Acute.dll, the assembly containing the Acute framework library.
• All System.* and Microsoft.* references are removed, and and are replaced with custom mscorlib.dll and System.Linq.dll references.
• The .csproj file is modified to use a custom targets file. This will cause building the project to invoke the Acute compiler, which will produce javascript output (in addition to the DLL as usual).
• acute.min.js is added to the project.

Note: After installing the NuGet package, you must re-load the project. This is unfortunate, but I suppose replacing mscorlib.dll isn't a normal scenario for a NuGet package.

Now, when you build your project, in your output directory there will be a {Your.Project.Name}.js file. You need to reference this and acute.min.js from your HTML file. You may want to set a post-build event on your ASP.NET project to copy these files into your web project directory.

See the walk-through for step-by-step details on creating an Acute application.