/build/static/layout/Breadcrumb_cap_w.png

removing MDAC 2.7 SP1 AND .NET Framework SP1 v1.14322

hi am repackaging am app called Info Pak

the application attempts to install MDAC and the .Net framework

can anyone please give me pointers on where to remove the references to the mdac and .net framework in the the package

0 Comments   [ + ] Show comments

Answers (3)

Posted by: nheim 17 years ago
10th Degree Black Belt
0
Hi cygan,
this is probably done with Custom Actions.
Fire up your MSI File in ORCA and have a look at the 'Custom Action' table.
If your lucky, the CA is self explanary and you can set a condition to it in the 'InstallExecuteSequence' table (maybe it is called in the 'InstallUISequence').
If this is not the case, please log the Installation and search for hints, when they are installed.
Are they installed also, if you are installing silently?
Regards, Nick
Posted by: dj_xest 17 years ago
5th Degree Black Belt
0
Hi Cygan,

nheim is right. They usually resides as a Custom Actions. But if you want to save time and avoid mistakes, you can first check them in your Redistributables in Installshield(Merge Modules). YOu will just need to uncheck the MDAC entries there and you can see that entries of MDAC in Custom Actions and other sections will also be removed.

Not sure with .NET framework if found as Merge MOdule but you can look for it in your CA.

You're doing a TRANSFORMS right?

Hope this help..
Posted by: cygan 17 years ago
Fifth Degree Brown Belt
0
great thanks a lot guys for the quick response

will have a look and let you know
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