PeakSWC.RemoteBlazorWebView.Wpf 6.0.25-rc1

This is a prerelease version of PeakSWC.RemoteBlazorWebView.Wpf.
There is a newer version of this package available.
See the version list below for details.
dotnet add package PeakSWC.RemoteBlazorWebView.Wpf --version 6.0.25-rc1
                    
NuGet\Install-Package PeakSWC.RemoteBlazorWebView.Wpf -Version 6.0.25-rc1
                    
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="PeakSWC.RemoteBlazorWebView.Wpf" Version="6.0.25-rc1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="PeakSWC.RemoteBlazorWebView.Wpf" Version="6.0.25-rc1" />
                    
Directory.Packages.props
<PackageReference Include="PeakSWC.RemoteBlazorWebView.Wpf" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add PeakSWC.RemoteBlazorWebView.Wpf --version 6.0.25-rc1
                    
#r "nuget: PeakSWC.RemoteBlazorWebView.Wpf, 6.0.25-rc1"
                    
#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.
#:package PeakSWC.RemoteBlazorWebView.Wpf@6.0.25-rc1
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=PeakSWC.RemoteBlazorWebView.Wpf&version=6.0.25-rc1&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=PeakSWC.RemoteBlazorWebView.Wpf&version=6.0.25-rc1&prerelease
                    
Install as a Cake Tool

RemoteBlazorWebViewTutorial

Microsoft has recently introduced two Blazor WebView Controls in .NET 6 Preview 3. One Blazor WebView control (Microsoft.AspNetCore.Components.WebView.Wpf) targets Windows Presentation Foundation (WPF) apps and the other (Microsoft.AspNetCore.Components.WebView.WindowsForms) targets Windows Form (WinForms) apps. The Microsoft controls allow developers to create user interfaces for desktop apps using Blazor web technology. The desktop apps using Blazor have the full feature set and performance of .NET 6 and are not contrained like a Blazor WebAssembly app.

The Remote versions of the Blazor WebView Controls (PeakSWC.RemoteBlazorWebView.Wpf and PeakSWC.RemoteBlazorWebView.WindowsForms) act as a drop-in replacement for the Microsoft controls along with the ability to share the user interface over a secure connection to a public server using a web browser. This is accomplished by setting up a secure server (RemoteWebWindowService) in the cloud and pointing your browser to it. With a couple of minimal changes you will be able to either run your app locally or remotely control your application.

Use Cases

The primary use case is to be able to share a desktop application controlling hardware with an external service technician. Typically, the application is behind a corporate firewall and is not easily accessed by the technician. The Remote Blazor controls allow the desktop application to be started in "Remote" mode which generates a unique Url for the technician to access the user interface.

Another use case is to be able to monitor data that is behind a firewall or on a private network without the cost and complexity to store the data externally. For example, if a brewer wanted to monitor fermentation data such as PH, Gravity, and Pressure they could build an app showing real-time graphical data using Blazor components and, with only a couple of changes, be able to view the user interface with a web browser from outside of the firewall.

How it works

RemoteBlazorWebView.Wpf has two modes of operation. In the first default mode, it works just like the Microsoft BlazorWebView Controls (see BlazorDesktopWPF). In the second mode, a url is specified on the control's properties. In this mode, all GUI interactions are sent to a server which can be accessed with a browser. Hosting the server (RemotableWebViewService.exe) in the cloud allows you to remotely control an application which is behind a firewall or does not have a static IP address.

Demo Quick Start

*** Note the name change to RemoteWebViewService

Install the RemoteWebViewService

dotnet tool update -g PeakSWC.RemoteWebViewService --version 6.*-* 

Start the server

RemoteWebViewService

Open the RemoteBlazorWebViewTutorial.sln with Visual Studio

Run the Local Profile using the Run button

Make sure the RemoteBlazorWebViewTutorial.WppfApp is set as Startup Project

Next we will run the application remotely

Run the Remote Profile using the Run button

A main window will come up with a URL. Click on it

At this point the sample blazor app will be running in a web browser!

