This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: MS VS2005 Redistributables Merge Modules not really working on Vista?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2007
01:13 PM
MS VS2005 Redistributables Merge Modules not really working on Vista?
We have an install where we need to install Visual C++ 8.0 ATL (x86) WinXSX MSM (and x64) on Windows Vista in order to be able to register a component of ours.
This fails every time on Vista. On XP and Windows 2003 this works, but on Vista it seems that the C++ libraries are never installed before the dll is registered.
Has anyone seen this? Any ideas on how to fix it?
I have added the MS VS Redist setup and launched it as a custom action during installation with success, but this does not work when/if I run our installer silently saying that another installer is already running and ending.
Thanks,
Dan
This fails every time on Vista. On XP and Windows 2003 this works, but on Vista it seems that the C++ libraries are never installed before the dll is registered.
Has anyone seen this? Any ideas on how to fix it?
I have added the MS VS Redist setup and launched it as a custom action during installation with success, but this does not work when/if I run our installer silently saying that another installer is already running and ending.
Thanks,
Dan
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2007
01:36 PM
Dan,
we ran into the same problem. Check out the article below which explains this.
http://blogs.msdn.com/astebner/archive/2007/01/09/problems-with-custom-actions-that-depend-on-the-visual-c-8-0-runtime-files-on-windows-vista.aspx.
we ended up having to extract the COM at build time, but that is not reliable either because the com extractor inside isntallshield doesnt pick up every COM info in our dlls.
yann
we ran into the same problem. Check out the article below which explains this.
http://blogs.msdn.com/astebner/archive/2007/01/09/problems-with-custom-actions-that-depend-on-the-visual-c-8-0-runtime-files-on-windows-vista.aspx.
we ended up having to extract the COM at build time, but that is not reliable either because the com extractor inside isntallshield doesnt pick up every COM info in our dlls.
yann
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2007
01:51 PM
Thanks Yann! That helps a lot...
Dan
Dan
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)