8 replies to this topic

[pauldavidson]

Hi.

I am using InstallShield 2010.

Wehn I get to the stage that the install is taking place, it looks like it has stuck. However I added some trace in to see what was happening, and it seems to take a very long time when copying over each individual file.

Here is an example (note the last few lines with the timestamp):

[Stefan Krueger]

Are you installing from CD, network or local hard disk? (CD or network communication might be slow)
Antivirus software running in the background?

[pauldavidson]

I am running it directly from the hard drive. I have tried on 2 machines. 1 with anti-virus and 1 without. Something has actually changed in the installer I would guess. The install was working fine before installing the files. There were a few loose ends to the installer, and I was busy with other things, so a colleague was tidying it up a bit, and since then it takes a very long time to install each individual file. It even takes a while to cancel the setup. We are both a little confused, as he did not change anything that should have had this affect.

Unless there is some way to diagnose, the only alternative I can think of is to start again, but this will be time consuming in itself, with custom dialogs, and a lot of code etc.

[pauldavidson]

Ok I created a new installer and copied stuff over as a test. It was still slow. Now I had a look at some files that were slow. It seems to be all the dll files. If I remove them all, and it only installs jpg's etc, it is as quick as you would expect.

Why would copying these over be so slow? It does not pick them up as self-reg files if I check. Only refers to them as assembly files.

[pauldavidson]

Found something interesting.

This is only a problem with an InstallScript project. If I use an InstallScript MSI project it is no longer an issue.

I would still like to figure out why though!

[Stefan Krueger]

Assembly registration maybe? Maybe the change wasn't in the setup (do you have an older build archived?) but in the .NET runtime (Windows update)?

[pauldavidson]

No there was no windows update done since that I recall. I am already wondering if this has been an issue all along, but my testing was on my machine at home that is very high spec, so the delay would not have been noticeable.

1. Using the current InstallScript project = extremely slow install
2. Using a brand new InstallScript project with same install files = extremely slow install
3. Using a brand new InstallScript MSI project with same install files = fast install

[vravula]

Hey, did someone find a solution for this issue?

 

I recently got a customer request to debug the slow installation (InstallScript based) of a product on their machines.

 

IS debugger showed me the install is taking a lot of time to copy a file to the destination.

In Windows Task Manager I noticed a process called DotNetInstaller.exe is spawned everytime before copying a file. Do you know what this process does?

 

Thanks,

Venkatesh

[Stefan Krueger]

Just a shot in the dark: check you component settings - is .NEt Assembly set to yes or no?