Re: [WiX-users] Help on Service

2008-01-11 Thread Meyrignac, Jean-Charles
Trying to guess, since the description of your problem is very poor...

The problem is easy to locate: run the installer. When you get your error 
message, check if Service.exe has been copied.
If it is not the case, remove the attribute Assembly=.net on your File 
entry.


JC

-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Anidil
Envoyé : vendredi 11 janvier 2008 08:08
À : wix-users@lists.sourceforge.net
Objet : Re: [WiX-users] Help on Service



I get the following error message:
Service 'service.exe' ('service.exe') failed to start.Verify that you have
sufficient privileges to start system services

I'm logged in as Admin user




-
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] Help on Service

2008-01-11 Thread Anidil


I see that the service.exe has been copied and registered under windows
service console.but it doesn't start automatically.I get the following
message when tried starting manually.Windows could not start the service on
Local Computer. Error 1053: The service did not respond to the start or
control request in a timely fashion.

Is this somethig to do with the service.exe? While using the installshield
installer, we have passed the /RegServer to a standalone
ExecuteProcess.exe to register the service.exe.

here are the snip of the wix code

Component Id=InstallService
Guid={A217EE94-F719-47c4-BEE0-28FDF944CD5C}
  File Id=EXECUTEPROCESS Name=ExecProc.exe
Source=ExecuteProcess.exe DiskId=1 KeyPath=yes DefaultSize=7121522
DefaultVersion=4.3.0.0.1170.S  / 
 File Id=EXECUTABLE1 DiskId=1 LongName=service.exe
Name=service.exe Source=service.exe DefaultSize=1017 / 
ServiceInstall Id=RegisterService Name=ExecProc 
DisplayName=ABCD
Service  Type=ownProcess Start=auto ErrorControl=normal
Description=Service Account=[SERVICEACCOUNT] Password=[SERVICEPASSWORD]
 /
  ServiceControl Id=StartService Name=service.exe 
Start=install Wait=no /
  ServiceControl Id=StopService Name=service.exe 
Stop=both Wait=yes Remove=uninstall / 
/Component



Meyrignac, Jean-Charles wrote:
 
 Trying to guess, since the description of your problem is very poor...
 
 The problem is easy to locate: run the installer. When you get your error
 message, check if Service.exe has been copied.
 If it is not the case, remove the attribute Assembly=.net on your File
 entry.
 
 
 JC
 
 -Message d'origine-
 De : [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] De la part de Anidil
 Envoyé : vendredi 11 janvier 2008 08:08
 À : wix-users@lists.sourceforge.net
 Objet : Re: [WiX-users] Help on Service
 
 
 
 I get the following error message:
 Service 'service.exe' ('service.exe') failed to start.Verify that you
 have
 sufficient privileges to start system services
 
 I'm logged in as Admin user
 
 
 
 
 -
 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
 
 

-- 
View this message in context: 
http://www.nabble.com/Help-on-Service-tp12774904p14752117.html
Sent from the wix-users mailing list archive at Nabble.com.


-
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] Help on Service

2008-01-11 Thread Meyrignac, Jean-Charles
You should put Wait=yes during StartService, since your service seems to take 
some time to start.

JC

-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Anidil
Envoyé : vendredi 11 janvier 2008 10:09
À : wix-users@lists.sourceforge.net
Objet : Re: [WiX-users] Help on Service



I see that the service.exe has been copied and registered under windows
service console.but it doesn't start automatically.I get the following
message when tried starting manually.Windows could not start the service on
Local Computer. Error 1053: The service did not respond to the start or
control request in a timely fashion.

Is this somethig to do with the service.exe? While using the installshield
installer, we have passed the /RegServer to a standalone
ExecuteProcess.exe to register the service.exe.

here are the snip of the wix code

Component Id=InstallService
Guid={A217EE94-F719-47c4-BEE0-28FDF944CD5C}
  File Id=EXECUTEPROCESS Name=ExecProc.exe
Source=ExecuteProcess.exe DiskId=1 KeyPath=yes DefaultSize=7121522
DefaultVersion=4.3.0.0.1170.S  / 
 File Id=EXECUTABLE1 DiskId=1 LongName=service.exe
