[WiX-users] Debug CRT merge module

2007-05-22 Thread Harry Liljeström 

Hi,

I have WiX source code, which contains debug version of an executable. Also,
in WiX I have included CRT merge module (debug version):
Merge Id=VC8Runtime SourceFile=C:\Program Files\Common Files\Merge
Modules\Microsoft_VC80_DebugCRT_x86.msm Language=1033 DiskId=1/

The MSI package is created successfully and it is also installed correctly
on the target system.

The CRT dll:s are installed in:
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_f75eb16c

Trying to launch the executable gives me following error:
'The system cannot execute the specified program.'

Can someone explain to me why the debug version of the executable cannot be
executed in the target system?

Thanks,

Harry


-- 
View this message in context: 
http://www.nabble.com/Debug-CRT-merge-module-tf3794591.html#a10732487
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Icon attribute on ProgId elements

2007-03-26 Thread Harry Liljeström 

That sounds like ProgId is referring to a File, not the Icon.  Can you
share out a bit more .wxs code?

Hi,

I have following .wxs code:

Component Id=ConfiguratorExe Guid=CCF29E44-B11F-11DB-A6D4-B41B56D89593
   File Id=configurator.exe Name=configurator.exe DiskId=1
Source=C:\Test\release\configurator.exe/
   ProgId Id=File.tst Advertise=yes Description=Test App configuration
file Icon=TstFileIcon IconIndex=0
  Extension Id=tst Advertise=yes
 Verb Id=open Command=Configure Test App Argument='%1' /
  /Extension
   /ProgId
/Component

Icon Id=TstFileIcon SourceFile=C:\Test\win\icon_32.ico/

Double click on e.g. testconf.tst file launches correctly the installed
configurator.exe, but testconf.tst file doesn't show correct TstFileIcon. It
shows Windows own icon. I'm using WiX 3.0.2420 build.

I have also tested this same .wxs code snippet in WiX 2.0.4820 build and it
seems that after successfully candle and lighting the .wxs code, the msi
tables ProgId, Extension and Verb doesn't appear to .msi package.

Can someone provide some help in this?

Thanks,

Harry
-- 
View this message in context: 
http://www.nabble.com/Icon-attribute-on-ProgId-elements-tf3373329.html#a9669370
Sent from the wix-users mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Reboot, when driver interface has been changed

2007-02-13 Thread Harry Liljeström 

Hi,

I have following scenario:
1. A deferred InstallDeviceDriver custom action installs device drivers. The
custom action checks if the driver interface has been changed? Then it
writes a volatile key in the registry, which indicates that a reboot is
necessary!

CustomAction Id=InstallDeviceDriver FileKey=instw2k.exe ExeCommand=-p
quot;[INSTALLDIR]quot;
  Impersonate=no Execute=deferred/

2. In WiX a property DOREBOOT, contains the registry value of the volatile
key value doreboot, if it is written in the registry?
Property Id=DOREBOOT
   RegistrySearch Id=RebootVolatile Type=raw Root=HKLM
  Key=SOFTWARE\MyTest\volatilekey
Name=doreboot/
/Property

3. The DOREBOOT property is used as ScheduleReboot action condition:
InstallExecuteSequence
   Custom Action=InstallDeviceDriver After=InstallFiles
  NOT Installed OR UPGRADINGPRODUCTCODE
   /Custom
   ScheduleReboot Before=InstallFinalize
  DOREBOOT
   /ScheduleReboot
/InstallExecuteSequence

My questions are:
- When is the RegistrySearch launched during installation?
- Is it possible to schedule it happen just before ScheduleReboot, in my
InstallExecuteSequence?
- If this scenario is not possible in WiX? What would be a alternative way
of doing this?

Thanks in advance,

Harry
-- 
View this message in context: 
http://www.nabble.com/Reboot%2C-when-driver-interface-has-been-changed-tf3220275.html#a8943325
Sent from the wix-users mailing list archive at Nabble.com.


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users