[mapguide-internals] About the WiX installer

[Jackie Ng]

Update time:

1. I've added the IIS and IIS7 custom actions supplied by Autodesk. IIS7
custom actions has not been integrated into the installer yet.

2. You should now be able to have an IIS-specific configuration and a
Apache-specific configuration. If you msiexec the installer from the
command-line setting MGWEB_CONFIG=IIS|APACHE, you should get certain
features enabled and disabled. eg. If MGWEB_CONFIG=IIS, the apache web
server will be disabled. This means we should now be able to toggle this
value (and the affected features) via a custom dialog (yet to be done).

3. IIS configuration is slightly better than Apache. With IIS, php works and
the mapagent works, but only through mapagent.exe (ie.
http://localhost/mapguide/mapagent/mapagent.exe?OPERATION=...). The
isapi_mapagent.dll handler seems to be properly mapped, but does nothing. I
get login failed with Site Administrator.

4. Fixed a small issue with php.ini, there was a bug in the templating of
the file, resulting in a bogus php extension path. Also the installer now
writes the PHP path to the registry so it now knows where to look for
php.ini

The pressing issues at hand:

1. The mapagent. I can't find out if it works for Apache because it cannot
load mod_mgmapagent.so and it is only working in IIS if you are using the
executable (mapagent.exe) in your mapagent calls. 

I have a small theory about why it won't load on Apache. Maybe it is because
the mod_mgmapagent.so module was built with Visual Studio 2008, but the
Apache web server binaries may have been built with something else? Would
this make the apache module incompatible?

- Jackie
-- 
View this message in context: http://n2.nabble.com/About-the-WiX-installer-tp2339047p2454788.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.