Hi,
For more clarity I need to set ISWIFile object Name property explicitly.
Next code fails with exception in KeyPath property (in attachment).
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Question with file
Started by
AntonS
, Aug 11 2004 13:33
1 reply to this topic
AntonS
-
- Full Members
- 94 posts
Posted 11 August 2004 - 13:33
| CODE |
| Set ISWIFile = ISWIComponent.AddFile("C:\WINDOWS\notepad.exe") ISWIFile.Name = "MyNotepad1" ISWIComponent.KeyPathType = kptFile ' Next line fail ISWIComponent.KeyPath = ISWIFile.Name |
Assume, that ISWIComponent - is an InstallShield Component object.
Why?
When I try remove file with RemoveFile method, ISWIFile object still exist, but AddFile method receive only file name as string, ISWIFile object is orphan and therefore I can not link it to ISWIComponent object.
Name property defined in documentation as Read-Write property, but without link to ISWIComponent object its Write feature seems to be useless .
Attached Images
AntonS
-
- Full Members
- 94 posts
Posted 20 August 2004 - 14:37
This issue has been reproduced and determined to be a bug in our software. This issue has been submitted to InstallShield Development team as work order # 1-TKJDP.
Currently there is no workaround for this issue. InstallShield Development team is investigating this issue, but at this moment, there is no estimated time frame for when this issue will be fixed.
Further I proposed to track the status of this issue using the work order number by checking release notes at www.installshield.com/downloads or searching the Knowledge Base at http://support.installshield.com/kb/.
Eventually, not so important, is there file keys created automatically (implicitly), or explicitly.
But I recommend to abstain from setting ISWIFile Name property at this time.
Currently there is no workaround for this issue. InstallShield Development team is investigating this issue, but at this moment, there is no estimated time frame for when this issue will be fixed.
Further I proposed to track the status of this issue using the work order number by checking release notes at www.installshield.com/downloads or searching the Knowledge Base at http://support.installshield.com/kb/.
Eventually, not so important, is there file keys created automatically (implicitly), or explicitly.
But I recommend to abstain from setting ISWIFile Name property at this time.