[WiX-users] Reverse engineered VS2003 MSI

2008-04-08 Thread Christopher Butcher
Hi guys

 

I've run DARK on a VS2003 MSI for a Web Service.

 

Using the WXS generated I've built a new MSI using CANDLE and LIGHT.

 

On first attempt it didn't work. 

 

I discovered that it would work when I removed the following three lines
and then massaged the InstallExecutionSequence to cope with their
disappearance.

 

CustomAction Id=WEBCA_GatherWebFolderProperties Return=check
BinaryKey=MSVBDPCADLL DllEntry=GatherWebFolderProperties /

CustomAction Id=WEBCA_ApplyWebFolderProperties Return=check
Execute=commit BinaryKey=MSVBDPCADLL
DllEntry=ApplyWebFolderProperties /

CustomAction Id=WEBCA_RollbackApplyWebFolderProperties
Return=check Execute=rollback BinaryKey=MSVBDPCADLL
DllEntry=RollbackApplyWebFolderProperties /

 

Build the MSI - it installs ok.

 

However...

 

It does not set the default document for the web application.

 

The custom table entry appears to be correct;

 

CustomTable Id=_IISProperties

  Column Id=Directory_ Type=string Width=72 PrimaryKey=yes
/

  Column Id=Attributes Type=int Width=2 /

  Column Id=DefaultDoc Nullable=yes Type=string Width=255
/

  Row

Data Column=Directory_![CDATA[TARGETDIR]]/Data

Data Column=Attributes![CDATA[594]]/Data

Data Column=DefaultDoc![CDATA[MyWebService.asmx]]/Data

  /Row

/CustomTable

CustomTable Id=_VDirToUrl

...

/CustomTable

CustomTable Id=_UrlToDir

...

/CustomTable

CustomTable Id=_AppRootCreate

..

/CustomTable

CustomTable Id=_VsdLaunchCondition

...

/CustomTable

 

But it just won't set.

 

I could understand how the removal of the 3 custom actions above might
be causing this. But to be honest, unless I remove them, the MSI won't
run successfully.

 

I've read lots of mini-guides explaining to use WebSite, WebVirtualDir
and WebApplication. But they are all for WXS scripts started from
scratch. I'm trying to modify this VS2003 MSI so that I can preserve the
basic UI it already has in place.

 

Does anyone else have any experience of building customised WIX scripts
based on WXS extracted by DARK from VS2003 MSI's?

 

Krs

Chris

 


Disclaimer of IDOX Group plc (IDOX)

This e-mail and any attachments are confidential, may be privileged and are 
intended solely for the use of the intended recipient/s. If you are not an 
intended recipient, please (a) notify the sender immediately, copying [EMAIL 
PROTECTED] as appropriate; and (b) delete the original e-mail and your reply 
from your system. Unless authorized by IDOX, copying, forwarding, disclosing or 
using this e-mail is prohibited. No liability is accepted for damage caused by 
the presence of any virus. The contents of this e-mail are provided subject to 
contract. Views or opinions in this e-mail are those of the author and not 
necessarily those of IDOX. IDOX may intercept, copy or monitor e-mails from or 
to anyone using its facilities in accordance with the law. 


-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] ServiceInstall and ServiceControl

2008-03-28 Thread Christopher Butcher
Thanks Bob

 

I've done a registry search for the GUIDs used in the WXS file, but no
entries in the registry.

 

How would you suggest exploring where the component is shared, or how do
you identify component rules violations?

 

Krs

Chris

 



From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 27 March 2008 14:38
To: Christopher Butcher
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ServiceInstall and ServiceControl

 

Christopher Butcher wrote: 

The service does uninstall, the files are deleted by the MSI ok. It's
just that whatever registry entries which enable the service to appear
in SERVICES.MSC are left in place. If I delete them manually and then
reboot then the service is removed from SERVICES.MSC. But surely you
shouldn't need to do that. I have seen MSI's gracefully remove services
completely - why would this one be acting so ungraceful?

 

Action start 21:01:24: InstallValidate.

MSI (s) (CC:1C) [21:01:24:890]: Feature: DefaultFeature; Installed:
Local;   Request: Absent;   Action: Absent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_SERVICEEXE; Installed:
Local;   Request: Absent;   Action: FileAbsent


