I have a VSIX package (extension) that works and can be debugged in VS 2013 and 2015. I have now adjusted the manifest to allow the package to be installed in VS 2017. However, it doesn't work there properly and I want to debug it.
I open the package project in VS 2015 and tell it to debug the package in VS 2017 RC with the usual command line switch /rootsuffix Exp
. A clean VS 2017 instance starts, but the package is not installed in it so it cannot be debugged. How to fix this?
The only practical way to add support for VS 2017 is to open and build your extension in VS 2017: How to: Migrate Extensibility Projects to Visual Studio 2017. After the migration it should be easy to debug in VS 2017.