Name=service.exe Source=service.exe DefaultSize=1017 / 
ServiceInstall Id=RegisterService Name=ExecProc 
DisplayName=ABCD
Service  Type=ownProcess Start=auto ErrorControl=normal
Description=Service Account=[SERVICEACCOUNT] Password=[SERVICEPASSWORD]
 /
  ServiceControl Id=StartService Name=service.exe 
Start=install Wait=no /
  ServiceControl Id=StopService Name=service.exe 
Stop=both Wait=yes Remove=uninstall / 
/Component


-
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


[WiX-users] Service Control Install

2008-01-11 Thread SaiTeja

Hi,

am creating one MSI for both 32  64 bit OS.

Except one component is different, remaining all binaries are same for both
OS

GuardSvc32.exe for 32 bit OS and GuardSvc64.exe for 64 bit OS

Problems am facing now is

* On 32 bit OS, Service is started automatically after rebooting–
Stopping service is failing while uninstalling(GuardSvc32 couldn't be
stopped. Verify that you have sufficient privileges to stop system services)
* On 64 bit OS, Service is note starting automatically after rebooting –
Because of service is not started it is uninstalled properly.

I tried with wait = yes and even wait=no also in service control

Following is my wix code related to service control and service install

 Component Id=guardsvc32.exe
Guid={EB172BF4-C1F7-467F-89C3-A5B73F3E8B45} DiskId=1 Win64=no
  Condition((NOT VersionNT=500) AND (NOT VersionNT64))/Condition
  File Id=guardsvc32.exe Name=guards32.exe
LongName=guardsvc32.exe KeyPath=yes Source=guardsvc32.exe /
   ServiceInstall Id=NewServiceInstall1
Name=GuardSvc32
DisplayName=Test Machine Client Service
Type=ownProcess
Start=auto
ErrorControl=normal
Description=Enables the Test Machine Client. If
this service is stopped, Test Machine-protected content will be
unavailable.
Interactive=no Vital=yes
  ServiceDependency Id=EventLog/
  ServiceDependency Id=RpcSs /
  ServiceDependency Id=Dnscache /
  ServiceDependency Id=CryptSvc /
  ServiceDependency Id=TermService /
  /ServiceInstall
ServiceControl Id=Guardvc32Event Name=GuardSvc32
Stop=uninstall Remove=uninstall/
/Component

Component Id=guardsvc64.exe Guid={8D6F5BA9-DA8C-403F-8092-FD5A05616B2B}
DiskId=1 Win64=yes
  Condition((NOT VersionNT=500) AND (VersionNT64))/Condition   
File Id=guardsvc64.exe Name=grds64.exe
LongName=guardsvc64.exe KeyPath=yes Source=guardsvc64.exe /
   ServiceInstall Id=NewServiceInstall2
Name=GuardSvc64
DisplayName=Test Machine Client Service   
   
Type=ownProcess
Start=auto
ErrorControl=normal
Description=Enables the Test Machine Client. If
this service is stopped,Test Machine-protected content will be unavailable.
Interactive=no Vital=yes
  ServiceDependency Id=EventLog/
  ServiceDependency Id=RpcSs /
  ServiceDependency Id=Dnscache /
  ServiceDependency Id=CryptSvc /
  ServiceDependency Id=TermService /
/ServiceInstall
ServiceControl Id=Guardvc64Event Name=GuardSvc64
Stop=uninstall Remove=uninstall/
/Component 
-- 
View this message in context: 
http://www.nabble.com/Service-Control---Install-tp14753568p14753568.html
Sent from the wix-users mailing list archive at Nabble.com.


-
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] queries

2008-01-11 Thread Daniel Janz
To point 3: Have a look at this page
http://helpnet.installshield.com/robo/projects/helplibdevstudio9/IHelpPr
opReference.htm#OS

Look at the Version9X, VersionNT and VersionNT64-Properties.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of SaiTeja
Sent: Freitag, 11. Januar 2008 08:20
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] queries


Hi 

I have couple of queries. 

1) I have Install Custom actions and Uninstall Custom actions.

I have added Roll back for all custom actions

now my question is How do I find all my custom actions are working fine?

2) I want my MSI should work properly on VISTA OS also
For supporting this, what modifications should I have to take care.

3) How can we find OS type ie 32 bit or 64 bit OS while MSI running?
I want to set some property's depends on OS while MSI running?


