WISE - Release problems
Hi,
Since I added new releases to my installation I have problems to compile my installation package.
Any changes that I do at the source paths cause the installation to fail during compilation
Does any one knows WHY?
Since I added new releases to my installation I have problems to compile my installation package.
Any changes that I do at the source paths cause the installation to fail during compilation
Does any one knows WHY?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
Emil
17 years ago
Hi,
I checked it out and it seems that my installation works properly if and only if I comile all the releases at the same time....[8|]
I don't know why yet (WISE bug???) but when I tries to compile only specific release it failes if there is missing file (the wildcard ability is lost...)
Does anyone familiar with this problem??
I checked it out and it seems that my installation works properly if and only if I comile all the releases at the same time....[8|]
I don't know why yet (WISE bug???) but when I tries to compile only specific release it failes if there is missing file (the wildcard ability is lost...)
Does anyone familiar with this problem??
Posted by:
aa006
17 years ago
Posted by:
Emil
17 years ago
Posted by:
dm1
17 years ago
Posted by:
Emil
17 years ago
Thanks you all, But...
The problem that I have is a little bit different: I'm using few releases.
for example: if you build regular installation package you can set wildcard as *.* then, every time you compile your WSI file it adjust itself to the changes that made at the file source path.
But(!!), when you start using 2 or more releases in your setup the WSI package no longer succeed to adjust itself to file changes (meaning that, if you remove/add file the installation file will not adjust itself to the changes that you made.)
It is important to add that the compliation is through the command line and I choose the release simply by /c="ReleaseName"
The problem that I have is a little bit different: I'm using few releases.
for example: if you build regular installation package you can set wildcard as *.* then, every time you compile your WSI file it adjust itself to the changes that made at the file source path.
But(!!), when you start using 2 or more releases in your setup the WSI package no longer succeed to adjust itself to file changes (meaning that, if you remove/add file the installation file will not adjust itself to the changes that you made.)
It is important to add that the compliation is through the command line and I choose the release simply by /c="ReleaseName"
Posted by:
aogilmor
17 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.