Filtering a Dirty App Setup.exe
Hi!
We currently use the DotNetFX.exe MSI to deploy .Net 1.1 Framework.
I'm currently capturing an application that forces the installation of the .Net Framework. This if ofcourse produces tons of garbage registry information related to the .Net 1.1 Framework and not the application itself (11000 reg entries [8D] )
I've contacted the company that has developed this to try make them atleast check if the Framework is installed before they install the framework but with no luck.
Does anyone know if it's "safe" to i.e capture the install of DotNetFX.exe and add the registry information captured as exclude filters in Wise Package Studio ?
Or another approach ?
We currently use the DotNetFX.exe MSI to deploy .Net 1.1 Framework.
I'm currently capturing an application that forces the installation of the .Net Framework. This if ofcourse produces tons of garbage registry information related to the .Net 1.1 Framework and not the application itself (11000 reg entries [8D] )
I've contacted the company that has developed this to try make them atleast check if the Framework is installed before they install the framework but with no luck.
Does anyone know if it's "safe" to i.e capture the install of DotNetFX.exe and add the registry information captured as exclude filters in Wise Package Studio ?
Or another approach ?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
MSIMaker
20 years ago
Try this.
Start the app install and once the dotnet stuff is completed during the install. Start your capture from there.
That way you are only capturing the actual app install and not the dependancies.
Start the app install and once the dotnet stuff is completed during the install. Start your capture from there.
That way you are only capturing the actual app install and not the dependancies.
Posted by:
cdupuis
20 years ago
The DotNet should have some sort of check to make sure it is not installed prior to it installing. I would deploy dotnet first in it's own package, which is quite easy, then on your reference machine, install dot net through what ever deploy methood you are using, then run a snapshot, then install the APP, you should see it now not even install the dotnet (the built in check should allow this). End capture and voila. Still might not work but worth a try. Remember to reboot after the dotnet install.
Posted by:
oofemioo
20 years ago
I've had problems with this same osrt of package. The dotNet still installs despite the availability of the doNet on your local system.
The best way to go about this is to install dotNet and then start your own installation.
You will still capture some dot Net components but this will be reduced to the barest minimum.
The best way to go about this is to install dotNet and then start your own installation.
You will still capture some dot Net components but this will be reduced to the barest minimum.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
