PDA

View Full Version : Different between IS 2008 vs 12.0?



zxbuilder
06-13-2007, 01:54 PM
Hi All,

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

RobertDickau
06-13-2007, 02:32 PM
For an overview of what's new in InstallShield 2008, please see the Top New Features (http://www.macrovision.com/products/installshield/installshield/features/topnew.html) page.

For a detailed list of changes, please see the InstallShield 2008 Release Notes (http://support.installshield.com/kb/view.asp?articleid=Q112996).

zxbuilder
06-13-2007, 04:11 PM
Robert Dickau,

Thank for your info. Another question is what IS is best fit for window Application (IS 12.0 or 2008)?

Thanks,
Tim

RobertDickau
06-13-2007, 04:28 PM
InstallShield 2008 has the most up-to-date support for Windows Vista and other technologies, and so naturally I'd suggest that version for a Windows application.

Vijay_K
06-14-2007, 07:57 AM
The IS2008 release notes quote;
"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

Christopher Painter
06-14-2007, 08:02 AM
Two different directories implies two different components obviously... I do this all the time. For example I have an install the deploys 80+ web services so I have files lile Global.asax and Web.config get statically linked 80+ times.

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.

Vijay_K
06-14-2007, 08:31 AM
Hi Christopher ,
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.

Christopher Painter
06-14-2007, 08:37 AM
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

Vijay_K
06-14-2007, 08:43 AM
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?

RobertDickau
06-14-2007, 09:18 AM
For an uncompressed InstallScript build, you might set the CD-ROM Folder property of the two features containing identically named files to different values ("src1" and "src2", or preferably something more imaginative). The CD-ROM Folder values are used as subdirectory names at your installation source to keep multiple files with the same name from colliding.

Either that, or perhaps consider a compressed build.

Christopher Painter
06-14-2007, 09:26 AM
Vijay, meet Robert.... he's THE man.

Robert- I was describing a problem from a couple years ago.... you are right, I choose a compressed media set.

RobertDickau
06-14-2007, 09:43 AM
(And Vijay, meet Chris --- he's one of the most prolific of the invisible army of helpful volunteers you'll find here...)

((Also, for anyone following along, in the MSI world the component property Source Location addresses the same uncompressed-file-name-collision issue described in this thread...))

Vijay_K
06-14-2007, 09:59 AM
Thanks guys.
I manged to create a work around.
You are right on the money abour "src1" and "src2".
When IS12 builds the release, it goes through the components and creates a file/folder in the release 1 folder named "Folder1" for instance. You need unique component names, as well as, unique high level folders within these components.
I had folders that were named the same in the unique components, so when it came to build these folders, it simply, gets confused.
ie Component 1
|--Folder1
|-File1
|-File3
Component 2
|--Folder1
|-File2
|-File3


When it build it puts both file 1 and file 2 in folder1, and creates one instance of file3 even if they are different.

This should be
ie Component 1
|--Folder1
|-File1
|-File3
Component 2
|--Folder2
|-File2
|-File3

Now the correct files and folders are created.

Cheers guys..