-- 
View this message in context:
http://www.nabble.com/queries-tp14750959p14750959.html
Sent from the wix-users mailing list archive at Nabble.com.



-
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/marketp
lace
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
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] register file types and DLL

2008-01-11 Thread Don Tasanasanta (Volt)
Take a look at RegistryValue in the WiX help documentation.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lincoln Lavoie
Sent: Thursday, January 10, 2008 7:36 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] register file types and DLL

Hello All,

I'm new to using wix.  I'm trying to develop a relatively simple installer, but 
it does need to register one dll file and the file type used by the 
application.  Where can I find the documentation for this part of WiX.

Cheers,
Lincoln
-
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] Failed to create patch. error code:0x34

2008-01-11 Thread Crouch, John
I'll answer my own question.
 
The solution turns out to be not using the Win2003 Platform SDK patching
exe and Patchwiz.dll but to use the same items from the Microsoft
Windows SDK for Windows Vista and .NET Framework 3.0 here!
 
http://www.microsoft.com/downloads/details.aspx?FamilyId=C2B1E300-F358-4
523-B479-F53D234CDCCFdisplaylang=en
blocked::http://www.microsoft.com/downloads/details.aspx?FamilyId=C2B1E
300-F358-4523-B479-F53D234CDCCFdisplaylang=en .
 
Kind regards,
National Oilwell Varco

John Crouch
Software Engineer/Developer

National Oilwell Norway AS
Phone: +4751818181
Direct:  +4751217563
Fax: +4751800547
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 
www.nov.com http://www.nov.com/ 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Crouch,
John
Sent: Monday, December 10, 2007 12:36 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Failed to create patch. error code:0x34


Folks,
I'm getting the above error which translates into, The range offset in
the RetainOffsets field in the FamilyFileRanges Table
http://msdn2.microsoft.com/en-us/library/aa368575.aspx  is invalid. ,
I think.
 
Again, I think this means that the Patch Sequence - sequence attribute
is wrong but I don't know why.  Has anyone got a hint for me?
Wix and msimsp logfiles are below. Using Wix 3.0.2925.0
 
msimsp.log reads

* Log starting: 2007-12-10 11:31:46 *
 
Input-PCP path = '1.4.0_patch.pcp'
Patch-MSP path = '1.4.1_patch.msp'
Temp Folder=
'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\~PCW_TMP.TMP\'
Patch GUID =
'{44158ED1-8508-49D8-A611-2A24DA35F6E2}'
ListOfPatchGUIDsToReplace  = 'none'
ListOfTargetProductCodes   = '*'
PatchSourceList= 'blank'
AllowProductCodeMismatches = '0'
AllowProductVersionMajorMismatches = '0'
OptimizePatchSizeForLargeFiles = 'blank'
ApiPatchingSymbolFlags = 'blank'
MsiFileToUseToCreatePatchTables= 'blank'
SqlCmdToCreatePatchTable   = 'blank'
SqlCmdToCreatePatchPackageTable= 'blank'
SqlCmdToCreateMsiPatchHeadersTable = 'blank'
DontRemoveTempFolderWhenFinished   = '0'
IncludeWholeFilesOnly  = '1'
MinimumRequiredMsiVersion  = 'blank'
SEQUENCE_DATA_GENERATION_DISABLED  = 'blank'
AllowRemoval   = 'blank'
 
Using internal SQL cmd to create 'Patch' table.
Using internal SQL cmd to create 'PatchPackage' table.
Using internal SQL cmd to create 'MsiPatchHeaders' table.
 
WARNING (14): File versions are equal.  Upgraded:
'c:\NewInstall\files\.\PFiles\MY\MY Baby DAL WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe'
ver=1.0.0.0;  Target: 'c:\OldInstall\files\.\PFiles\MY\MY Baby DAL WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe'
ver=1.0.0.0.
 Files differ: 'c:\NewInstall\files\.\PFiles\MY\MY Baby DAL WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe',
   'c:\OldInstall\files\.\PFiles\MY\MY Baby DAL WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe'.
Patch API could not create a small patch; using whole upgraded file.
  Including entire file: 'c:\NewInstall\files\.\PFiles\MY\MY Baby DAL
