Releases: dotnet/netcorecli-fsc
v1.0.5
Bugfix for VisualStudio for Mac debugging
use FSharp.Compiler.Tools
v4.1.17 who contains fix for https://bugzilla.xamarin.com/show_bug.cgi?id=55092
v1.0.4
Bugfix and work for VS 2017 roslyn project system
Added a new package version 1.0.4-bundled-0100 who contains the bits (the Sdk
directory) who should be embedded in sdk bundles, like the .net core sdk (dotnet/cli
) and VS (and mono soon)
v1.0.3
Now the fsproj works with all three the msbuild host runtimes (.net core, .net framework, mono >= 5.0)
Example:
- .net core
dotnet restore
,dotnet build
(as note,dotnet build
=dotnet msbuild /t:Build
) - .net fw
msbuild.exe /t:Restore
,msbuild.exe /t:Build
- mono
msbuild /t:Restore
,msbuild /t:Build
Also fsc
used will depends on msbuild host runtimes, so:
- .net core
fsc.dll
(netcoreapp1.0
) - .net fw
fsc.exe
(net40
) - mono
mono fsc.exe
(net40
)
NOTE fsc
used is inside FSharp.Compiler.Tools
nuget package
bump to FSharp.Compiler.Tools
4.1.15
NOTE msbuild.exe (VS2017) need a workaround, more info in dotnet/fsharp#2928
NOTE mono 5.0 Alpha 3 (5.0.0.61) need a workaround, more info in mono bug #55626
v1.0.2
Updated to use FSharp.Compiler.Tools
v4.1.1
Enable VSCode intellisense/debugging with Ionide 2.25.1
New msbuild Fsc
task properties can be used:
SkipCompilerExecution
: to skip compilationProvideCommandLineArgs
: if true,FscCommandLineArgs
will be setFscCommandLineArgs
: the fsc arguments list
v1.0.1
Tested with .NET Core Sdk 1.0.0-rc4-004771
Minor bugs fixed:
- Embedded resources (like resx) now works
- The target framework define is implicit generated. So for
netstandard1.6
theNETSTANDARD1_6
define is passed to compiler. see #83 for more info (and how to disable it)
See closed issues in milestone
Thanks to @neoeinstein that helped make this release
v1.0.0
Tested with .NET Core Sdk 1.0.0-rc4-004771
The dotnet-compile-fsc
tool is not needed anymore. No more project.json legacy.
The FscTask
from FSharp.Compiler.Tools
package is used to invoke fsc.
The fsc
is from FSharp.Compiler.Tools
4.1.0 package.
See closed issues in milestone
Example projects in examples/rc4
VSCode/ionide doesnt support 1.0.0
yet. Use previous FSharp.NET.Sdk 1.0.0-beta-060000
plus dotnet-compile-fsc
until support is implemented, if you require ide intellisense.
v1.0.0-beta-060000
All closed issues
- add
FSharp.Sdk
package, extracted fromFSharp.NET.Sdk
- packages are compatibile with sdk
preview4
,rc3
,rc4
Fix vscode/ionide Intellisense
Fixed vscode/ionide intellisense.
Intellisense works if vscode is opened after the first dotnet build
. Like preview2
So using .NET Core Sdk preview4
:
dotnet new -l fsharp
dotnet restore
dotnet build
code .
Current preview4
projects need to redo dotnet restore
to use new Fsharp.NET.Sdk
package (in fsproj the version should be 1.0.0-beta-*
)
Support .NET Core Sdk preview2.1 and .NET Core 1.1
Support .NET Core 1.1 with .NET Core Sdk 1.0.0-preview2.1
Support for preview4 Sdk attribute
the FSharp.NET.Sdk
package 1.0.0-beta-*
it's to be used with Sdk
attribute of fsproj
added to .NET Core Sdk 1.0.0-preview4