Quantcast
Channel: ASP.NET MVC / Web API / Web Pages
Viewing all articles
Browse latest Browse all 7925

Updated Wiki: Building from Source

$
0
0

Building from Source

If you are contributing code or you want to build from source then building from source is what you will want to do. Follow the steps below:

  1. To build our sources, you must be running either Windows 8 or Windows Server 2012. You will also need to install Visual Studio 2012.
  2. Make sure you have git installed*. In addition, you may want to install one of the git helpers:
    • TortoiseGit is highly recommended, because it offers graphical log/tree views and diff/merge experience.
    • Posh-Git is highly recommended for PowerShell users.
    • Git Source Control Provider is an optional component that integrates git into Visual Studio.
  3. Using your preferred git client clone our git repo located at
    git clone https://git01.codeplex.com/aspnetwebstack.git
  4. Download SkipStrongNames, and unzip it. From an elevated command prompt, run “skipstrongnames -e” to allow you to run unit tests against the delay-signed binaries.
  5. To build and run the tests from a command prompt, run build.cmd (found in the root directory). Note: As part of building you may need to obtain NuGet packages from the Outercurve Foundation NuGet public feed**.
    build

    For Visual Studio, there are two solution files in the root of the repository: Runtime.sln and Extensions.sln. The Runtime solution contains the runtime assemblies which were shipped as part of the MVC and Web API release. The Extensions solution contains extension projects which target the released MVC and Web API RTM (v4) and build upon them to provide additional features. The Runtime and Extensions solutions build into two separate directories. Extensions are being refreshed as part of the Fall 2012 update; see the roadmap for additional information.

    The Extensions solution references Runtime binaries from the shipped (RTM) version, not from the latest Runtime source. If you want to reference the Extensions assemblies, you will need to use the matching RTM version of the Runtime assemblies, as provided by the public NuGet package. Note that the version of any Runtime assemblies in the Extensions folder is the RTM version, and not the latest version built from source.

* When installing git, you may be asked how to configure line ending conversions; choose the option appropriate for your plaftorm. For cross-platform compatibility, all our commited text files use LF as the line ending. Choose the line ending conversion option that 1) does any necessary conversion to your platform’s line ending on checkout and 2) converts from CRLF to LF on commit.

** By running build, you will be initiating the download of other software packages from a NuGet-based feed that is owned by the Outercurve Foundation. You are responsible for locating, reading and complying with the license terms that accompany each such package. Each package is licensed to you by its owner. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.


Viewing all articles
Browse latest Browse all 7925

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>