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
Anonymous record support for expressions in FCS (#6257)
* fix flakey test (?)
* use runsettings
* same fix for FCS tests2
* anonymous record support for expressions in FCS
* anonymous record support for expressions in FCS
* add tests for anonymous records and fix service testing with F# interactive
* fix FCS docs
* fix build
* add diagnostics
* update other baseline
* fix final parallel case
* try again to fix test
* update test fixes
Copy file name to clipboardExpand all lines: fcs/docsrc/content/corelib.fsx
+4-22Lines changed: 4 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
(*** hide ***)
2
-
#I "../../bin/v4.5/"
2
+
#I "../../../artifacts/bin/fcs/net45"
3
3
(**
4
4
Compiler Services: Notes on FSharp.Core.dll
5
5
=================================================
@@ -13,14 +13,11 @@ include a copy of FSharp.Core.dll as part of your application.
13
13
For example, if you build a ``HostedCompiler.exe``, you will normally place an FSharp.Core.dll (say 4.3.1.0) alongside
14
14
your ``HostedCompiler.exe``.
15
15
16
-
If doing dynamic compilation and execution you may also need to include
17
-
an FSharp.Core.optdata and FSharp.Core.sigdata, see below for guidance.
18
-
19
16
Binding redirects for your application
20
17
--------------------------------------
21
18
22
19
The FSharp.Compiler.Service.dll component depends on FSharp.Core 4.4.0.0. Normally your application will target
23
-
a later version of FSharp.Core, and you will need a [binding redirect](http://msdn.microsoft.com/en-us/library/7wd6ex19(v=vs.110).aspx) to ensure
20
+
a later version of FSharp.Core, and you may need a [binding redirect](http://msdn.microsoft.com/en-us/library/7wd6ex19(v=vs.110).aspx) to ensure
24
21
that other versions of FSharp.Core forward to the final version of FSharp.Core.dll your application uses.
25
22
Binding redirect files are normally generated automatically by build tools. If not, you can use one like this
26
23
(if your tool is called ``HostedCompiler.exe``, the binding redirect file is called ``HostedCompiler.exe.config``)
@@ -80,27 +77,12 @@ by the following choice:
80
77
81
78
2. If there is no static reference to FSharp.Core in the host assembly, then
82
79
83
-
- For FSharp.Compiler.Service 0.x series, a reference to FSharp.Core version 4.3.0.0 is added
84
-
85
-
- For FSharp.Compiler.Service 1.3.1.x (F# 3.1 series), a reference to FSharp.Core version 4.3.1.0 is added
86
-
87
-
- For FSharp.Compiler.Service 1.4.0.x (F# 4.0 series), a reference to FSharp.Core version 4.4.0.0 is added
80
+
- For FSharp.Compiler.Service 1.4.0.x above (F# 4.0 series), a reference to FSharp.Core version 4.4.0.0 is added
88
81
89
82
Do I need to include FSharp.Core.optdata and FSharp.Core.sigdata?
90
83
--------------------------------------
91
84
92
-
If your compilation arguments explicitly reference an FSharp.Core.dll from an SDK location, then FSharp.Core.sigdata and FSharp.Core.optdata should be alongside the DLL
93
-
(if these files are not installed, then that's a bug in the F# SDK installation). If your compilation
94
-
arguments are always making an explicit reference, then you should _not_ include FSharp.Core.optdata and FSharp.Core.sigdata as part of your application.
95
-
96
-
If you are relying on an implicit reference (e.g. for script processing, see above), this means your tool may reference the FSharp.Core.dll
97
-
that is part of your application. In this case, you may either get an error that FSharp.Core.optdata and FSharp.Core.sigdata are not
98
-
found alongside FSharp.Core.dll. **If you want to implicitly reference the FSharp.Core.dll you are including in your application,
99
-
then also add FSharp.Core.sigdata and FSharp.Core.optdata as two additional files to your application**. When using ``CompileToDynamicAssembly``, this problem
100
-
can also manifest itself as [a stack overflow during assembly resolution](https://github.com/fsharp/FSharp.Compiler.Service/issues/258).
101
-
102
-
Tools that dynamically compile and execute code (e.g. a ``HostedExecution.exe``) often make an implicit
103
-
reference to FSharp.Core.dll, which means they normally also include FSharp.Core.optdata and FSharp.Core.sigdata.
85
+
No, unless you are doing something with very old FSharp.Core.dll.
0 commit comments