Releases: dotnet-websharper/core
WebSharper 4.6.5
This is a minor release for WebSharper 4.6.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.6.5.374
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.6.5.374.vsix
This release updates to a new version of FSharp.Compiler.Service. For optimal compilation speed, run the packages\WebSharper.FSharp.4.6.5.406\tools\runngen.ps1
script in administrator mode once.
Fixes
- #1105 Do not write BOM (UTF-8 byte order mark) for
Content.Text
. Thanks to @panesofglass and @Tarmil.
Improvements
- #1104 Optimize partial tail recursion for F#. When a recursive call is not always in tail position, still optimize for if any tail calls are used.
WebSharper 4.6.4
This is a dependency update release for WebSharper 4.6.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.6.4.373
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.6.4.373.vsix
Fixes
- #1103 Fix code support for WebSharper projects in Visual Studio Code by turning compiler switch and extra flags off for design-time builds.
Enhancements
- #1102 Using
<NoWarn>$(NoWarn);9002</NoWarn>
on a project now hides all warnings by WebSharper.
Breaking changes
- #1055 updated .NET Core compilers to run on netcoreapp3.1. A netcoreapp3.1 runtime installed is needed instead of netcoreapp2.0.
WebSharper 4.6.3
This is a bugfix release for WebSharper 4.6.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.6.3.368
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.6.3.368.vsix
Fixes
- #1101 Fix adding extra parameters to
RemotingProvider
attribute.
WebSharper 4.6.2
This is a minor release for WebSharper 4.6.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.6.2.367
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.6.2.367.vsix
This release updates to a new version of FSharp.Compiler.Service. For optimal compilation speed, run the packages\WebSharper.FSharp.4.6.2.386\tools\runngen.ps1
script in administrator mode once.
Fixes
- #1094 Behavior of
Map
constructor with sequence parameter matches .NET, keeping last value for keys in multiples. - #1098 Fixed translation bug for tupled lambda functions using
as
alias on parameter.
Improvements
- #1097 WebSharper-generated resource/script links can be removed, by having setting in
web.config
/.NET Core configuration with the name of the resource type and empty string value. - #1095 QuotationCompiler now recognizes all attributes. This will enable updating WebSharper.Warp to WebSharper 4 and other use cases of dynamic translation from F# interactive.
- Updated to FSharp.Compiler.Service 35.0.
WebSharper 4.6.1
This is a minor release for WebSharper 4.6.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.6.1.363
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.6.1.363.vsix
This release updates to a new version of FSharp.Compiler.Service. For optimal compilation speed, run the packages\WebSharper.FSharp.4.6.1.381\tools\runngen.ps1
script in administrator mode once.
Fixes
- #1091 Fixed an F# compilation error that happened whenever an F# expression that is translated to a JavaScript statement (for example
try ... with
was used within a single element array construction. - #1092 Fixed C# MSBuild errors around
WebSharper.MSBuild.CSharp.WebSharperTask
.
Improvements
- Updated to FSharp.Compiler.Service 34.1.0.
WebSharper 4.6
This is a major release for WebSharper 4. See the associated WebSharper UI release.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.6.0.357
Templates for Visual Studio 2017: http://websharper.com/installers/WebSharper.4.6.0.357.vsix
This release updates to a new version of FSharp.Compiler.Service. For optimal compilation speed, run the packages\WebSharper.FSharp.4.6.0.361\tools\runngen.ps1
script in administrator mode once.
Features
- #1067 Added the
Proxy
project type (experimental feature). Having"project"="proxy"
inwsconfig.json
makes the produced dll to contain no IL code, but have full WebSharper translation and metadata. With the use of multiple project files or msbuild conditionals, this allows building a dll from the original source code (or with slight modifications only) that can be used in parallel with the original .NET-facing library to add WebSharper cliens-side support for it. Also set"proxyTargetName"="OriginalAssemblyName"
. Examples upcoming. - #1069 Added
SingleNoJSErrors
compiler setting. Having"singleNoJSErrors"=true
inwsconfig.json
makes the WebSharper compiler report only the first occurrence of every type/method that is unsupported for the client side. - #1075 Added
UseJavaScriptSymbol
compiler setting. Having"useJavaScriptSymbol"=true
inwsconfig.json
makes the WebSharper compiler to include theJAVASCRIPT
conditional compilation symbol when making a pass for parsing the project for client-side use. Using#if JAVASCRIPT
is a top-level way of differentiating server-side and client-side code where needed, available in both F# and C#. This is added as an opt-in feature, because re-parsing takes some time, there should be no compile time regressions on existing projects. - #1084
wsconfig.json
location (including file name) is now configurable via theWebSharperConfigFile
project file property. Also, if not set,wsconfig.ProjectName.json
is checked first. - #1082 Strong naming works when building on .NET Core
- #576 Client-side support for collection interfaces
- #1073 Client-side support for
Microsoft.FSharp.Core.OptimizedClosures.FSharpFunc
- #1071 More client-side support for
Microsoft.FSharp.Core.LanguagePrimitives
/Operators
- #1073 Client-side support for
System.Collections.Generic.KeyNotFoundException
,System.Threading.Interlocked
- dotnet-websharper/templates#14 .NET Core/Standard templates available for Visual Studio
- dotnet-websharper/templates#23 Extension template available for .NET Standard
- Updated to
FSharp.Compiler.Service
version33.0.1
.
Fixes
WebSharper 4.5.19
This is a minor release for WebSharper 4.5.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.5.19.332
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.5.19.332.vsix
This release updates to a new version of FSharp.Compiler.Service. For optimal compilation speed, run the packages\WebSharper.FSharp.4.5.19.349\tools\runngen.ps1
script in administrator mode once.
Improvements
- #1064 Full support for FSharp.Core 4.7.0 new functions.
- Updated to FSharp.Compiler.Service 32.0.0, this includes syntax changes coming with F# 4.7, most notably implicit yields in sequence/list/array expressions.
WebSharper 4.5.18
This is a minor release for WebSharper 4.5.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.5.18.328
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.5.18.328.vsix
Improvements
- #1061 Remoting context is now using AsyncLocal. You can now call
WebSharper.Web.Remoting.GetContext()
from inside an F# async workflow or C# async method, you do not have to make sure it runs synchronously on the same thread. This is a non-breaking change that eliminates a common annoyance. - #1038 Improve error messages on F# type compilation failures
- #1058 Add a warning if an RPC is returning type without full client support
WebSharper 4.5.17
This release has an issue, unnecessary warnings are produced on every RPC call for FSharpAsync
. Use 4.5.18.348 instead.
WebSharper 4.5.16
This is a minor release for WebSharper 4.5.
Templates for .NET Core SDK: dotnet new -i WebSharper.Templates::4.5.16.325
Templates for Visual Studio 2017/2019: http://websharper.com/installers/WebSharper.4.5.16.325.vsix
This release updates to a new version of FSharp.Compiler.Service. For optimal compilation speed, run the packages\WebSharper.FSharp.4.5.16.344\tools\runngen.ps1
script in administrator mode once.
Improvements
- #1060 Updated to FSharp.Compiler.Service 31.0.0.
- Updated compiler to FSharp.Core 4.7.0. Base libraries still depend only on FSharp.Core 4.2.3.