- Joined
- Jun 22, 2005
- Messages
- 19
- Reaction score
- 0
Hi,
I think there's another problem how the Component Designer handles path names containing blanks.
In the Component Designer I created a shortcut resource and opened it. In the "Edit Component Resource" window I opened "Extended Properties" and selected the "Target Path".
The original path to my Acrobat Reader is
C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe
In Component Designer syntax this would translate to
%16422%\Adobe\Acrobat 7.0\Reader\AcroRd32.exe
I put this into the Value field of the "Target Path" property.
The Component Database Manager accepted my component without warning or error, as did the Target Designer. When I inspected the created shortcut file afterwards, however, I found that the entire path had been omitted and only the filename AcroRd32.exe had survived the build process.
Did I just forget to put a special (undocumented) character around my path string (parentheses didn't work either)? Or does the Component designer have a general problem in handling path names containing whitespaces? Is there any description how it is done correctly?
skagway095
I think there's another problem how the Component Designer handles path names containing blanks.
In the Component Designer I created a shortcut resource and opened it. In the "Edit Component Resource" window I opened "Extended Properties" and selected the "Target Path".
The original path to my Acrobat Reader is
C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe
In Component Designer syntax this would translate to
%16422%\Adobe\Acrobat 7.0\Reader\AcroRd32.exe
I put this into the Value field of the "Target Path" property.
The Component Database Manager accepted my component without warning or error, as did the Target Designer. When I inspected the created shortcut file afterwards, however, I found that the entire path had been omitted and only the filename AcroRd32.exe had survived the build process.
Did I just forget to put a special (undocumented) character around my path string (parentheses didn't work either)? Or does the Component designer have a general problem in handling path names containing whitespaces? Is there any description how it is done correctly?
skagway095