The FileAbsent action indicates that the component is shared with
another product installed in a different directory. If that's not the
case, you likely have a component rules violation between different
products over time.




-- 
sig://boB
http://joyofsetup.com/

Disclaimer of IDOX Group plc (IDOX)

This e-mail and any attachments are confidential, may be privileged and are 
intended solely for the use of the intended recipient/s. If you are not an 
intended recipient, please (a) notify the sender immediately, copying [EMAIL 
PROTECTED] as appropriate; and (b) delete the original e-mail and your reply 
from your system. Unless authorized by IDOX, copying, forwarding, disclosing or 
using this e-mail is prohibited. No liability is accepted for damage caused by 
the presence of any virus. The contents of this e-mail are provided subject to 
contract. Views or opinions in this e-mail are those of the author and not 
necessarily those of IDOX. IDOX may intercept, copy or monitor e-mails from or 
to anyone using its facilities in accordance with the law. 


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] ServiceInstall and ServiceControl

2008-03-26 Thread Christopher Butcher
Hi Bob

 

Turned on the verbose logging. InstallValidate section is listed below.

 

The service does uninstall, the files are deleted by the MSI ok. It's
just that whatever registry entries which enable the service to appear
in SERVICES.MSC are left in place. If I delete them manually and then
reboot then the service is removed from SERVICES.MSC. But surely you
shouldn't need to do that. I have seen MSI's gracefully remove services
completely - why would this one be acting so ungraceful?

 

Action start 21:01:24: InstallValidate.

MSI (s) (CC:1C) [21:01:24:890]: Feature: DefaultFeature; Installed:
Local;   Request: Absent;   Action: Absent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_SERVICEEXE; Installed:
Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_CREATEDOCDIR; Installed:
Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_CREATELOGSDIR; Installed:
Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_CREATECONSOLEDIR;
Installed: Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_CREATESERVICEDIR;
Installed: Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_SQL; Installed: Local;
Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_UFWEB; Installed: Local;
Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_DOCUMENTS; Installed:
Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_LOG4NET; Installed: Local;
Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_README; Installed: Local;
Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_CONSOLEEXE; Installed:
Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Component: C_CONSOLEICON; Installed:
Local;   Request: Absent;   Action: FileAbsent

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: Registry 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: BindImage 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: ProgId 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: PublishComponent 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: SelfReg 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: Extension 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: Font 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: Shortcut 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: Class 

MSI (s) (CC:1C) [21:01:24:890]: Note: 1: 2205 2:  3: _RemoveFilePath 

MSI (s) (CC:1C) [21:01:25:015]: PROPERTY CHANGE: Modifying
CostingComplete property. Its current value is '0'. Its new value: '1'.

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: Registry 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: BindImage 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: ProgId 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: PublishComponent 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: SelfReg 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: Extension 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: Font 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: Shortcut 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2205 2:  3: Class 

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2727 2:  

MSI (s) (CC:1C) [21:01:25:015]: Note: 1: 2727 2:  

Action ended 21:01:25: InstallValidate. Return value 1.

 



From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 26 March 2008 03:22
To: Christopher Butcher
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ServiceInstall and ServiceControl

 

Christopher Butcher wrote: 

The installation runs through fine and installs, the oddity comes after
uninstalling.

 

The MSI runs fine and says it has uninstalled.

 

But when you check the Services panel, your service is still there.


Create a verbose log and check the InstallValidate logging to make sure
the service component is being uninstalled.



-- 
sig://boB
http://joyofsetup.com/

Disclaimer of IDOX Group plc (IDOX)

This e-mail and any attachments are confidential, may be privileged and are 
intended solely for the use of the intended recipient/s. If you are not an 
intended recipient, please (a) notify the sender immediately, copying [EMAIL 
PROTECTED] as appropriate; and (b) delete the original e-mail and your reply 
from your system. Unless authorized by IDOX, copying, forwarding, disclosing or 
using this e-mail is prohibited. No liability is accepted for damage caused by 
the presence of any virus. The contents of this e-mail are provided subject to 
contract. Views or opinions in this e-mail are those of the author and not 
necessarily those of IDOX. IDOX may intercept, copy or monitor e-mails from or 
to anyone using its facilities in accordance with the law