WITS Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe';
   FTK=DALWITSfile4; temp location=MYFalcn\01010.FLE.
 Files differ: 'c:\NewInstall\files\.\PFiles\MY\MY Baby DAL WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe.config',
   'c:\OldInstall\files\.\PFiles\MY\MY Baby DAL WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe.config'.
Patch API could not create a small patch; using whole upgraded file.
  Including entire file: 'c:\NewInstall\files\.\PFiles\MY\MY Baby DAL
WITS
Service\bin\Release\MY.Baby.DataAccessLayer.WITSService.exe.config';
   FTK=WITSfile5; temp location=MYFalcn\01011.FLE.
 
* Log finishing: 2007-12-10 11:31:54 *
 
Patch WIX is
 
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
  ?define WixDir = . ?
  ?define Proj1 = c:\OldInstall\files ?
  ?define Proj2 = c:\NewInstall\files ? 
 
  PatchCreation 
 Id={44158ED1-8508-49d8-A611-2A24DA35F6E2}
   CleanWorkingFolder=yes
   OutputPath=Baby 1.4.0 - patch.pcp
   WholeFilesOnly=yes
   
 
PatchInformation
  Description=Patches the WITS Service/MDT Totco TIM box no
date and time issue 
  Comments=Patch for new exe and config
  ShortNames=no
  Languages=1033
  Compressed=yes
  Manufacturer=Mine/
 
PatchMetadata
  AllowRemoval=yes
  Description=Patches the andmagichappens.cmd file
  ManufacturerName=Mine
  TargetProductName=Baby
  Classification=Hotfix
  DisplayName=Baby 1.4 Patch 1.01/
 
  

[WiX-users] Removing a file

2008-01-11 Thread Graham Vickrage
As a newbie I am really struggling to do the simplest of tasks

I need to remove a shortcut left by an old application in the start menu 
  startup directory.

I have tried to define a directory (under the component) and add a 
removefile tag in the component. But this does not work. Any clues as I 
can't find a single example on that is doing anything similar.

Any help greatly appreciated.

Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder  Name='PFiles'
Directory Id='CourtneyThorne' Name='Courtney Thorne Ltd'
  Directory Id=INSTALLDIR Name=Call Manager 4.0

Component Id='MainExecutable' 
Guid='f83bbc21-952a-43d4-8055-da2bea58b891'
  File Id='CallManEXE' Name='Call Manager.exe' DiskId='1' 
Source='Call Manager.exe' Vital='yes'
Shortcut Id=startmenuCT Directory=ProgramMenuDir 
Name=Call Manager 4.0
  WorkingDirectory='INSTALLDIR' Icon=CallManager.exe 
IconIndex=0 /   
Shortcut Id=desktopCT Directory=DesktopFolder 
Name=Call Manager 4.0
  WorkingDirectory=INSTALLDIR Icon=CallManager.exe 
IconIndex=0 /
  /File
  File Id='CallManConfEXE' Name='Call Manager.exe.config' 
DiskId='1' Source='Call Manager.exe.config' Vital='yes'
  /File
  RemoveFile Id=oldinstallshortcut On=install 
Name=Launch logging.exe.lnk Directory=oldlnkstartupfolder /
/Component

  /Directory
/Directory
/Directory

  Directory Id=ProgramMenuFolder Name=PMenu
Directory Id=ProgramMenuDir Name=Courtney Thorne Ltd /
  /Directory
 
  Directory Id=DesktopFolder Name=Desktop /
  Directory Id=oldlnkstartupfolder FileSource=C:\Documents and 
Settings\All Users\Start Menu\Programs\Startup Name=Call Manager 4.0 /
/Directory

-
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] reference counting

2008-01-11 Thread Wilson, Phil
Component guid needs to be the same.

There is file path sharing for non-MSI installs based on the SharedDlls 
registry counting that you need to worry about only if your files are also 
installed by non-MSI installs to the same location. That's what the 
msidbComponentAttributesSharedDllRefCount bit in the Component table is for.

Phil Wilson
949-639-1680

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta 
(Volt)
Sent: Thursday, January 10, 2008 5:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] reference counting

Does reference counting rely on the file name? or is it the component GUID?

