Opened 10 years ago

Closed 10 years ago

#911 closed defect (fixed)

Installer: install rolls back on systems without MFC installed, even with MSMs

Reported by: jbirch Owned by:
Priority: medium Milestone: 2.1
Component: Installer Version:
Severity: critical Keywords:
Cc: jng External ID:

Description

I believe that this is because the MSMs are not yet fully installed when the custom actions need them. One approach is to run the custom actions deferred, but at that point they no longer have the installation path available to them. Another approach is to static-link MFC into the custom action DLLs.

I've attached a patch which I believe accomplishes the latter, and allows an install to complete on a clean Windows 2003 machine. It would be great if someone else could test this...

Attachments (1)

mapguide_installer.patch (2.5 KB) - added by jbirch 10 years ago.

Download all attachments as: .zip

Change History (5)

Changed 10 years ago by jbirch

Attachment: mapguide_installer.patch added

comment:1 Changed 10 years ago by jbirch

By applying this patch and then removing the code that adds the MFC MSM (leaving the CRT MSM in place), I was able to get installers to work correctly on clean machines, and also remove about 10Mb from the installer.

I think the MFC install may have been conflicting with the CRT install, because before I removed the MFC MSM I had to manually install the VC2008 SP1 runtime to get the server service to start.

comment:2 Changed 10 years ago by jng

Applied patch in r3741, removed MFC msm in r3742

comment:3 Changed 10 years ago by jng

The NSIS-driven bootstrapper package in r3748 should fix this

comment:4 Changed 10 years ago by jbirch

Resolution: fixed
Status: newclosed

yes, it does :)

Note: See TracTickets for help on using tickets.