[WiX-users] ServiceInstall and ServiceControl

2008-03-25 Thread Christopher Butcher
Hi Guys

 

I'm experiencing an odd behaviour when using ServiceInstall and
ServiceControl.

 

  Component Id=C_SERVICEEXE
Guid=90362226-CBC6-8A2A-9D2C-6D3B922B0F15 Location=local

File Id=SERVICEEXE Name=SERVCLNT.EXE
LongName=SDService.exe Vital=yes KeyPath=yes DiskId=1
Source=..\SDService.exe /

ServiceControl Id=SERVICEEXE Name=Super Duper Service
Stop=both Wait=yes Remove=both /

ServiceInstall Id=SERVICEEXE Name=Super Duper Service
Vital=yes DisplayName=Super Duper Service Type=ownProcess
Start=auto ErrorControl=normal Description=My Super Duper Service
description /

File Id=SERVICECONFIG Name=SERVCLNT.CFG
LongName=SDService.exe.config DiskId=1 CompanionFile=SERVICEEXE
Source=..\SDService.exe.config /

  /Component

 

The installation runs through fine and installs, the oddity comes after
uninstalling.

 

The MSI runs fine and says it has uninstalled.

 

But when you check the Services panel, your service is still there.

 

Checking REGEDIT, you can still see the entries in
HKLM\SYSTEM\CurrentControlSet\Services.

 

Has anyone experienced this, and found a solution?

 

Krs

Chris

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Building a Web App MSI for VS 2003

2008-03-11 Thread Christopher Butcher
Trying to build a WIX install to run with CruiseControl.

 

I built an MSI from VS2003 for a Web App solution.

 

Then ran DARK on it, run CANDLE and LIGHT and builds a new MSI fine.

 

But when you run the MSI, asks for target folder, accepts, starts
install, then fails.

 

Digging inside, the error log shows...

 

Action start 13:44:12: CreateFolders.

CreateFolders: Folder: Creating folders

Action ended 13:44:12: CreateFolders. Return value 1.

Action 13:44:12: WEBCA_GatherWebFolderProperties. 

Action start 13:44:12: WEBCA_GatherWebFolderProperties.

DEBUG: Error 2769:  Custom Action WEBCA_GatherWebFolderProperties did
not close 1 MSIHANDLEs.

The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2769. The arguments are: WEBCA_GatherWebFolderProperties, 1, 

Action ended 13:44:12: WEBCA_GatherWebFolderProperties. Return value 3.

Action ended 13:44:12: INSTALL. Return value 3.

Action ended 13:44:12: ExecuteAction. Return value 3.

Action 13:44:12: FatalErrorForm. 

Action start 13:44:12: FatalErrorForm.

Action 13:44:12: FatalErrorForm. Dialog created

Action ended 13:44:14: FatalErrorForm. Return value 1.

Action ended 13:44:14: INSTALL. Return value 3.

 

What is the problem with GatherWebFolderProperties.

 

Inside the WXS the custom action is defined as...

 

CustomAction Id=WEBCA_GatherWebFolderProperties Return=check
BinaryKey=MSVBDPCADLL DllEntry=GatherWebFolderProperties /

 

 

Has anyone experienced similar problems, or have a better approach to
this?

 

 

 

Chris Butcher 



 


Disclaimer of IDOX Group plc (IDOX)

This e-mail and any attachments are confidential, may be privileged and are 
intended solely for the use of the intended recipient/s. If you are not an 
intended recipient, please (a) notify the sender immediately, copying [EMAIL 
PROTECTED] as appropriate; and (b) delete the original e-mail and your reply 
from your system. Unless authorized by IDOX, copying, forwarding, disclosing or 
using this e-mail is prohibited. No liability is accepted for damage caused by 
the presence of any virus. The contents of this e-mail are provided subject to 
contract. Views or opinions in this e-mail are those of the author and not 
necessarily those of IDOX. IDOX may intercept, copy or monitor e-mails from or 
to anyone using its facilities in accordance with the law. 


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users