3

VS by default creates a legacy style project. I started manual migration, but then it fails to recognize the COM interop references for EnvDTE...

Is it possible at all?

mark
  • 53,726
  • 70
  • 260
  • 529
  • Hi, what does your project file looks like?(before the migration and after the migration) Maybe you can check if there's something wrong with the migration. – Pod Mo Nov 19 '19 at 10:01

1 Answers1

6

Is it possible at all?

It's possible as I know. For now, there's no any official document or blog which describes the steps about how to migrate a vsix project from old csproj format to new sdk-format,but at least it's a possible thing.

We may need some msbuild hacks to make it possible, here's one great open-source extension VsVim from JaredPar that has done this trial. Thanks to him!. I think you could get some useful info from this sdk-format project file.

In addition: Though it's possible, it's not recommended to do the migration before sdk-format vsix project is officially supported. Someone who does this may lose some UI features in Project=>Properties during vsix development.

LoLance
  • 22,153
  • 1
  • 27
  • 59
  • 1
    arg this was so painful, I reverted to the old style project - I still don't know how it can work - It would be nice to have at least official support of the UI part, and some output when it doesn't work, like why the vsix wouldn't be generated. – Matthieu Feb 02 '21 at 17:46