search

bsivanov / Open-XML-Package-Editor-Power-Tool-for-Visual-Studio

This Power Tool is a Visual Studio add-in that provides an easy way to parse and edit Open Packaging Conventions files, including Word, Excel and PowerPoint documents.
17 stars 4 forks source link

Add support for Visual Studio 2022 #3

Closed bsivanov closed 2 years ago

bsivanov commented 3 years ago

Add support for Visual Studio 2022 by creating separate targeting Visual Studio 2022. This closes #2.

The "old" project - OpenXMLEditor.11.csproj should support 32bit versions - VS2012-VS2019. The "new" project - OpenXMLEditor.17.csproj should support 64bit versions - VS2022.

Most of the files are extracted as shared project. During this, the property of some of the files was set to be IncludeInVSIX, which fixes #1.

PrzemyslawKlys commented 2 years ago

Can we get this accepted and published? ;-)

bsivanov commented 2 years ago

Can we get this accepted and published? ;-)

Yes, I will try to squeeze it this week... (some personal issues, COVID, Christmas, pure laziness and so on, you know).

The problem I was concerned about is that I have to drop the support for versions before VS2017 if I choose this approach, as there's currently no way to upload multiple VSIX for one extension (Visual studio PMs mentioned they have plans to do this but nothing is scheduled) . And I want to avoid splitting it in two separate extensions.

So I tested some different approaches, but with the breaking changes introduced recently, it seems there is no way to avoid the split. So I will probably upload the old-versions-compatible VSIX (supporting VS2012-2019) as a release here and link it in the repo README and extension description. Not ideal, but let's suppose there aren't too much users doing fresh installs on VS2015 and below. The "official" extension will support VS2017-VS2022 (this is still in my local branch and not in the PR).

PrzemyslawKlys commented 2 years ago

Thank you.

bsivanov commented 2 years ago

I decided on another approach, so abandoning this (see #4)