<title>Visual F# Tools</title>

<title>F# Compiler, Core Library andVisual F# Tools</title>

<styletype="text/css">

<h1>F# Compiler + Library Open Contribution Repository</h1>

<h1>F# Compiler, Core Library and Visual F# Tools Open Contribution Repository</h1>

This repo is where you can contribute to the F# compiler.

This repo is where you can contribute to the F# compiler, core library and the Visual F# Tools.

To learn what F# is and why it&#39;s interesting, go to<ahref="http://fsharp.org">fsharp.org</a>.

To get a free F# environment, go to<ahref="http://fsharp.org/use/windows">fsharp.org</a>.

The compiler is compiled as a set of .NET 4.0 components using a bootstrap process.

<p>This uses the lkg compiler to build. Note that you need the .NET framework 3.5 installed on your machine in order to complete this step.</p>

This uses the lkg compiler to build. Note that you need the .NET framework 3.5 installed on your machine in order to complete this step.</p>

gacutil /i lkg\FSharp-2.0.50726.900\bin\FSharp.Core.dll

msbuild src/fsharp-proto-build.proj

<h3>2. Building an F# (Debug) library and compiler</h3>

<p>This uses the proto compiler to build FSharp.Core.dll,FSharp.Compiler.dll andfsc.exe.</p>

<p>This uses the proto compiler to build<code>FSharp.Core.dll</code><code>FSharp.Compiler.dll</code>,<code>fsc.exe</code> and<code>fsi.exe</code></p>

msbuild src/fsharp-library-build.proj

msbuild src/fsharp-compiler-build.proj

<p>You can now use the updated commpiler in<code>Debug\net40\bin\fsc.exe</code> to develop and test basic language and tool features.</p>

<p>You can now use the updated F# compiler in<code>Debug\net40\bin\fsc.exe</code> and F# Interactive in<code>Debug\net40\bin\fsi.exe</code> to develop and test basic language and tool features.<p>

<p><b>Note:</b> The updated library is not used until you run<code>update.cmd</code>, see below. The updated

compiler is not run 'pre-compiled' until you run<code>update.cmd -ngen</code>, see below.</p>

<h3>3. Full Steps Before Running Tests</h3>

<p>See<ahref="tests\TESTGUIDE.html">tests\TESTGUIDE.html</a> to run tests.</p>

<p>See<ahref="TESTGUIDE.html">TESTGUIDE.html</a> for instructions on how to run tests.</p>

<p>Prior to a<b>Debug</b> test run, you need to complete<b>all<b> of these steps:</p>

<p>Prior to a<b>Debug</b> test run, you need to complete<b>all</b> of these steps:</p>

msbuild src/fsharp-library-build.proj /p:Configuration=Debug

msbuild src/fsharp-compiler-build.proj /p:Configuration=Debug

src\update.cmd debug -ngen

tests\BuildTestTools.cmd Debug

<p>[Optional] Ifbuilding andtesting the Visual Studio bits (see below) you will also need:</p>

<p>[Optional] If testing the Visual Studio bits (see below) you will also need:</p>

msbuild vsintegration\fsharp-vsintegration-build.proj /p:Configuration=Debug

msbuild vsintegration\fsharp-vsintegration-unittests-build.proj /p:Configuration=Debug

<p>Prior to a<b>Release</b> test run, you need to do all of these:</p>

<p>Prior to a<b>Release</b> test run, you need to do<b>all</b> of these:</p>

msbuild src/fsharp-library-build.proj /p:Configuration=Release

msbuild src/fsharp-compiler-build.proj /p:Configuration=Release

src\update.cmd release -ngen

tests\BuildTestTools.cmd Release

<p>[Optional] Ifbuilding andtesting the VisualStudio bits (see below) you will also need:</p>

<p>[Optional] If testing the VisualF# IDE Tools (see below) you will also need:</p>

msbuild vsintegration\fsharp-vsintegration-build.proj /p:Configuration=Release

msbuild vsintegration\fsharp-vsintegration-unittests-build.proj /p:Configuration=Release

<h3>4. [Optional] Build and Install VisualStudio components</h3>

<h3>4. [Optional] Build and InstalltheVisualF# IDE Tools</h3>

To build the VS components:

cd ..\vsintegration

msbuild fsharp-vsintegration-build.proj

msbuild vsintegration\fsharp-vsintegration-build.proj

To install the VS components:

<li>Then:</li>

..\Debug\net40\bin\EnableOpenSource.vsix

Debug\net40\bin\EnableOpenSource.vsix

Now restart Visual Studio, now it should be running your freshly builtcomponents.

Now restart Visual Studio, now it should be running your freshly builtVisual F# IDE Tools.

<h3>Notes on the build</h3>

<p>Perl and NUnit should be included in the %PATH% to make execution easiest. It is also recommended that you run tests from an elevated command prompt, as there are a couple of test cases which modify the GAC, and this requires administrative privileges.

<p>Before running tests, make sure you have successfully built all required projects as specified in the 'Prepare For Tests' section of the<ahref="../DEVGUIDE.html">DEVGUIDE</a>.

<p>Before running tests, make sure you have successfully built all required projects as specified in the 'Prepare For Tests' section of the<ahref="DEVGUIDE.html">DEVGUIDE</a>.

Don't forget to build and install the Visual Studio components as well if you want to run the IDE tests below.

<p><h3>Running Tests</h3>

<h3>Running Tests</h3>

<p>The script<code>tests\RunTests.cmd</code> has been provided to make execution of the above suites very simple. You can kick off a full test run of any of the above suites like this:

<pNote:<b>Don't</b> run tests from a Visual Studio developer command prompt.</b> (see below)</p>

<p>The script<code>tests\RunTests.cmd</code> has been provided to make execution of the above suites simple. You can kick off a full test run of any of the above suites like this:

RunTests.cmd &lt;debug|release&gt; fsharp [tags to run] [tags not to run]

RunTests.cmd &lt;debug|release&gt; fsharpqa [tags to run] [tags not to run]