This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Relative path in DIsplay icon not working
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 13, 2009
05:55 AM
Relative path in DIsplay icon not working
I want to show a custom icon in the As remove programs. SO I am setting Display Icon property in the General Information->Add or Remove Programs view.
The problem is that when I hardcode the actual physical path then the icon is showing up correctly. But when I try to give relative path for eg.\App.ico, then the icon is not shown.
I'm using pure installscript project.
If anybody has the solution, please suggest.
Thanks,
Mayur.
The problem is that when I hardcode the actual physical path then the icon is showing up correctly. But when I try to give relative path for eg.
I'm using pure installscript project.
If anybody has the solution, please suggest.
Thanks,
Mayur.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 13, 2009
07:42 AM
In InstallScript projects, the path that you specify should be the path on the target system, not on your development system. You can use system variables in your path (for example: \App.ico).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 14, 2009
02:36 AM
Thanks Debbie. That works well.
But then I was wondering, how does it work when the direct physical path is hardcoded?
But then I was wondering, how does it work when the direct physical path is hardcoded?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 14, 2009
08:19 AM
If your UI dialogs allow end users to change the destination path of your product, and they do change the path, the hard-coded path for the icon will be wrong. What if, for example, you hard-code a value that begins with C:\, but an end user doesn't have a C drive? I think in many cases, hard-coding the path is not recommended.