Implement DDEX Provider as VSIX [DNET659]

[firebird-automations]

Submitted by: André Ziegler (andre.ziegler)

Replaces DNET581
Replaces DNET739
Block progress on DNET373
Replaces DNET623

Votes: 1

To fix the issue, that the DDEX provider gets lost after updating an Visual Studio extension (DNET581), implement/install the DDEX provider as VSPackage

[firebird-automations]

Modified by: @cincuranet

Link: This issue replaces DNET739 [ DNET739 ]

[firebird-automations]

Commented by: André Ziegler (andre.ziegler)

"I'm planning to change the DDEX provider from installer to VSIX"

which version will you support in the VSIX? 2012-2017? Or 2017 only?

[firebird-automations]

Commented by: @cincuranet

Not sure yet. Probably 2017 and 2015.

[firebird-automations]

Modified by: @cincuranet

Link: This issue block progress on DNET373 [ DNET373 ]

[firebird-automations]

Modified by: @cincuranet

Link: This issue replaces DNET623 [ DNET623 ]

[firebird-automations]

Modified by: @cincuranet

issuetype: Sub-task [ 5 ] => Task [ 3 ]

Parent: DNET581 [ 20235 ] =>

[firebird-automations]

Modified by: @cincuranet

Link: This issue replaces DNET581 [ DNET581 ]

[MagicAndre1981]

ok, I see the issues are migrated to github.

based on the fork of Daniel Rail (which is now deleted) I was able to to compile the VSIX with some modifications.

I installed it a few weeks ago, compared to old installer, after updating other extensions it still works.

Some modifications are hardcoded paths to VS locations (which differ for each SKU) because some DLLs are not available as nugets.

Now I have no idea how to put his change history + my local modifications into a new pull request

[cincuranet]

I do not plan to keep DDEX, as discussed in the mailing list. Probably dropping it together with other changes related to .NET 6 (again, outlined in the list).

[cincuranet]

Closing because #1001.