Product Compatible and additional computed target framework versions.
.NET net6.0-windows7.0 is compatible.  net7.0-windows was computed.  net8.0-windows was computed.  net9.0-windows was computed.  net10.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

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.0.0-preview5 116 6/14/2025
10.0.0-preview4 223 5/14/2025
10.0.0-preview3 75 4/12/2025
9.0.6 134 6/15/2025
9.0.5 472 5/14/2025
9.0.4 140 4/12/2025
9.0.2 169 2/16/2025
9.0.1 124 1/18/2025
9.0.0 148 11/14/2024
9.0.0-rc2 79 10/26/2024
9.0.0-preview7 250 8/19/2024
9.0.0-preview6 68 7/29/2024
9.0.0-preview5 94 6/23/2024
8.0.11 136 11/14/2024
8.0.10 1,402 10/10/2024
8.0.8 286 8/20/2024
8.0.7 138 7/29/2024
8.0.6 262 6/19/2024
8.0.4 169 6/19/2024
8.0.3 169 4/20/2024
8.0.2 659 2/23/2024
8.0.1 164 2/16/2024
8.0.0 224 12/30/2023
8.0.0-rc2 100 10/14/2023
8.0.0-preview5 137 6/15/2023
8.0.0-preview4 134 5/24/2023
8.0.0-preview3 144 4/21/2023
8.0.0-preview2 145 3/29/2023
7.0.16 174 2/25/2024
7.0.14 196 12/29/2023
7.0.12 291 10/14/2023
7.0.9 221 8/15/2023
7.0.7 258 6/14/2023
7.0.5 1,869 4/20/2023
7.0.4 386 3/24/2023
7.0.3 272 3/17/2023
7.0.2 369 1/29/2023
7.0.0 457 11/13/2022
7.0.0-rc1 168 10/9/2022
7.0.0-pre6 249 7/14/2022
7.0.0-pre5 256 7/2/2022
7.0.0-pre4 201 5/11/2022
6.3.9 736 2/11/2023
6.3.8 349 2/1/2023
6.3.7 344 1/31/2023
6.3.6 456 11/13/2022
6.3.5 487 10/11/2022
6.3.4 1,348 7/13/2022
6.3.3 700 7/3/2022
6.3.2 509 6/15/2022
6.3.1 729 5/25/2022
6.3.0 236 5/21/2022
6.2.0 260 5/8/2022
6.1.2-pre 202 4/7/2022
6.1.1-pre 539 2/19/2022
6.1.0-pre 274 2/7/2022
6.0.38-pre 232 2/1/2022
6.0.37-pre 250 1/25/2022
6.0.36 306 1/4/2022
6.0.35 250 1/1/2022
6.0.34 227 12/30/2021
6.0.33 219 12/29/2021
6.0.32 301 12/12/2021
6.0.31 316 12/4/2021
6.0.30 829 12/3/2021
6.0.29 303 11/17/2021
6.0.28-rc2 280 10/14/2021
6.0.27-rc1 252 10/11/2021
6.0.26-rc1 208 10/7/2021
6.0.25-rc1 264 10/4/2021
6.0.24-rc1 294 10/1/2021
6.0.23-rc1 267 9/26/2021
6.0.22-rc1 242 9/15/2021
6.0.21-preview7 262 9/7/2021
6.0.20-preview7 238 8/26/2021
6.0.16-preview7 210 8/25/2021
6.0.15-preview7 235 8/13/2021
6.0.13-preview6 217 8/9/2021
6.0.12-preview6 286 8/1/2021
6.0.11-preview6 205 7/16/2021
6.0.10-preview5 338 7/10/2021
6.0.9-preview5 303 6/29/2021
6.0.8-preview5 296 6/22/2021
6.0.7-preview4 221 6/17/2021
6.0.6-preview4 228 6/1/2021
6.0.5-preview4 257 5/28/2021
6.0.4-preview4 256 5/28/2021
6.0.3-preview4 242 5/26/2021
6.0.2-preview3 216 5/26/2021
6.0.1-preview3 230 5/22/2021
0.1.7-pre 310 5/25/2021
0.1.6-pre 315 2/21/2021
0.1.4-pre 450 11/1/2020

Enhanced error message reporting