Flexera Community

Jan 23, 2007

I have two file sets. The Target Location of the first one is set to $[OSFolder], that of the second one to $[CommonAppDataFolder]When I run the unit test, I get:Unit Test: ISDEV : error -9034: Unable to resolve value for path variable '$[OSFolder]' ...

May 16, 2008

I forgot to mention: I am using IS 11.5 but playing around with the trial version of IS 2008 ...

May 16, 2008

Hi,we have the same problem. We have about 21000 file in our setup, but only 3files statically linked (because we have to create shortcuts).The difference to your case is, that our directory- and file structure do notdramatically change between minor...

Feb 15, 2007

Christopher Painter wrote:...Nested installs are pure junk. Don't even consider them.So then, what are "best practises" if you have to comibine software parts (deployments) from different manufuacturers, which my software depends on (And it does not ...

Jan 23, 2007

Another shocking setbacks:- file permissions do not work: I tried to set a file to read- and writeable for all users - but it isn't- file attributes do not work: I tried to set a file to "hidden" and "system", but it did not work.- No permission se...

Jan 23, 2007

Now I found out, that you can use the directories of the directory table as values of DIM runtime variables, e.g. "[WindowsFolder]".Why is this important issue missing in the documentation ?? :confused:

Flexera Community

User Statistics

User Activity

Some Target Location Runtime Variables are not defined

Re: Dynamic file links and upgrades, Work around?

dynamic file linking generates new keys on every run

Nested Installations

Re: Some Target Location Runtime Variables are not defined

try and error: directory table keys can be used !