The problem has always been a licensing issue rather than a technical one.
There have been no further announcements of an API for Voice Command. It's
been technically possible to automate Voice Command since it was first
released (I wrote a proof of concept and showed it to some Microsoft people)
but the speech engine is licensed by Microsoft from a third-party and the
license only allows it to be used for the Voice Command functionality, not
to provide any programmatic access to the engine.
Peter

Signature
Peter Foot
Microsoft Device Application Development MVP
www.peterfoot.net | www.inthehand.com
In The Hand Ltd - .NET Solutions for Mobility
> Does any one remember the demonstration of the Voice Command API
> (http://channel9.msdn.com/showpost.aspx?postid=303900 , skip 15 minutes
[quoted text clipped - 4 lines]
>
> Joel Johnson
Joel - 11 Mar 2008 13:05 GMT
Thanks for the explanation. I was really beginning to think that MSFT forgot
about it. I can see how opening third party access could cut the technology
owner out of potential income.
Joel
> The problem has always been a licensing issue rather than a technical one.
> There have been no further announcements of an API for Voice Command. It's
[quoted text clipped - 5 lines]
>
> Peter