date:20071114

Re: [WiX-users] empty feature tree in maintenance mode

2007-11-14 Thread Sedgar


Hi all, as Stefan sad me in private mail: ghosts from the past is back!
I had same problem with maintenance mode, but with Stefan help I localize
and then found a reason of problem. It concealed in IsolateComponents
Action.

Quotation from  http://msdn2.microsoft.com/en-us/library/Aa369561.aspx  MSDN
:
This action must come after the CostInitialize action and before the
CostFinalize action.

Resolution (received from Stefan by mail) :

Stefan Battmer wrote:
 
 What solved the problem that time was reordering the install sequence. 
 The error occurred with this sequence:
 
 InstallUISequence
   Show Dialog=FatalErrorForm OnExit=error![CDATA[NOT 
 HideFatalErrorForm]]/Show
   Show Dialog=UserExitForm OnExit=cancel/
   Show Dialog=FinishedForm OnExit=success/
   Custom Action=ERRCA_UIANDADVERTISED 
 Before=AppSearch![CDATA[ProductState=1]]/Custom
   Custom Action=DIRCA_TARGETDIR 
 After=ValidateProductID![CDATA[TARGETDIR=]]/Custom
   Show Dialog=ResumeForm 
 After=IsolateComponents![CDATA[Installed= AND RESUME]]/Show
   Show Dialog=MaintenanceForm 
 After=ResumeForm![CDATA[Installed]]/Show
   Show Dialog=WelcomeForm 
 After=CostFinalize![CDATA[Installed= AND NOT RESUME]]/Show
   Show Dialog=ProgressForm After=WelcomeForm/
 /InstallUISequence
 
 After changing it like this everything was working fine:
 
 InstallUISequence
   Show Dialog=FatalErrorForm OnExit=error![CDATA[NOT 
 HideFatalErrorForm]]/Show
   Show Dialog=UserExitForm OnExit=cancel/
   Show Dialog=FinishedForm OnExit=success/
   Custom Action=ERRCA_UIANDADVERTISED 
 Before=AppSearch![CDATA[ProductState=1]]/Custom
   Custom Action=DIRCA_TARGETDIR 
 After=ValidateProductID![CDATA[TARGETDIR=]]/Custom
   Show Dialog=ResumeForm 
 After=MaintenanceForm![CDATA[Installed= AND RESUME]]/Show
   Show Dialog=MaintenanceForm 
 After=WelcomeForm![CDATA[Installed]]/Show
   Show Dialog=WelcomeForm 
 After=CostFinalize![CDATA[Installed= AND NOT RESUME]]/Show
   Show Dialog=ProgressForm After=WelcomeForm/
 /InstallUISequence
 

Resolution of problem in my case:

 InstallUISequence
Show Dialog=FatalErrorDlg OnExit=error /
Show Dialog=UserExitDlg OnExit=cancel /
Show Dialog=ExitDlg OnExit=success /
Show Dialog=WelcomeDlg
After=MigrateFeatureStates![CDATA[Installed=]]/Show
Show Dialog=WelcomeMaintenanceDlg
After=IsolateComponents![CDATA[Installed]]/Show
Show Dialog=ProgressDlg After=WelcomeDlg /
Show Dialog=PrepareDlg After=LaunchConditions /
  /InstallUISequence

Changed to

  InstallUISequence
Show Dialog=FatalErrorDlg OnExit=error /
Show Dialog=UserExitDlg OnExit=cancel /
Show Dialog=ExitDlg OnExit=success /
Show Dialog=WelcomeDlg
After=MigrateFeatureStates![CDATA[Installed=]]/Show
Show Dialog=WelcomeMaintenanceDlg
After=WelcomeDlg![CDATA[Installed]]/Show
Show Dialog=ProgressDlg After=WelcomeDlg /
Show Dialog=PrepareDlg After=LaunchConditions /
  /InstallUISequence




