Bug in Component Database Manager for import on SLD with registry

[jadeboy]

I created an Adobe Acrobat 4 component (.SLD). The registry is fine in
the .SLD but when I use Component Database Manager to import the
Acrobat 4 .SLD it improperly converts some "" to " in the registry
part of the .SLD. Below is some example. Any permenant solution to this
annoying bug, it wasted my entire day.

Good Registry:

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\open\command]
@="\"C:\\Program Files\\Adobe\\Acrobat 4.0\\Reader\\AcroRd32.exe\"
\"%1\""

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\open\ddeexec]
@="[FileOpenEx(\"%1\")]"


[HKEY_CLASSES_ROOT\AcroExch.Document\shell\print\command]
@="\"C:\\Program Files\\Adobe\\Acrobat 4.0\\Reader\\AcroRd32.exe\""

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\print\ddeexec]
@=" [FilePrintSilentEx(\"%1\")]"


[HKEY_CLASSES_ROOT\AcroExch.Document\shell\printto\command]
@="\"C:\\Program Files\\Adobe\\Acrobat 4.0\\Reader\\AcroRd32.exe\""

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\printto\ddeexec]
@=" [FilePrintToEx(\"%1\" \"%2\" \"%3\" \"%4\")]"



Bad Registry


[HKEY_CLASSES_ROOT\AcroExch.Document\shell\open\command]
@=""C:\\Program Files\\Adobe\\Acrobat
4.0\\Reader\\AcroRd32.exe"

"%1""

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\open\ddeexec]
@=hex(0):

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\print\command]
@=""C:\\Program Files\\Adobe\\Acrobat
4.0\\Reader\\AcroRd32.exe""

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\print\ddeexec]
@=hex(0):


[HKEY_CLASSES_ROOT\AcroExch.Document\shell\printto\command]
@=""C:\\Program Files\\Adobe\\Acrobat
4.0\\Reader\\AcroRd32.exe""

[HKEY_CLASSES_ROOT\AcroExch.Document\shell\printto\ddeexec]
@=hex(0):

 

[KM]

jadeboy,

No good solution to the bug other than manually fixing all the reg.keys :-(
For some reasons Microsoft never fixed this annoying bug in any SP, though it's been there forever.

 

[Nikolai Vorontsov]

Hello jadeboy,

part of the .SLD. Below is some example. Any permenant solution to this
annoying bug, it wasted my entire day.

Not permanent but suitable:
1. Save your component as an xml file.
2. Open it in a good editor.
3. Search and replace quotes.
4. Open component in CD and save it back in a normal (binary) format

You don't need to do this often - not many softwares write quotes to the
registry...

 

[jadeboy]

The problem is not the .SLD part, it's the importing of the .SLD into
Component Database Manager. If I load up .SLD file into Component
Designer, the registry is fine. It's importing into the database that
screw it up, once you select the component from Target Designer the
registry value is all messed up.

 

[jadeboy]

How can I ? The bad data is in the database, not in the .SLD file.

 

[KM]

jadeboy,

What do you mean?
CDM doesn't do anything with registry entries from an SLD. (at least it doesn't do anything bad)

Are you sure the entries are *correct* in the SLD file?
How do you know they are NOT correct after you imported the component in database? Are you checking them in TD?
Could you show us the SLD file?

The annoying bug that has been reported long time ago and we all continue to struggle with is in CD (Component Designer,
specifically Reg importer). Not in CDM.

 

[jadeboy]

I have confirmed that the .SLD is fine, I checked each individual
values. It's during CDM import that it messed up, I confirmed by adding
the component in TD and looking at the registry. I have also found
Target Designer also messed up when importing the registry. The above
registry "Good Registry" shows the actual registry and the "Bad
Registry" is the resulting registry from importing it.

 

[Andy Allred [MS]]

Hi, could you please zip your SLD (not the repository) and e-mail it to me
at wecrt AT microsoft.com? I'm triaging CD and IMport Framework bugs right
now and if this repro's for me it would be a great test case.

If I'm not able to repro but can fix this issue, I'll send a fixed version
back to you asap.

Note that it's possible the " is actually in the SLD but being
interpretted correctly by CD, but not TD. If you open the SLD in notepad,
drill down to those reg resources and I bet you find it's actually '&quot'
and not ' " '. In any case i'd be happy to look at this for you if you send
me the zipped SLD.

Thanks

 

[KM]

jadeboy,

It is really surprising if the bug you're describing is in CDM.

As Andy already said, you may want to open SLD and check the actual registry content there.
Or feel free to post your SLD here (zip it first and post as attachment using proper news client e.g. OE).