tim_dang1.5524923071401643E12 asked a question.
I'm using IS 11.5 now. I would like to take a training and upgrade IS to support .net v3.0 and Vista window. I would like to know what's different between IS 2008 and 12.0?
Thanks,
Tim
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
For a detailed list of changes, please see the InstallShield 2008 Release Notes .
Thank for your info. Another question is what IS is best fit for window Application (IS 12.0 or 2008)?
Thanks,
Tim
"IOA-000028242
InstallShield no longer crashes if you include two dynamic file links in the same component, and each has a file with the same name.
"
I find a problem also when using static links (but IS12 does not crash), with two different files with the same name, that exist in diferent directories, can any one tell me if this fix in 2008 will also solve the static link issue?
Thanks in advance.
Vijay_K
Why type of build are you doing? The only thing I can think of is where you have 2 components with the same keyfile / directory but mutually exclusive conditions ( i.e. install this dll on 9x and this dll on NT platforms and make them transitive so that if you upgrade the OS and repair it'll switch out )
In that scenario an uncompressed build can be problematic as the source tree will try to put the same dll name in the same directory.
Otherwise I'm not sure what problem you are having.
Thanks for the prompt responce.
I have an install script object.
2 Different Component, with 2 different Target location.
In Component 1 i have added a file called c:\Feature.txt,
In Component 2 I have added a file called c:\test\Feature.txt.
Although the files are different and from different location, when I build, and install the installscript project, I only get a copy of one file, installed in the 2 different target directories I specified for each component.
Thanks,
I look forward to your response.
Sorry,
Chris
Robert can probably help you alot more.... most of my InstallScript project experience is back from the 5/5.5 days. I did one in 7 when I was learning MSI and have pretty much stayed in the MSI world ever since. Typically I'm doing Basic MSI with InstallScript CA's.
Sorry,
Chris "
Thanks Mate, Who is Robert??? Does he have a surname, or any way of cantacting him from this forum?
Either that, or perhaps consider a compressed build.
Robert- I was describing a problem from a couple years ago.... you are right, I choose a compressed media set.