Stefan Battmer wrote:
 
 Hi everyone,
 
 I have checked this with Wix 2.0.2520 and .4013 so it's most likely a bug 
 in my installer source file. My setup in general runs fine. It 
 incorporates a feature tree in a customize dialog where the user is 
 allowed to select what he wants to install. Now when I display this very 
 same dialog as a reaction on the user pressing 'Modify' in the maintenance 
 form the feature tree in the customize Dlg. stays empty. I am unsure what 
 information you might need. This is some part of the GUI source. I hope 
 this is just something silly I oversee. Please let me know if you need 
 more information. Any help or suggestion would be very nice.
 
 Thanks,
 
 Stefan
 
 Dialog Id=MaintenanceForm Width=373 Height=287
 Title=[ProductName]
 Control Id=FinishButton Type=PushButton X=300
 Y=261 Width=66 Height=18 Default=yes
 Text{\VSI_MS_Sans_Serif13.0_0_0}amp;Next/Text
 Publish Property=MODIFY
 Value=ALL![CDATA[MaintenanceForm_Action=Modify]]/Publish
 Publish Property=CustomizeForm_PrevArgs
 Value=MaintenanceForm![CDATA[1]]/Publish
 Publish Property=REINSTALL
 Value=ALL![CDATA[MaintenanceForm_Action=Repair]]/Publish
 Publish Event=Reinstall
 Value=ALL![CDATA[MaintenanceForm_Action=Repair]]/Publish
 Publish Property=REMOVE
 Value=ALL![CDATA[MaintenanceForm_Action=Remove]]/Publish
 Publish Event=Remove
 Value=ALL![CDATA[MaintenanceForm_Action=Remove]]/Publish
 Publish Event=EndDialog
 Value=Return![CDATA[(MaintenanceForm_Action=Repair) OR
 (MaintenanceForm_Action=Remove)]]/Publish
 !-- For some reason the customize tree stays
 empty when created via 
 maintenance --
 Publish Event=SpawnDialog

Re: [WiX-users] SelectionTree not showing the features to be installed!

2007-11-14 Thread Sedgar

Resolution found. Posted in neighbor topic:
http://www.nabble.com/empty-feature-tree-in-maintenance-mode-tf1650272.html#a13743269
Empty feature tree in maintenance mode

Sedgar wrote:

Hi.
Have same problem with visibility of features components in SelectionTree.
All fine at the first time of msi running.
But SelectionTree is empty after a product installed and I run
installation again for modify some compomets.
Any have idea about possible reasons of it?

Maintenance Welcome Dialog - Maintenance Type Dialog(Modify, Reinstall,
Remove) - Custom Setup Dialog(SelectionTree control with features) -
...

Sebastian Brand-2 wrote:

Also make sure the Feature's Level attribute is not set to 0.

Best regards,
Sebastian Brand

Instyler Software - http://www.instyler.com

On Oct 30, 2007, at 2:29 , Richard wrote:

In article
[EMAIL PROTECTED],
Sajo Jacob [EMAIL PROTECTED] writes:

I have defined all my features with Display='expand' and
AllowAdvertise=yes with the appropriate components refs but still
don't
see the features on the selectiontree. It in fact shows a 2 level
tree with
no names to the features, something is definitely not right here
since I
have more than 2 features. Am I missing something here?

Open the MSI in Orca and look at the Feature table to ensure that
everything is populated correctly.
--
The Direct3D Graphics Pipeline -- DirectX 9 draft available for
download
http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a
browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
View this message in context:
http://www.nabble.com/SelectionTree-not-showing-the-features-to-be-installed%21-tf4715585.html#a13743336
Sent from the wix-users mailing list archive at Nabble.com.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] capturing errors from deployment using octopusCLI

2007-11-14 Thread Chandra Mohan

Just to set the context right, we are using xml2iis (an vbscript utility) to 
create the website as the WIX iis:WebSite doesn't support all the IIS 
properties we intend to set. This xml2iis utility gets called in a custom 
action of the MSI.
Question still holds good - how do we get the octopuscli to return the error 
when the custom action fails.

Thanks,
Chandra

From: Pierson Lee (Volt)
Sent: Wednesday, November 14, 2007 5:23 AM
To: wix-users@lists.sourceforge.net
Cc: Michael Thurlkill; Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI

