↔
Bidirectional interoperability
Events, context, routing, List Actions and Host services move between SharePoint Online and the .NET session through a controlled asynchronous protocol.
SharePoint Online + .NET, without rewrites
Bring your .NET applications into SharePoint Online.
GDG-SPFx-Bridge creates a controlled, secure, bidirectional interoperability channel between modern SharePoint pages and server-side .NET applications.
Wisej.NET 4.1.1
Single Sign-On SharePoint
Semantic routing
SharePoint Online / SPFxContext, ListView, Host services
.NET applicationUI, CRUD, routing, business logic
The product
Two worlds, one application experience
The .NET application is hosted by a Host Web Part and coordinated by the Bridge Web Part. SharePoint knows contracts and data; the .NET application decides how to interpret them.
.N
Native .NET development
Keep using C# or VB.NET, your application model and Visual Studio. You do not need to rewrite the consumer application in React/TypeScript.
UI
UI-level integration
Dialogs, notifications, navigation, layout and SharePoint actions can be orchestrated from .NET code through the Host API.
ID
SharePoint identity
The Bridge uses the current SharePoint identity and passes the token to the Wisej session without introducing a second login in the production flow.
≡
ListView and List Actions
New/Edit/View/Delete actions can generate application routes, carrying the selected item and typed values to the .NET router.
◎
Semantic routing
SPFx carries route names and data, not C# Pages, classes or methods. Routes can target all Hosts, one application, or a specific instance.
How it works
One Bridge Web Part coordinates one or more .NET Hosts
The modern page keeps the SPFx runtime in the browser while application logic remains server-side. The boundary is explicit, verifiable and designed to avoid fragile coupling.
✓
One Bridge singleton per pageManages SharePoint context, token, SPFx services, routing and cross-host distribution.
✓
One Host Web Part per applicationHosts the Wisej iframe and registers applicationId, instanceName and webPartInstanceId.
✓
Session-scoped .NET libraryThe consumer uses SharePointBridge.Current as the entry point for Context, REST, CSOM, HostApi, ListView, Routes and Diagnostics.
✓
Browser/SPFx protocol v3Based on window.postMessage, asynchronous and bidirectional, with Host RPC, correlationId, timeout and deduplication.
Security by design
The Bridge does not turn the browser into a remote .NET endpoint
The protocol exposes semantic contracts and data, not server-side classes or methods. Origin checks and fail-closed policies reduce the attack surface.
event.origin and event.source are verified; the SharePoint parent must match the exact origin.
Authorized Wisej origins are explicitly restricted. The protocol path that can carry tokens never uses targetOrigin="*".
The token stays in the Wisej session and must not be stored in localStorage, sessionStorage, databases, application cookies or logs.
SharePointRestClient restricts REST requests to the same origin as the current SharePoint Web.
Real-world example
SharePoint CRUD without coupling SPFx to .NET classes
The SPFXBridgeTest demo shows New, Edit, View and Delete operations on a SharePoint list. The action carries a route and the selected ID; the .NET router loads the appropriate Page, accesses data and uses native dialogs in the host page.
Flexible data access: CRUD operations can be implemented using CSOM, REST or through the provider ADO.NET GDG.SharePoint.ADOProvider.
1
List ActionNew/Edit/View/Delete with selection constraints and route values.
2
Application RoutingTarget All, Application or Instance with correlationId and ACK.
3
CSOM / REST / ADO.NETFor CRUD functions you can use CSOM, REST or the ADO.NET provider GDG.SharePoint.ADOProvider, choosing the data access model that best fits the application.
API .NET
A consistent, session-scoped API surface
Consumer code uses a single public entry point and accesses Bridge capabilities without needing to know the underlying SPFx runtime.
ContextWeb, user, list, appearance and Host snapshots.
REST server-sideSame-origin REST with token refresh and 401 retry.
CSOMClientContext authenticated with the current token.
HostApiNavigation, Dialogs, Notifications and Layout executed by SPFx.
Host HTTPSharePointApi, Microsoft Graph and CustomApi.
ListViewTyped state, LastAction and source capabilities.
RoutesSemantic local routing inside the .NET session.
ApplicationRoutingDispatch to one or more Hosts registered on the page.
DiagnosticsPoint-in-time snapshot without ever exposing the AccessToken.
“A .NET C# / VB.NET developer can integrate SharePoint functionality, UI and authentication while continuing to use the tools and environment they already know.”
Who it is for
For software companies and .NET teams that need deep SharePoint integration
Designed for teams that do not want to settle for a “silent” iframe and do not want to rewrite mature applications in React/TypeScript solely to achieve deep SharePoint Online integration.
Gradual modernization
Integrate existing .NET applications into SharePoint while preserving business logic, toolchain and team expertise.
Portals and line-of-business
Combine SharePoint lists, content and shell with server-side .NET UI and application processes.
Deep integrations
Orchestrate routing, dialogs, notifications, data and SharePoint services without relying on DOM automation or private APIs.
Roadmap beyond Wisej.NET
The protocol architecture is designed to be independent of the consumer ASP.NET framework; a .NET Blazor implementation is planned as a future evolution.
Want to evaluate GDG-SPFx-Bridge for your project?
For product, usage, licensing and distribution information, request a technical session or a demo based on your SharePoint Online scenario.