This isn't really a problem, but a question.
Do you have tips how to increase the performance of the install process?
Because.. now I have more then 1000 components, and the installation/uninstallation takes very long..
Can I maybe do something like merging components?
Does it increase performance in any way if i use cab files?
Do you have any other tips?
Every idea would be appretiated!
Suggested Articles
Hi,
The install time depends on the number of components that must be deployed. So reducing the number of components is a good idea.
As for the CAB files I don't think that using them will improve the performance.
Also, another suggestion would be to organize your application into several features. This way you can give the user the possibility to install only a part of the components.
All the best,
Ciprian
The install time depends on the number of components that must be deployed. So reducing the number of components is a good idea.
As for the CAB files I don't think that using them will improve the performance.
Also, another suggestion would be to organize your application into several features. This way you can give the user the possibility to install only a part of the components.
All the best,
Ciprian
Hi,
Advanced Installer allows you to move resources between components or even reduce their number.
To do that go to the organization page and drag and drop the deisred resources between components.
More information at:
http://www.advancedinstaller.com/user-g ... ation.html
Also, for more details about organizing your application into components at:
http://msdn.microsoft.com/library/defau ... onents.asp
Best regards,
Ciprian
Advanced Installer allows you to move resources between components or even reduce their number.
To do that go to the organization page and drag and drop the deisred resources between components.
More information at:
http://www.advancedinstaller.com/user-g ... ation.html
Also, for more details about organizing your application into components at:
http://msdn.microsoft.com/library/defau ... onents.asp
Best regards,
Ciprian
Last edited by ciprian on Thu Sep 22, 2005 8:40 am, edited 1 time in total.
Hi,
I'm afraid that it is not possible to place in the same component two files from different folders.
Microsoft's Platform SDK states:
"Do not create components containing resources that will need to be installed into more than one directory on the user's system. The installer installs all of the resources in a component into the same directory. It is not possible to install some resources into subdirectories"
All the best,
Ciprian
I'm afraid that it is not possible to place in the same component two files from different folders.
Microsoft's Platform SDK states:
"Do not create components containing resources that will need to be installed into more than one directory on the user's system. The installer installs all of the resources in a component into the same directory. It is not possible to install some resources into subdirectories"
All the best,
Ciprian
Well.. that was what I was afraid of..
In my Project I saw a few components that had the same directory, and was able to move the resources.
Is or will there be in future releases any feature like "clean up components" which merges all components which have the same directory?
With more than 1000 components it would be impossible to do that manually..
In my Project I saw a few components that had the same directory, and was able to move the resources.
Is or will there be in future releases any feature like "clean up components" which merges all components which have the same directory?
With more than 1000 components it would be impossible to do that manually..
I'm afraid that such a feature doesn't exist.
When creating the components, Advanced Installer already groups the resources according to the rules specified by Microsoft.
For example every EXE, OCX, DLL file have each their own component
More information on this topic at:
http://msdn.microsoft.com/library/defau ... onents.asp
However there is a workaround. You could create a create a script that changes the extensions of the files to be placed in package.
Example EXE -> EXXE
Then you can add the files to the project. This way Advanced Installer will not generate new components for those type of files. The number of components will be smaller.
After you added all the files save the project. Then open the AIP file in a text editor and replace the extensions you created with the original ones
All the best,
Ciprian
When creating the components, Advanced Installer already groups the resources according to the rules specified by Microsoft.
For example every EXE, OCX, DLL file have each their own component
More information on this topic at:
http://msdn.microsoft.com/library/defau ... onents.asp
However there is a workaround. You could create a create a script that changes the extensions of the files to be placed in package.
Example EXE -> EXXE
Then you can add the files to the project. This way Advanced Installer will not generate new components for those type of files. The number of components will be smaller.
After you added all the files save the project. Then open the AIP file in a text editor and replace the extensions you created with the original ones
All the best,
Ciprian
Hello,
I have a similar problem - my project contains a lot of files ....
I have one suggestion:
You put all files (or a part of them) in one Zip archive file and after copy this zip file on the target computer, you can try to run a script that will unzzip this file and remove the zip file ....
I am not sure if its possible ...
I have a similar problem - my project contains a lot of files ....
I have one suggestion:
You put all files (or a part of them) in one Zip archive file and after copy this zip file on the target computer, you can try to run a script that will unzzip this file and remove the zip file ....
I am not sure if its possible ...
Hi,
This is a nice idea and it is certainly possible to do this through a custom action.
However, there would be some difficulties. A repair operation would restore the ZIP file if the script has deleted it. So the custom action that deletes it needs to run both on install and on repair.
Regards,
Mihai
This is a nice idea and it is certainly possible to do this through a custom action.
However, there would be some difficulties. A repair operation would restore the ZIP file if the script has deleted it. So the custom action that deletes it needs to run both on install and on repair.
Regards,
Mihai