Opened 10 years ago

Closed 10 years ago

#943 closed defect (fixed)

Unable to complete "IIS Configuration" or "Manual Configuration" if IIS is not installed

Reported by: pielera Owned by: jbirch
Priority: high Milestone: 2.1
Component: Installer Version: 2.1.0
Severity: trivial Keywords:
Cc: External ID:

Description

In "IIS Configuration"/"Manual Configuration" after selecting "PHP"/".NET" the "next"-button does not work. I am not able to finish the installation in either of these two configurations if IIS is not installed.

Maybe there could be a message that IIS must be installed before installing MapGuide Open Source... for the people who don't know what they are doing.

Change History (14)

comment:1 Changed 10 years ago by jng

Milestone: 2.1
Owner: set to jng
Priority: lowhigh

I'm sure there's a way to prevent certain

comment:2 Changed 10 years ago by jng

I'm sure there's a way to prevent certain paths from being taken through the installation process.

comment:3 Changed 10 years ago by jng

Status: newassigned

comment:4 Changed 10 years ago by jng

Resolution: fixed
Status: assignedclosed

Fixed in r3807

comment:5 Changed 10 years ago by jbirch

I wonder if it would make more sense to modify the NoDotNet dialog to be something like a MissingPrerequisites dialog, and have two text sections (.Net 2.0 not detected, ASP.Net Web Server Extensions will not be available; IIS not detected, IIS integration will not be available).

The condition for this dialog would be something like:

IISVERSIONMAJOR = "#0" OR NOT NETFRAMEWORK20

Then, within the WebServerConfigDlg have a choice of two controls containing RadioButtonGroups, the first one (giving IIS option) containing a condition like:

<Condition Action="show">NOT IISVERSIONMAJOR = "#0"</Condition>

And the second one (not giving IIS option) containing a condition like

<Condition Action="show">IISVERSIONMAJOR = "#0"</Condition>

comment:6 Changed 10 years ago by jbirch

Oh, and there'd be conditional controls in the MissingPrerequisites dialog too...

comment:7 Changed 10 years ago by jng

My motivation for having two separate dialogs is this:

1) If I do not have IIS installed, then the IIS configuration is NOT a valid option. If they do select IIS configuration then its go back or get out.

2) If I do not have .net installed, I can still go ahead with any configuration without any issues. If they choose to install the .net viewer, then it just won't be configured for asp.net 2.0

You can't really do both through a single dialog. Of course I am using this approach because manipulating the dialog UI with Wix/MSI is an extreme PITA!

comment:8 Changed 10 years ago by jbirch

Yeah, I was thinking that if you put both warnings (IIS/.Net) on the same screen, and then didn't even make the IIS choice available on the next screen, users wouldn't even have the option to choose IIS and get confused.

Any objection to me playing around with this?

comment:9 Changed 10 years ago by jng

If you can make it work, go for it. There's always "svn revert" :-)

comment:10 Changed 10 years ago by jbirch

Resolution: fixed
Status: closedreopened

comment:11 Changed 10 years ago by jbirch

Owner: changed from jng to jbirch
Status: reopenednew

comment:12 Changed 10 years ago by jbirch

Status: newassigned

comment:13 Changed 10 years ago by jbirch

Some changes made in r3811 Not done yet, but should be functionally complete.

comment:14 Changed 10 years ago by jbirch

Resolution: fixed
Status: assignedclosed

Finished in r3812

Note: See TracTickets for help on using tickets.