Forwarding to WiX list

Does anyone know how to fail an MSI install with an error code if the website 
fails to be installed/configured? I was think of Windows Service and thought 
there was a way to do the iis:WebSite also but there doesn't seem to be.

Any help is appreciated.

Thanks
Pierson

From: Michael Thurlkill
Sent: Tuesday, November 13, 2007 3:46 PM
To: Pierson Lee (Volt); Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI

We're using Wix.  Chandra did most of the work, but I know just enough to be 
dangerous.

From: Pierson Lee (Volt)
Sent: Tuesday, November 13, 2007 3:43 PM
To: Michael Thurlkill; Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI

Are you creating your MSIs through WiX or using something else?

From: Michael Thurlkill
Sent: Tuesday, November 13, 2007 3:38 PM
To: Pierson Lee (Volt); Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI

So, how do you do that?
Chandra, you probably know more about this than I do.   Can you help work out 
how to get the error code out of the msi and octopus?

From: Pierson Lee (Volt)
Sent: Friday, November 09, 2007 6:14 PM
To: Michael Thurlkill
Subject: RE: capturing errors from deployment using octopusCLI

I think you need to mark it critical in your MSI so the MSI install fails if it 
can't install the site. That's what I did to get Octopus to error

From: Michael Thurlkill
Sent: Friday, November 09, 2007 6:13 PM
To: Pierson Lee (Volt)
Subject: RE: capturing errors from deployment using octopusCLI

Yes.  I can see the errors from the msi in the octopus log.  I just don't 
appear to get an errorcode out of octopus.

From: Pierson Lee (Volt)
Sent: Friday, November 09, 2007 5:55 PM
To: Michael Thurlkill; Octopus Discussions
Subject: RE: capturing errors from deployment using octopusCLI

Are you deploying the website through an MSI?

From: Michael Thurlkill
Sent: Friday, November 09, 2007 12:25 PM
To: Michael Thurlkill; Octopus Discussions
Subject: RE: capturing errors from deployment using octopusCLI

Does anyone deploy websites using Octopus?

From: Michael Thurlkill
Sent: Thursday, November 08, 2007 4:39 PM
To: Octopus Discussions
Subject: capturing errors from deployment using octopusCLI

We are using octopuscli in an automated job to deploy a webapp to several web 
servers.
If it is unable to deploy to one or more servers we would like to know and 
return failure for the job.
I'm not seeing a way to do this other than parsing the logs to look for errors.
Is there a way to cause octopus to return an error code?
How are other teams dealing with this kind of scenario?

Thanks
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Enable Wix3 Custom Action Trace

2007-11-14 Thread Mark Allanson

Just wondering how I can go about enabling trace from WiX custom actions.
The perf counter install is failing without letting me know why (other than
the standard windows installer error 1723, a DLL count not be run). I have
had a look through the wix CA code, and can see it uses standard
OutputDebugStringA, but can't see any trace output.

I can see the checks at the top to ensure the trace level is set correctly.
How do I go about setting the trace level correctly so I can see the debug
output?

Just FYI, a snippet of my code for installing the performance counter is as
follows.

!-- Queueing Related performance counters --
Component Id=QueuingPerformanceCounters
Guid=1643532C-75E0-4769-901F-1C01C17B494C Directory=CoreBinaries
CreateFolder Directory=CoreBinaries /
util:PerformanceCategory Id=QPC
  DefaultLanguage=english
  Name=Queuing System
  MultiInstance=no
  Help=Measures statistics about the
queuing system.
  Library=netfxperf.dll
  Open=OpenPerformanceData
  Close=ClosePerformanceData
  Collect=CollectPerformanceData

util:PerformanceCounter Name=Messages Read/sec
Type=rateOfCountsPerSecond32 /
util:PerformanceCounter Name=Total Messages Read
Type=numberOfItems32 /
/util:PerformanceCategory
/Component

Anything wrong in there?

Cheers,

Mark
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

42 matches

Mail list logo