BlazorPolyfill.Server 6.0.100.1

.NET 6.0
There is a newer version of this package available.
See the version list below for details. 
dotnet add package BlazorPolyfill.Server --version 6.0.100.1
NuGet\Install-Package BlazorPolyfill.Server -Version 6.0.100.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="BlazorPolyfill.Server" Version="6.0.100.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add BlazorPolyfill.Server --version 6.0.100.1
#r "nuget: BlazorPolyfill.Server, 6.0.100.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install BlazorPolyfill.Server as a Cake Addin
#addin nuget:?package=BlazorPolyfill.Server&version=6.0.100.1

// Install BlazorPolyfill.Server as a Cake Tool
#tool nuget:?package=BlazorPolyfill.Server&version=6.0.100.1

6.0.100.1:

  • Added 'webRootPath' parameter on import javascript isolation emulation method. See the documentation for usage.

Documentation too big to be hosted on NuGet, read it on the the Blazor.Polyfill project page.

Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on BlazorPolyfill.Server:

Repository Stars
ant-design-blazor/ant-design-blazor
🌈A set of enterprise-class UI components based on Ant Design and Blazor WebAssembly.
Version Downloads Last updated
7.0.203.1 5,460 4/26/2023
7.0.203 561 4/24/2023
6.0.200 12,786 2/23/2022
6.0.100.3 3,043 12/4/2021
6.0.100.2 1,178 11/21/2021
6.0.100.1 17,091 11/13/2021
6.0.100 878 11/9/2021
5.0.102 26,800 2/1/2021
5.0.100.6 1,481 1/18/2021
5.0.100.5 984 1/5/2021
5.0.100.4 1,038 12/18/2020
5.0.100.2 1,019 12/8/2020
5.0.100.1 895 12/4/2020
5.0.0 1,078 12/2/2020

6.0.100.1:
- Added 'webRootPath' parameter on _import_ javascript isolation emulation method. See the documentation for usage.

6.0.100.0:
- Support for .NET 6.0.100

5.0.102.0:
- Added option to disable automatic React.NET registration, to give more control to advanced scenarios.
- Updated V8 and Native V8 dependencies to 7.1.0
- Added V8 native dependencies for ARM64 (Linux) and ARM64 (Windows)
- Added some conditional logics about the default JS engine used. Windows and OSX (all CPU type) and Linux (x64) uses ChakraCore. Linux (ARM64) use V8. Other platforms or failing scenarios should use the "UsePackagedBlazorServerLibrary" option instead.

5.0.100.6:
- Add configurable ES5 fallback option with a delegate validation
- Add Javascript isolation and dynamic import emulation - See the documentation

5.0.100.5:
- Fix dependencies error on Linux (Debian 10 default installation)
- Potentially fix Azure Web App error with the default Linux image container
- Added BlazorPolyfillOptions parameter for UseBlazorPolyfill methods in order to configure additional behaviors at startup
- Added the ForceES5Fallback option in order to force ES5 and Polyfill behaviors even if the browser is not Internet Explorer 11 or Edge Legacy.
- Added ChakraCore engine image and set it as default. V8 engine is still present as fallback engine.

5.0.100.4:
- Fix InputFile Razor component not working on IE11 and possibly some legacy Edge versions.

5.0.100.2:
- Fix possible application crash if request headers do not contains the User-Agent header or value

5.0.100.1:
- Add Edge Legacy (EdgeHTML engine) support
- Fix missing reconnection modal behavior on Internet Explorer 11 and Edge Legacy
- Add pre-caching of all files needed for this library at the first web app request, in order to prevent further requests to wait for file generation on the server before serving the app. This mean that, now, if the app page is shown, then everything is ready.

5.0.0:
- Add .NET 5.0 support