Office Addin Sideloader
A handy tool to manage your office addins locally, you can use it for addin development or deploy your addins for your clients out of AppSource.
NOTE: currently only support windows.
Features
- Add or remove Office Add-in locally.
- Support local or url manifest source.
- Debug sideload status and list manifest info.
- Single binary without any dependency.
- Use it as a library.
- Generate add-in installer/uninstaller with sentry support by single command.
- Support fixing add-in APP ERROR and clearing cache.
Installation
Pre-built releases
If you just use the command line and don't have a python environment, download pre-built binary from GitHub Releases.
Pypi
> pip install oaloader
Quick Start
> ./oaloader.exe --help
Usage: [OPTIONS] COMMAND [ARGS]...
Manage your office addins locally.
Options:
--version Show the version and exit.
-l, --level TEXT The log level [default: info]
--help Show this message and exit.
Commands:
add Register catalog and add manifests, manifests can be file paths
or...
fix Try fixing `APP ERROR` when starting up add-ins.
info Debug sideload status.
remove Remove manifest from catalog and manifest can be a file path or...
Build an Addin installer
- Install Poetry.
- Run
poetry installto prepare environment. - Checkout Nuitka Requirements and install a C compiler.
- Run
poetry run invoke installer -m <YOUR-ADDIN-MANIFEST-URL>to build your own installer.
If your want customize the installer, just edit installer.jinja2 or write your own installer with oaloader module.
Build an Addin uninstaller
Just using invoke uninstaller task like installer above.
FAQ
How it works?
Get error like ImportError: DLL load failed while importing win32xxx when import pywin32 module.
Try this solution:
- Open a terminal as Administrator
- Get your virtualenv path by running
poetry env info - Run
poetry run python <virtualenv path>/.venv/Scripts/pywin32_postinstall.py -install
see https://github.com/mhammond/pywin32/issues/1431#issuecomment-548584385 for more details.
Metadata
Release files for oaloader 0.4.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| oaloader-0.4.4.tar.gz | 8.9 kB | Without provenance | Details for oaloader-0.4.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| oaloader-0.4.4-py3-none-any.whl | Python 3 | none | any | Details for oaloader-0.4.4-py3-none-any.whl |
Total release size: 18.7 kB
Release files / oaloader-0.4.4.tar.gz
| Download URL | oaloader-0.4.4.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c374458a3b1242bd9952a30a1e38fe88ce4601f45f626d56b33749f44150e3d8
|
|
BLAKE2b-256 checksum How to use checksums |
25fe6d267140e4d98fe42e44b0634a0bee907af50eb501680cd9e3d006989366
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.9 CPython/3.8.11 Windows/10
|
Release files / oaloader-0.4.4-py3-none-any.whl
| Download URL | oaloader-0.4.4-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3f498893472e9c6db493a499eb9c3a6ed504fcf50b838679da78b28b20ad969
|
|
BLAKE2b-256 checksum How to use checksums |
3cab515be5bf9abaa5efee3e23faa08ad59ab11d12f01f2ae286bb1ce3bd20c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.9 CPython/3.8.11 Windows/10
|
Security for oaloader 0.4.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.