| Package | Version | Downloads |
|---|---|---|
WopiHost.Abstractions |
 |
 |
WopiHost.Core |
 |
 |
WopiHost.Discovery |
 |
 |
WopiHost.FileSystemProvider |
 |
 |
WopiHost.Url |
 |
 |
This project is a sample implementation of a WOPI host. Basically, it allows developers to integrate custom datasources with Office Online Server (formerly Office Web Apps) or any other WOPI client by implementing a bunch of interfaces.
- clean WebAPI built with ASP.NET Core MVC (no references to System.Web)
- uses new ASP.NET Core features (configuration, etc.)
- can be self-hosted or run under IIS
- file manipulation is extracted to own layer of abstraction (there is no dependency on System.IO)
- example implementation included (provider for Windows file system)
- file identifiers can be anything (doesn't have to correspond with the file's name in the file system)
- custom token authentication middleware
- DI used everywhere
- URL generator
- based on a WOPI discovery module
- all references are NuGets
- .NET 8 SDK or .NET 9 SDK
- Recommended: VS Code or Visual Studio 2022
The WopiHost app targets both net8.0 and net9.0.
If you need a version that's targeting an older version of .NET, check out the releases:
If you get errors saying that Microsoft.CobaltCore.*.nupkg can't be found, then just remove the reference or see the chapter Cobalt below.
See Samples for all samples.
Running the application only makes sense with a WOPI client as its counterpart. WopiHost is compatible with the following clients:
Note that WopiHost will always be compatible only with the latest version of OOS because Microsoft also supports only the latest version.
The deployment of OOS/OWA requires the server to be part of a domain. If your server is not part of any domain (e.g. you're running it in a VM sandbox) it can be overcome by promoting your machine to a Domain Controller.
To test your OWA server follow the instructions here.
To remove the OWA instance use Remove-OfficeWebAppsMachine.
You can use WopiHost to integrate with Microsoft 365 for the web which will require:
- onboarding - apply for CSPP
- extending the provided interfaces to support the required features by Microsoft; we provide a sample implementation of the interfaces that pass the interactive WOPI-Validator tests
- Test Microsoft 365 for the web integration
In the past (in Office Web Apps 2013), some HTTP actions required support of MS-FSSHTTP protocol (also known as "cobalt"). This is no longer true with Office Online Server 2016. However, if the WOPI client discovers (via SupportsCobalt property) that the WOPI host supports cobalt, it'll take advantage of it as it's more efficient.
If you need or want your project to use Cobalt, you'll need to create a NuGet package called Microsoft.CobaltCore.nupkg containing Microsoft.CobaltCore.dll. This DLL is part of Office Web Apps 2013 / Office Online Server 2016 and its license doesn't allow public distribution and therefore it's not part of this repository. Please always make sure your OWA/OOS server and user connecting to it have valid licenses before you start using it.
TODO
The IWopiStorageProvider interface is the main interface that needs to be implemented to provide access to the files. It's up to you how you implement it. One sample implementation is in the WopiHost.FileSystemProvider project.
The IWopiSecurityHandler interface is used to authenticate and authorize resource requests. One sample implementation is in the WopiHost.FileSystemProvider project.
The IWopiLockProvider interface is used to handle file locks. One sample implementation is in the WopiHost.MemoryLockProvider project.
The CheckFileInfo includes not only details about the file but also some additional properties that can be used by the WOPI client. You can either completely customize the response (by adding your own / missing properties), or update any properties before returning them by registering for the OnCheckFileInfo event.
The CheckContainerInfo includes also some security related properties (that are checked by IWopiSecurityHandler), but you can still customize the response using the OnCheckContainerInfo event.
TODO additional details
There is plenty of space for improvements in the overall architecture, implementation of the [MS-*] protocols or just finishing the TODOs in the code. Lot of refactoring still needs to be done and also the code style has to be unified. So please feel free to help me out with it :)
- Check out open issues
https://learn.microsoft.com/dotnet/standard/design-guidelines/
- LICENSE.txt - License for my part of the project
- ORIGINAL_WORK_LICENSE.txt - License for Marx Yu's part of the project. This project is based on Marx Yu's project.
- NOTICE.txt - additional notes to how the licenses are applied
- Official WOPI Documentation
- Official WOPI REST API Reference
- WOPI Host and url paths
- Office Online integration via WOPI Host by Richard diZerega + video
- SharePoint 2013: Building your own WOPI Client, part 1
- SharePoint 2013: Building your own WOPI Client, part 2
