You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
This uses the proto compiler to build`FSharp.Core.dll`,`FSharp.Compiler.dll`,`fsc.exe`, and`fsi.exe`.
28
35
29
-
```
30
-
msbuild src/fsharp-library-build.proj
31
-
msbuild src/fsharp-compiler-build.proj
32
-
```
36
+
msbuild src/fsharp-library-build.proj
37
+
msbuild src/fsharp-compiler-build.proj
33
38
34
39
You can now use the updated F# compiler in`debug\net40\bin\fsc.exe` and F# Interactive in`debug\net40\bin\fsi.exe` to develop and test basic language and tool features.
35
40
@@ -41,75 +46,81 @@ See [TESTGUIDE.md](TESTGUIDE.md) for full details on how to run tests.
41
46
42
47
Prior to a**Debug** test run, you need to complete**all** of these steps:
##4.[Optional] Install the Visual F# IDE Tools and Clobber the F# 4.0 SDK on the machine
98
+
99
+
NOTE: Step#2 will install a VSIX extension into Visual Studio 2015 that changes the Visual F# IDE Tools
100
+
components installed into Visual Studio 2015. You can revert this step by disabling or uninstalling the addin.
101
+
102
+
NOTE: Step#3 will clobber the machine-wide installed F# 4.0 SDK on your machine. This replaces the``fsi.exe``/``fsiAnyCpu.exe`` used
103
+
by Visual F# Interactive and the fsc.exe used by Microsoft.FSharp.targets. Repairing Visual Studio 2015 is currently the
104
+
only way to revert this step.
105
+
106
+
NOTE: After you complete the install, the FSharp.Core referenced by your projects will not be updated. If you want to make
107
+
a project that references your updated FSharp.Core, you must explicitly change the``TargetFSharpCoreVersion`` in the .fsproj
108
+
file to``4.4.0.5099`` (or a corresponding portable version number with suffix``5099``).
109
+
110
+
For debug:
97
111
98
-
##4.[Optional] Build and Install the Visual F# IDE Tools
112
+
1. Ensure that the VSIX package is uninstalled. In VS, select Tools/Extensions and Updates and if the package`VisualStudio.FSharp.EnableOpenSource` is installed, select Uninstall
113
+
1. Run``debug\net40\bin\EnableOpenSource.vsix``
114
+
1. Run``vsintegration\update-vsintegration.cmd debug`` (clobbers the installed F# 4.0 SDK)
1. Ensure that the VSIX package is uninstalled. In VS, select Tools/Extensions and Updates and if the package`VisualStudio.FSharp.EnableOpenSource` is installed, select Uninstall
119
+
1. Run``release\net40\bin\EnableOpenSource.vsix``
120
+
1. Run``vsintegration\update-vsintegration.cmd release`` (clobbers the installed F# 4.0 SDK)
105
121
106
-
To install the VS components:
122
+
Restart Visual Studio, it should now be running your freshly-built Visual F# IDE Tools with updated F# Interactive.
107
123
108
-
1. Ensure that the VSIX package is uninstalled.
109
-
- In VS, select Tools/Extensions and Updates
110
-
- If the package`VisualStudio.FSharp.EnableOpenSource` is installed, select Uninstall
111
-
1. Run```debug\net40\bin\EnableOpenSource.vsix```
112
-
1. Restart Visual Studio, it should now be running your freshly-built Visual F# IDE Tools.
@@ -39,4 +40,4 @@ Although the primary focus of this repo is F# for Windows and the Visual Studio
39
40
40
41
###Get In Touch
41
42
42
-
Keep up with the Visual F# Team and the development of the Visual F# Tools by following us[@VisualFSharp](https://twitter.com/VisualFSharp) or subscribing to our[team blog](http://blogs.msdn.com/b/fsharpteam/).
43
+
Keep up with the Visual F# Team and the development of the Visual F# Tools by following us[@VisualFSharp](https://twitter.com/VisualFSharp) or subscribing to our[team blog](http://blogs.msdn.com/b/fsharpteam/).
Copy file name to clipboardExpand all lines: TESTGUIDE.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,8 @@ The test cases for this suite reside next to the Visual F# Tools code, at `vsint
22
22
In order to run all of the tests, you will need to install
23
23
24
24
*[Perl](http://www.perl.org/get.html) (ActiveState Perl 5.16.3 is known to work fine)
25
-
*[NUnit](http://nunit.org/?p=download) (2.6.3 is known to work fine)
26
25
27
-
Perland NUnitmust be included in the`%PATH%` for the below steps to work. 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.
26
+
Perl must be included in the`%PATH%` for the below steps to work. 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.
28
27
29
28
Before running tests, make sure you have successfully built all required projects as specified in the 'Prepare For Tests' section of the[DEVGUIDE](DEVGUIDE.md).