Why are Matlab.Application.Single entries corrupted in registry?

2 次查看（过去 30 天）

David Varga 2015-6-4

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/222463-why-are-matlab-application-single-entries-corrupted-in-registry

Dear support,

I have several Matlab versions installed, and my problem is I am unable to start a new Matlab instance (Matlab.Application.Single) via COM with the version I specify what is not the last registered Matlab version.

For example:

I am exucuting a code in R2011b (7.13) that tries to start a new Matlab.Application.Single.7.13 instance. But it starts a new R2010bSP1 instance (the one I've installed lastly) rather than opening a new R2011b instance.

I have investigated the issue:

Correct entries:

In registry in the node "Matlab.Application.Single", the CLSID is set to the class id that corresponds to R2010bSP1, and this is absolutely okay, because this is the currently registered Matlab version.
In node "Matlab.Application.Single.7.11" it is also the correct R2010bSP1 CLSID is displayed.

Not so correct entries:

But in the node "Matlab.Application.Single.7.13", what is the dedicated node to R2011b, the CLSID is the same as I have written above.
This is true for R2008b also.
For R2013b and R2014b (8.2, 8.4) in the dedicated nodes a different class id is inserted (and both of them are correct).

So as a conclusion:

Why the installation of R2010bSP1 have corrupted my registry entries for Matlab versions older than R2013b?
Is there a generic solution to fix the registry in an "official" way or shall I implement something to fix it (generating new CLSID-s and assign them accordingly)?
If there is an official solution, what is that?

Thanks a lot in advance!