vb.net - Is there a reason I would use the Microsoft.Speech Namespace instead of directly using SAPI 5.4 in Visual Studio? -

speech in visual studio confusing. in other languages , vb6, have working code uses sapi 5.4 objects. see there microsoft.speech , system.speech objects in visual studio. assume can have managed code. can still program directly sapi? should know why want use 1 method or other? code isn't remotely similar. application run on windows server , written in vb.net

you might want @ answer this question first.

given you're running on windows server, want microsoft.speech rather system.speech following reasons:

• server doesn't include sr engines default; have install desktop experience pack;
• system.speech requires training work well;
• microsoft.speech has sr engines work lower-quality audio.

you can still program directly sapi; real difference between server sapi , desktop sapi underlying sr engine. (the client-side api same.)

programming directly sapi more complicated, gives more control. couldn't recommend 1 or other without knowing ultimate goals are.