TD is corrupting slx files

[J.S.]

I imported the component "Language Support Prototype" into my
configuration by curiosity at the beginning of a long day's work on my
current TD configuration. There was an error message saying that this
component was somehow faulty. Ok, I thought 'forget it'. I saved my work
after hours of configuration and built serveral images. Finally I closed
the project.
Now I wanted to reopen the slx. TD rejects the file with an error message

Configuration Management Interface (CMI) Error
Code = 0x800a16a8
Description = Language Support Prototype does not contain valid
cmiLangId property

and closes again. None of my backups from day's start is able to open
because this component seems to be added to all afterwards saved files
although my efforts to integrate the faulty component were successless
this morning.

This is the SP2 Target Designer environment with all updates that can be
found on the ms embedded website.

What to do now to save hours of nearly unreproduceable work?

 

[KM]

J.S.,

If you saved you SLX as XML - you can manually edit it to remove the faulty component.

If not... you are out of luck with TD, but still can load the SLX with CMIExplorer. Search this NG. I've posted a few CMIExplorer
scripts on how to load SLX and add/delete components from the script.

KM

PS. That wasn't a good idea to add that component to your configuration.
But I don't understand why Microsoft didn't make the component visibility < 100.

 

[J.S.]

KM,

thanks for your help. Seems as I am to spend another day to redo my work...

PS. That wasn't a good idea to add that component to your configuration.
But I don't understand why Microsoft didn't make the component visibility < 100.

Not a good idea? I agree:-( Now I know it.

@MS: I don't understand why MS doesn't fix such a poisoning component...
or at least prevent users to add it.