OfficeDev / OfficeDev/Office-Addin-Scripts
Support access to Dev Tools console in "New Outlook"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 194
- Forks
- 117
- Avg merge
- 1d 32m
- Merged PRs (30d)
- 2
Description
To get access to the Dev Tools console in "New Outlook", it is necessary to start outlook with a switch --devtools as mentioned here:
https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/one-outlook#debug-your-add-in
Currently, there is no way to pass this switch when using office-addin-debugging
Ideally, the script would have a way of detecting "New Outlook" and add the switch automatically when starting Outlook for sideloading add-ins.
Alternatively, if we had a way to pass the switch to the office-addin-debugging script so that it passes it on to Outlook, it would help to solve the problem, but would put a burden on users to know about this switch and use it if they are in "New Outlook" mode.
Contributor guide
No contributing guide indexed for this repository
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 with the office-addin-debugging package linked in the issue and review how it launches Outlook for sideloading add-ins. Determine whether New Outlook can be detected and how the --devtools switch could be passed through; done means users can access the Dev Tools console when debugging in New Outlook, either automatically or through a documented option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100