Make EDDI compatible with VoiceAttack V2

[alxwolf]

What happens now

After VoiceAttack starts it shows:

Plugin initialization exception [EDDI 4.1.0]: Could not load file or assembly 'Eddi, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null'. Format of the executable (.exe) or library (.dll) is invalid.

How it can be fixed

VoiceAttack v1 can still be accessed - go to https://voiceattack.com/downloads

If you are a VoiceAttack v2 user, you will be able to install v1.

For standalone (website) version users, your registration key will work with both versions.

For Steam users, make sure to download the 'Steam Legacy Edition' version (note that you will need to be logged into Steam to validate that version).

((c) @gmagenheimer)

What I'd like to happen

Have EDDI compatible with VoiceAttack V2 in the long run

How it can happen

No idea how to fix it, but there's a workaround for the moment - use VoiceAttack v1.

EDDI Version

V 4.1.0

[Darkcyde13]

The developer is aware of this, I first reported it on the EDDI Discord channel. They have a copy of VA v2 and will be looking into it, although no timeframe for when (or if) it will be done. 🙂

This is the pinned message on Discord:

"EDDI is currently incompatible with VoiceAttack version 2. I have a copy of VoiceAttack version 2 and will begin to explore development on that updated platform. In the meantime, EDDI is still compatible with legacy VoiceAttack version 1.

If you use the standalone (website) version of VoiceAttack, go to voiceattack.com/downloads. Your version 2 registration key will work with both versions.
If you use the Steam version of VoiceAttack, download the 'Steam Legacy Edition' version. If VoiceAttack version 2 installed then you will be able to validate and install version 1 also.
Data files are stored separately so you should be able to have both versions installed simultaneously without issue. "

[Tkael]

I've revised the Discord message to state:

EDDI is currently incompatible with VoiceAttack version 2. I have a copy of VoiceAttack version 2 and will begin to explore development on that updated platform. Support for VoiceAttack version 1 on new EDDI releases will likely sunset once that update is completed. In the meantime, EDDI is still compatible with legacy VoiceAttack version 1 so I don't feel like there is a need for a great rush to switch to version 2.

Notes: Switching to version 2 is likely to require a framework upgrade from .Net Framework 4.8 to .Net 8. It is also likely to cause EDDI to run in 64 bit mode by default, meaning that older 32 bit-only voices may stop working with EDDI. There may be software library dependency issues or isolation issues which could require significant code revisions.

Per VoiceAttack's developer:
VoiceAttack v1 can still be accessed - go to voiceattack.com/downloads.
If you are a VoiceAttack v2 user, you will be able to install v1.
For standalone (website) version users, your registration key will work with both versions.
For Steam users, make sure to download the 'Steam Legacy Edition' version (note that you will need to be logged into Steam to validate that version).

Data files are stored separately so you should be able to have both versions installed simultaneously without issue.

[eugenweissbart]

Hate to be that guy, but any updates on this?

Give us hope <3

[Tkael]

Fixing bugs / issues in 4.1.6 comes first.
I have been able to successfully port EDDI to .NET 8 but there are issues that still need to be resolved when running EDDI as a plugin for VoiceAttack. The AppDomain separation that used to exist between EDDI and VoiceAttack is gone in .Net 8. That's a major change that I need to handle properly before EDDI can be compatible with VoiceAttack 2.

[DamienSaussac]

Sorry to be that other guy but .Net 8 will reach its end of support by November 2026. You should consider porting EDDI to .Net 10

[Tkael]

Sorry to be that other guy but .Net 8 will reach its end of support by November 2026. You should consider porting EDDI to .Net 10

The change from .Net 8 to .Net 10 should be a smaller change. But for now .Net 8 is still the correct target.