Great suggestion – we’re working on this for a future servicing release of Visual Studio 2017. Thanks!Anonymous commented
Now that I have your attention, consider also VSIXs containing multiple conditional manifests (not only conditional .pkgdef files or conditional DLLs). Example: manifest v1 for VS 2010, v2 for VS 2012-VS 2015, v3 for VS 2017, and v4 for the future.
VSX developers want to target multiple VS versions with a single VSIX. The most common question today is "How do I create a VSIX targeting VS 2010-2017? I know that Microsoft considers VS 2010 little used, but the reality is that there are still people using VS 2005 and 2008.