If I have a product that installs a file and a second product that installs the 
same file do I need the component GUIDS  for that file to be the same in order 
for reference counting to work? Or is it enough that the files are being 
installed to the same location with the same name?


-
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] register file types and DLL

2008-01-11 Thread Daniel Janz
Hmm.. I currently stuck on the same.

What I found out:

 

There is a tool called tallow which can generate a WiX-Fragment for a
lot of stuff

and there is a Class-Element
http://wix.sourceforge.net/manual-wix2/wix_xsd_class.htm which looks
useful for this kind of stuff.

 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Don
Tasanasanta (Volt)
Sent: Freitag, 11. Januar 2008 16:25
To: Lincoln Lavoie; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] register file types and DLL

 

Take a look at RegistryValue in the WiX help documentation.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lincoln
Lavoie
Sent: Thursday, January 10, 2008 7:36 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] register file types and DLL

 

Hello All,

I'm new to using wix.  I'm trying to develop a relatively simple
installer, but it does need to register one dll file and the file type
used by the application.  Where can I find the documentation for this
part of WiX. 

Cheers,
Lincoln

-
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


[WiX-users] Disable autoplay on multi-disk installs?

2008-01-11 Thread Craig Miller
Anyone know how to get Wix to disable autoplay on a mult-disk install?  

Each disk that is inserted gets autoplayed rather than just the first disk.

Thanks for the help,
Craig


---
http://www.overlandnavigator.com
Touchscreen Friendly GPS Mapping 


-
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


[WiX-users] Orphaned files locks program directory and disallow remove it with uninstallation process

2008-01-11 Thread Andrey Ogorodnik
Hello!

I have a problem with MSI/WiX. I have a program, here it is a
structure of directories:

.\Program Files\PROG\ - directory of program, created by installer
.\Program Files\PROG\DATA\ - directory with data, created only by
program, must be removed by installer when you using Remove option
(*** I know that for data there is an APPDATA dir, and its not a good
idea to write data to subdirs of Program Files, but this program is
for system administrators)

I have a following problem. I wrote an xml for WiX, that removes
orphaned files in DATA directory, also it removes this folder too.
But, as I think, removing process of these files and DATA directory
starting AFTER msi-installer trying remove program's directory.
Summary: directory of the progem wasn't removed, because of
subdirectory DATA was exist. Subdirectory DATA was removed later
by my code. But noone will try to remove program's directory after
this. How to change (and need?) order of removing? I need to remove
orphaned files BEFORE msi-installer tries to remove files and
directories that was created by it before.

Sample of code:
===
Directory Id=TARGETDIR Name=SourceDir
  ?include $(var.COMMONDIR)\toolkit.wxi?
  Directory Id=ProgramMenuFolder Name=PMenu
Directory Id=ProgramsCompanyName Name=$(var.COMPANY_DIR_SHORT) 
LongName=$(var.COMPANY_DIR) /
  /Directory
  Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=CompanyDir Name=$(var.COMPANY_DIR_SHORT) 
LongName=$(var.COMPANY_DIR)
  Directory Id=INSTALLDIR Name=$(var.PROG_PROG_DIR)
?include $(var.COMMONDIR)\ms_libs1.wxi?
Component Id=PCComponent Guid=!GUID1! DiskId=1
  File Id=prog.exe Name=prog.exe Source=prog.exe Vital=yes
Shortcut Id=PROG_ShortCut Directory=ProgramsCompanyName 
Name=$(var.PROG_VSHORT) LongName=$(var.PROG_LNK) 
Description=$(var.PROG_LNK_DESC) WorkingDirectory=TARGETDIR /
  /File
  File Id=prog_gui.dll Name=prog_gui.dll Source=prog_gui.dll 
Vital=yes /
  File Id=prog_krn.dll Name=prog_krn.dll Source=prog_krn.dll 
Vital=yes /
/Component

Directory Id=DataDir Name=DATA
  Component Id=RemoveConfigs Guid=!GUID2!
RemoveFile Id=progdata.bin Name=progdata.bin On=uninstall /
RemoveFolder Id=DataDir On=uninstall /
  /Component
/Directory !-- DataDir --

  /Directory
/Directory
  /Directory
/Directory

Feature Id=PCFeature Title=$(var.PROG_SHORT) Description=This is a 
feature description Level=1 ConfigurableDirectory=INSTALLDIR
  ComponentRef Id=PCComponent /
  ComponentRef Id=Toolkit /
