ADD: add Dev Kit to recommended extension

[hermanwenhe]

Thank you for your pull request! Please provide the following information.

---

Change Description:

Add https://marketplace.visualstudio.com/items?itemName=msoffice.microsoft-office-add-in-debugger to extension recommendation list of templates since it's officially released.

1. Do these changes impact any npm scripts commands (in package.json)? (e.g., running 'npm run start')
   No

2. Do these changes impact VS Code debugging options (launch.json)?
   No

3. Do these changes impact template output? (e.g., add/remove file, update file location, update file contents)
   No

4. Do these changes impact documentation? (e.g., a tutorial on https://docs.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins)
   No

If you answered yes to any of these please do the following:
> Include 'Rick-Kirkham' in the review
> Make sure the README file is correct

Validation/testing performed:

Describe manual testing done. 

[Rick-Kirkham]

Must have approval from @AlexJerabek before merging.

[akrantz]

The microsoft-office-addin-debugger is only required for legacy Edge, and shouldn't be needed for most scenarios. So I don't know that we want to recommend it here.

@millerds

[hermanwenhe]

This line is actually the Office Add-ins Development Kit. We leverage the old debugger's id so that we don't need to go through a whole review process. You can check it by click the link in PR description. @akrantz @AlexJerabek

[akrantz]

I don't believe you should be doing that. Not only is it confusing but it has the potential to bring in the old extension.

[Rick-Kirkham]

This line is actually the Office Add-ins Development Kit. We leverage the old debugger's id so that we don't need to go through a whole review process. You can check it by click the link in PR description. @akrantz @AlexJerabek

As I understand it, the Dev Kit is another tool for creating add-in projects. What is the reason for recommending it in templates that are used by other add-in creation tools?

[hermanwenhe]

I don't believe you should be doing that. Not only is it confusing but it has the potential to bring in the old extension.

We release the Dev Kit as a new version of the old debugger. If they click the pop-up install button of recommendation extension, they would install the latest version which is the Dev Kit. Therefore, there is no chance for developers to install an old version of VSC extension unless this is what they intend to do.

[AlexJerabek]

Will the ID "msoffice.microsoft-office-add-in-debugger" for the Dev Kit change, or is this permanently the old name?

[MingjiaLiu1995]

The Dev Kit is beyond project creation and can help developers explore more on platform capabilities. For example, they can explore samples or check the useful links in the side panel when they complete trying the first project.

[MingjiaLiu1995]

The Id will not change, still "microsoft-office-add-in-debugger".

[AlexJerabek]

I'm inclined to approve, but do we want this to be pushed to all our developers before the tool reaches GA?

[MingjiaLiu1995]

I'm inclined to approve, but do we want this to be pushed to all our developers before the tool reaches GA?

I think we can add the recommendation when the extension reaches GA for the following reasons.

1. Hopefully the extension will also support Outlook at GA, so all WXPO developers can use it in development.
2. By then, we complete merging sample repos and can check-in more samples for further explorations.

[millerds]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[millerds]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).