News:

HOT TIP! Exploring the commands packaged in VC's standard configurations is a great way to learn how to build your own. You can also clone a command as a starting point: just right-click and select "Clone" (or type Alt-C).

Main Menu

VC 2.136 + Win10 (9926) = .Net ERROR

Started by Kidovzky, February 10, 2015, 07:36:54 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


Kidovzky

11.02.2015 2:50:35   VoxLog created:
11.02.2015 2:50:35   115   .Net version: 4.0.30319.0
11.02.2015 2:50:35   115   Version.Major: 4
11.02.2015 2:50:35   115   Version.MinorRevision: 0
11.02.2015 2:50:35   165   .Net version: 4.0.30319.0
11.02.2015 2:50:35   166   Version.Major: 4
11.02.2015 2:50:35   166   Version.MinorRevision: 0

jitterjames

Thanks.  This is a known bug in Windows 10.

It will be dealt with in a future version of VC.

For now, just click OK and VC will continue to work normally.

Kidovzky

#3
Yes, but it worked for VoxCommando.exe, not for VoxCommandoSP.exe.
In SAPI mode i cant use russian lanhuage.
:( :-\
And TTSMS doesn't work. I can't see that in activated plugin list in the main menu.

When new version of VC will be released ?

jitterjames

This .Net message has nothing to do with that.

Either you have not installed the requirements for using the SP version correctly, or there is some other problem with running SP on windows 10. If you receive some other error message please let us know.

You are using a prerelease version of windows 10 so you should expect problems.  You should only use prerelease operating systems on a test machine. Microsoft is very clear about this when you download and install it.

The new version of VoxCommando will only remove this .Net warning. It won't change how it works.

If anyone is already using VoxCommando SP with windows 10 please let us know.

jitterjames

I have installed Windows 10 preview and everything works correctly.

After clicking OK on the .Net 4.5 warning message, I am able to run VoxCommando SP and use TTSMS voices, no problem.

So I guess you probably did not install the prerequisites for using the SP version correctly.

jitterjames