/Feature

Feature Id=RemoveConfigsFeature Title=Remove config files Level=1 
Display=hidden
  ComponentRef Id=RemoveConfigs /
/Feature[/CODE]
===

Also I tried to add this:

===
InstallExecuteSequence
RemoveFiles /
RemoveFolders /
/InstallExecuteSequence
===

Not helped to me. :(

After removing program, I have an empty directories:
.\Program Files\Company Name\PROG\

P.S. Is it possible to post here a full debug log of installation? (About
 80kb in plaintext, or 8kb in archive - as attach?).

-- 
Best regards,
 Andrey  mailto:[EMAIL PROTECTED]


-
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] Help on Service

2008-01-11 Thread Richard
Is your service also a COM server?

/RegServer is generally used with EXE COM servers.
-- 
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/

-
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] Help on Service

2008-01-11 Thread Adam Majer
Anidil wrote:
 
 I see that the service.exe has been copied and registered under windows
 service console.but it doesn't start automatically.I get the following
 message when tried starting manually.Windows could not start the service on
 Local Computer. Error 1053: The service did not respond to the start or
 control request in a timely fashion.

I don't know if this is the same problem as in my case, but if your
service uses some runtime that is also installed by the MSI (eg. C
runtime), it CANNOT be started until MSI finalizes installation. The C
runtime will not be available and will fail to start.

This is assuming you are installing on Vista.

- Adam

-
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] Service Control Install

2008-01-11 Thread Adam Majer
SaiTeja wrote:

   Condition((NOT VersionNT=500) AND (VersionNT64))/Condition   

This is just a side note, but you should almost never use something like
(NOT Version=500). Maybe you are looking for something like
(VersionNT500)? If you do not want to use CDATA section, you probably
can just type (VersionNT gt; 500 )

The reason for this is what will happen if someone wants to install this
on NT 4 for some reason?

Cheers,
Adam

-
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] Help on Service

2008-01-11 Thread Richard

In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED]  writes:

 I don't know if this is the same problem as in my case, but if your
 service uses some runtime that is also installed by the MSI (eg. C
 runtime), it CANNOT be started until MSI finalizes installation. The C
 runtime will not be available and will fail to start.
 
 This is assuming you are installing on Vista.

...and also assuming you're using a version of the C runtime that
installs side-by-side.  The newer ones do, the older ones don't.
-- 
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/

-
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


[WiX-users] LGHT0095 error with FeatureRef

2008-01-11 Thread Kevin Richardson

Hi all,

I'm in the process of converting from WiX2 - WiX3.

Everything is fine in WiX2... in WiX3, when I run the linker, I get  
the following error:


error LGHT0095: Multiple primary references were found for Feature  
'OnlyFeature' in Product 'GUID' and Product 'SAME GUID'.


I have one file, no fragments, etc. The only relevant content is the  
following (GUIDs, filenames, etc. changed of course):


DirectoryRef Id=INSTALLDIR
  Component Id=File1.dll Guid=GUID1 DiskId=1
File Id=File1.dll Name=File1.dll KeyPath=yes  
SelfRegCost=4096 Source=Program Files\Program\File1.dll /

  /Component
  Component Id=File2.dll Guid=GUID2 DiskId=1
File Id=File2.dll Name=File2.dll KeyPath=yes  
SelfRegCost=4096 Source=Program Files\Program\File2.dll /

  /Component
  Component Id=File3.dll Guid=GUID3 DiskId=1
File Id=FIle3.dll Name=File3.dll KeyPath=yes  
Source=Program Files\Program\File3.dll /

  /Component
  Component Id=File1.exe Guid=GUID4 DiskId=1
File Id=File1.exe Name=File1.exe KeyPath=yes  
Source=Program Files\Program\File1.exe /
Shortcut Id=Shortcut1 Directory=ProgramMenuFolder  
Name=Shortcut Advertise=yes Icon=Icon.exe /

  /Component
/DirectoryRef

DirectoryRef Id=INSTALLERCACHE
  Component Id=InstallerCache Guid=GUID5 KeyPath=yes
