Launching Redistrib. exe from installation
G'Day All,
Just a quick one; I'm trying to launch a vendor supplied MS redistrib. from an installation vcredist_x86.exe and I'm having trouble launching this from a CA.
I've tried the standard type 18 and 51. I'm placing it after the InstallFinalize. Any advice appreciated.
I suppose I could just insert it from the MM. I haven't had much joy with MM lately esp the SQL ones, so a little reluctant to utilise this in case of further complications.
Regards
Wayne
Just a quick one; I'm trying to launch a vendor supplied MS redistrib. from an installation vcredist_x86.exe and I'm having trouble launching this from a CA.
I've tried the standard type 18 and 51. I'm placing it after the InstallFinalize. Any advice appreciated.
I suppose I could just insert it from the MM. I haven't had much joy with MM lately esp the SQL ones, so a little reluctant to utilise this in case of further complications.
Regards
Wayne
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
WayneB
17 years ago
Update:
I think I'm going to try the latest MM for Visual C runtimes. I've had to get the latest VS2005 SP1 installation as the SP1 MM for VC fixes bugs that were in the first release relating to WI 3.0 and earlier, and besides they didn't register for me. So doing the laborious upgrade to VS2005 (there is something to be said about overheads Mr MS [:@]) just to get the 2 MM required.
Just as well I'm working tomorrow anyway[;)]. Luv working with quality apps [8D]
Regards
Wayne
I think I'm going to try the latest MM for Visual C runtimes. I've had to get the latest VS2005 SP1 installation as the SP1 MM for VC fixes bugs that were in the first release relating to WI 3.0 and earlier, and besides they didn't register for me. So doing the laborious upgrade to VS2005 (there is something to be said about overheads Mr MS [:@]) just to get the 2 MM required.
Just as well I'm working tomorrow anyway[;)]. Luv working with quality apps [8D]
Regards
Wayne
Posted by:
anonymous_9363
17 years ago
I went that route for .Net Framework 2.0 in trying to get it installed per-user, precisely because of that issue with the VC runtime call-out. Trying to match the MM names in the .Net MSI with the VS MM names proved to be a major headache: I lost count of the number of admin installs I did trying to decipher what MM did what. In the end, I managed to persuade the client that .Net F/W is one of those 'applications' which should be an exception from their "All apps will be installed per-user" dictat.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.