What happens now
Well suggestion for this came from my playing with available languages that I could select. I came a cross NaturalVoiceSAPIAdapter which enables additional voices in net8 sample app I had. When I tried it in current version of EDDI 4.1.0-b3 when running on Windows 11 those new languages where not visible. Quick test showed that that was due to Net Framework used in EDDI.
What I'd like to happen
I would suggest porting EDDI to net8 to give it more opportunity for future enhancements from framework updates. This is partly related to #2379.
How it can happen
You can check out my quick hack job in porting at net8 repo to see what is required to make it work. Basically what I did is:
- Switch to new .csproj style files using net8, target framework is set net8.0-windows10.0.26100.0
- Had to include code for CSCore, they have net8 port but it is not in NuGet yet
- Had to update to latest RestSharp, was getting serialization errors
- To compile solution I had to disable few tests, reason was missing PrivateType class from testing framework
- Publish doesn't copy all the files to output folder, so manual copy is needed
EDDI Version
Changes are done on development branch.
What happens now
Well suggestion for this came from my playing with available languages that I could select. I came a cross NaturalVoiceSAPIAdapter which enables additional voices in net8 sample app I had. When I tried it in current version of EDDI 4.1.0-b3 when running on Windows 11 those new languages where not visible. Quick test showed that that was due to Net Framework used in EDDI.
What I'd like to happen
I would suggest porting EDDI to net8 to give it more opportunity for future enhancements from framework updates. This is partly related to #2379.
How it can happen
You can check out my quick hack job in porting at net8 repo to see what is required to make it work. Basically what I did is:
EDDI Version
Changes are done on development branch.