Condition![CDATA[NOT DONTCACHEMSI]]/Condition
CreateFolder /
CopyFile Id=Program.msi SourceProperty=SourceDir  
SourceName=Program.msi DestinationDirectory=INSTALLERCACHE /
RemoveFile Id=Program.msi Directory=INSTALLERCACHE  
Name=Program.msi On=uninstall /
RemoveFolder Id=INSTALLERCACHE Directory=INSTALLERCACHE  
On=uninstall /

  /Component
/DirectoryRef

FeatureRef Id=OnlyFeature
  ComponentRef Id=File1.exe /
  ComponentRef Id=File1.dll /
  ComponentRef Id=File2.dll /
  ComponentRef Id=File3.dll /
  ComponentRef Id=InstallerCache /
/FeatureRef


The only way I can make it work is to put the ComponentRefs directly  
under the Feature element. However, I also need to add dynamically  
linked files, and those tools are set up for FeatureRef/ComponentRefs.


I'm sure I've just missed something simple because I find it hard to  
believe that FeatureRef/ComponentRef isn't valid anymore. This is  
wix-3.0.3711.0.


Thanks,

-kevin-
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] LGHT0095 error with FeatureRef

2008-01-11 Thread Brian Rogers
Hey Kevin,

I have noticed this as well.

-- 
Brian Rogers
Intelligence removes complexity. - BR
http://www.codeplex.com/wixml/

On Jan 11, 2008 4:53 PM, Kevin Richardson [EMAIL PROTECTED] wrote:

 Hi all,
 I'm in the process of converting from WiX2 - WiX3.

 Everything is fine in WiX2... in WiX3, when I run the linker, I get the
 following error:

 error LGHT0095: Multiple primary references were found for Feature
 'OnlyFeature' in Product 'GUID' and Product 'SAME GUID'.

 I have one file, no fragments, etc. The only relevant content is the
 following (GUIDs, filenames, etc. changed of course):

  DirectoryRef Id=INSTALLDIR
   Component Id=File1.dll Guid=GUID1 DiskId=1
 File Id=File1.dll Name=File1.dll KeyPath=yes
 SelfRegCost=4096 Source=Program Files\Program\File1.dll /
   /Component
   Component Id=File2.dll Guid=GUID2 DiskId=1
 File Id=File2.dll Name=File2.dll KeyPath=yes
 SelfRegCost=4096 Source=Program Files\Program\File2.dll /
   /Component
Component Id=File3.dll Guid=GUID3 DiskId=1
 File Id=FIle3.dll Name=File3.dll KeyPath=yes
 Source=Program Files\Program\File3.dll /
   /Component
   Component Id=File1.exe Guid=GUID4 DiskId=1
 File Id=File1.exe Name=File1.exe KeyPath=yes
 Source=Program Files\Program\File1.exe /
 Shortcut Id=Shortcut1 Directory=ProgramMenuFolder
 Name=Shortcut Advertise=yes Icon=Icon.exe /
   /Component
 /DirectoryRef

  DirectoryRef Id=INSTALLERCACHE
   Component Id=InstallerCache Guid=GUID5 KeyPath=yes
 Condition![CDATA[NOT DONTCACHEMSI]]/Condition

 CreateFolder /

 CopyFile Id=Program.msi SourceProperty=SourceDir SourceName=
 Program.msi DestinationDirectory=INSTALLERCACHE /
 RemoveFile Id=Program.msi Directory=INSTALLERCACHE Name=
 Program.msi On=uninstall /
 RemoveFolder Id=INSTALLERCACHE Directory=INSTALLERCACHE
 On=uninstall /
   /Component

 /DirectoryRef

  FeatureRef Id=OnlyFeature
   ComponentRef Id=File1.exe /
   ComponentRef Id=File1.dll /
   ComponentRef Id=File2.dll /
   ComponentRef Id=File3.dll /
   ComponentRef Id=InstallerCache /
 /FeatureRef


 The only way I can make it work is to put the ComponentRefs directly under
 the Feature element. However, I also need to add dynamically linked files,
 and those tools are set up for FeatureRef/ComponentRefs.

 I'm sure I've just missed something simple because I find it hard to
 believe that FeatureRef/ComponentRef isn't valid anymore. This is
 wix-3.0.3711.0.

 Thanks,

 -kevin

 -
 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

-
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