Visualstudio-docs: Native C++ package support

[annajayne]

This topic assumes that VSIX packages are always implemented using managed code, which is not necessarily the case.

How does this relate to native C++ packages created using the Wizard (which use VSL::IVsPackageImpl) etc.?

As VS2017 is the second version of Visual Studio to support AsyncPackages, the documentation, VSL implementation and samples should really support asynchronously loaded native C++ packages by now.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 126cb7b6-69ed-c50d-5b1b-b4b94948bf96
• Version Independent ID: f666821f-3bd5-282d-6bd6-4550fafa2872
• Content: How to: Use AsyncPackage to Load VSPackages in the Background - Visual Studio
• Content Source: docs/extensibility/how-to-use-asyncpackage-to-load-vspackages-in-the-background.md
• Product: visual-studio-dev15
• GitHub Login: @gregvanl
• Microsoft Alias: gregvanl

[mlevis]

Yes Native C++ support needs to be added. You can still create a C++ vspackage in VS 2019. I have a very extensive extension that has been around since VS6. Converting all of that to C# is not an option.

[leslierichardson95]

Thanks for submitting your feedback and we apologize for the delayed response. Due to current resourcing and substantial extensibility changes we are currently working on that will result in significant, structural doc changes, we are closing this lower priority issue. We will return to this issue on a later date and address it based on it's relevance after those extensive extensibility updates are made. Feel free to comment here as necessary.