Another Environment Variables question
Hi,
I have a small problem with Environment Variables when making MSI-packages. The problem is that they all end with a "\", is there any way of removing the "\" in a simple way because some the programs doesnt like the paths ending with "\".
Edit: forgot to mention that I use Wise Package Studio.
I have a small problem with Environment Variables when making MSI-packages. The problem is that they all end with a "\", is there any way of removing the "\" in a simple way because some the programs doesnt like the paths ending with "\".
Edit: forgot to mention that I use Wise Package Studio.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
dj_xest
18 years ago
Anha,
I think you can safely remove that "\". It will have the same effect...
I think you can safely remove that "\". It will have the same effect...
Posted by:
anha
18 years ago
Ah,
I might have been a bit unclear. I get "\" at the end when I use [INSTALLDIR] or anyother variable that represents a path. Its nothing that I add when I set them. From what I see it happens automaticly.
I might have been a bit unclear. I get "\" at the end when I use [INSTALLDIR] or anyother variable that represents a path. Its nothing that I add when I set them. From what I see it happens automaticly.
Posted by:
dj_xest
18 years ago
Hi anha,
Wise and Installshield generates it automatically as you have said when defining it for [INSTALLDIR]. The only way to get what you want is to use [ProgramFilesFolder] string then append your working directory here. For example:
[ProgramFilesFolder]Your Folder\anha >> This could be your INSTALLDIR... what do you think? NOw, the problem here is if you ever have a standards in your team to always use [INSTALLDIR], you should probably include it in your documentation explaining why you did that.
Check it out.[;)]
Wise and Installshield generates it automatically as you have said when defining it for [INSTALLDIR]. The only way to get what you want is to use [ProgramFilesFolder] string then append your working directory here. For example:
[ProgramFilesFolder]Your Folder\anha >> This could be your INSTALLDIR... what do you think? NOw, the problem here is if you ever have a standards in your team to always use [INSTALLDIR], you should probably include it in your documentation explaining why you did that.
Check it out.[;)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.