I'm trying to write a "custom debugger extension" for VS 2017 (>= 15.8.8). Now... what did I do? First -> C#, new VSIX project. Second -> Add item "custom debugger extension" ... then I tried to compile... but, "AppliesTo(MyUnconfiguredProject.UniqueCapability)" does not compile... I didn't find out anything about this "MyUnconfiguredProject" class, so I out-commented it. Then it compiled, but the debugging extension does not show up (I wanted to use it for C++ projects) ... ok then, I added 2 files into the "ImportBefore" and "ImportAfter" (.props and .targets). .targets is just importing the ".xaml" file of my project and the .props defines one "DebuggerFlavor". (I found out, that this is needed by investigating an old project description I found somewhere). Fine... now, the compiler is shown. I select it and when I try to start, I get an error... debugging cannot launch bla bla... whatever.
Now, here's where it's getting interesting. The .vsixmanifest file contains PackageManifest. So, it's a version 2 manifest file. When I replace this with a version 1 manifest... simply by copying in the file from this project I found... then it works and the debugger extension starts.
And now the question... what's going on here? What's the point I'm not understanding? I did build and use version 2 manifest files in my projects earlier (those were extension written in C++ and therefor COM modules). I never had such problems... is there something I need to do because it's an assembly and not a dll? ... or... what?
Rudolf