Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

VC++ 2008 SP1 MFC Security Update v9.0.30729.6161


3 replies to this topic

Superfreak3

Superfreak3
  • Full Members
  • 437 posts

Posted 10 December 2012 - 14:44

Hi all,

A third party app we use now requires v9.0.30729.6161 of the VC++ 2008 Runtime. We currently have an earlier version included in a repackaged installation via Merge Module.

I was wondering if anyone knows if there are Modules available for v9.0.30729.6161.

I tried installing VS 2008 on a VM with all the latest updates applied afterwards, but the Modules were not updated. Applying the version specific vcredist .exe didn't update them either.

I guess if I can't find modules I'll have to simply chain the vcredist to the current install. I'm then wondering if this redist...

http://www.microsoft...s.aspx?id=26368

... is the complete runtime or just some changes for the MFC update. In other words, I wonder if I can remove the current VC++ 2008 Merge Modules I'm using and simply install the runtime via this .exe.

Any information on either locating Modules or, if none available, whether the .exe will suffice in installing the complete, required runtime would be greatly appreciated!

Thanks Much!!

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 11 December 2012 - 16:02

It's probably better to use the redist.exe (e.g. as a Prerequisite) instead of the merge module, to avoid problems like this:
http://msmvps.com/bl...er-updates.aspx

Superfreak3

Superfreak3
  • Full Members
  • 437 posts

Posted 17 December 2012 - 03:29

We don't bootstrap the prerequisites for this particular installation, but I guess I could still call the redist from the .msi.

VBScab

VBScab
  • Full Members
  • 436 posts

Posted 17 December 2012 - 11:15

In your shoes. I'd simply build a new MM and add it to a new version of the main package (for new deployments) and deploy it as a separate MSI (for existing deployments).
- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.