microsoft / microsoft/winget-pkgs
[Package Request]: Microsoft 365 Access Runtime
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 616
Description
### How can we help?
I would like someone else to build the manifest.
### Please read and ensure the following
- [x] The installer meets the above requirements
### Please provide the following information
Download Page Url: https://support.microsoft.com/en-us/Access/download-and-install-microsoft-365-access-runtime *(de facto)*
Publisher: Microsoft
Package Name: Microsoft 365 Access Runtime
Description: Enables distributing Access 365 applications to users who don't have Microsoft Office installed on their computers or a version of Microsoft Office that doesn’t include Access.
Package Version: 16.0.20228.20124 (at the time of writing)
Installer Url: Most likely https://download.microsoft.com/download/6c1eeb25-cf8b-41d9-8d0d-cc1dbc032140/officedeploymenttool_20131-20090.exe
### Technical details:
The app is claimed by Team Microsoft Office to be the successor to `Microsoft.AccessDatabaseEngine.2016`. In contrast to the 2016 version, the modern version is distributed very similarly to how regular Office apps are, almost certainly necessitating some sort of public hosting of a config file.
The config file would look very much like this:
```
```
* (For the x86 installer's config file, replace `"64"` with `"32"`.)
* (For the ARM64 installer's config file, add the line ` ` below ` `.)
For those wondering, a config file that only involves Access Runtime would **not** conflict with the regular `Microsoft.Office` package. Whereas an Access Runtime-only config would involve the `AccessRuntimeRetail` sub-product of Office, the `Microsoft.Office` package instead involves the `O365ProPlusRetail`, `VisioProRetail`, and `ProjectProRetail` sub-products.
Somewhat related:
* #411075.
* #410765.
* https://github.com/pl4nty/winget-extras/pull/319.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Microsoft 365 Access Runtime download details and the related items #411075, #410765, and winget-extras PR #319. Use the provided configuration requirements to account for x86, x64, and ARM64 installers. Done means the package request has a complete manifest and the installer configuration is publicly available as required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100