date:20100506

A Custom Action must point to a DLL/EXE/VBScript or Jscript.

If the file must be in the MSI itself you cannot run it using a 
VBScript/DLL/EXE Custom action because the .chm is not extracted yet. You could 
wrap the .CHM in a small EXE and run that then...

Best regards,
Sebastian Brand
www.instyler.com | blog.sebastianbrand.com 


-Original Message-
From: Goran Brcanski [mailto:goran.brcan...@gmail.com] 
Sent: Donnerstag, 6. Mai 2010 10:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Show help file during installation


Is it possible to run .chm file during installation?

I added one checkbox, and if it's checked custom action is called which
should show install guide.

I tried this:

Binary Id=InstallGuide SourceFile=InstallGuide.chm /

CustomAction  Id='ShowInstallGuide' BinaryKey=InstallGuide ExeCommand=''
Execute='immediate' Return='asyncNoWait' /


Checkbox state is checked on Next button click:
Publish Dialog=CustomWelcomeDlg Control=Next Event=DoAction
Value=ShowInstallGuideSHOW_INSTALL_GUIDE = 1/Publish

It works if I define executable file in Binary element, but nothing happens
for .chm or any other non executable file.

I was thinking to try calling hh.exe InstallGuide.chm but I am not sure how
to call this when InstallGuide.chm is not on the disk but in installer.


Thanks,
Goran
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Show-help-file-during-installation-tp5013146p5013146.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Show help file during installation

2010-05-06 Thread Peter Shirtcliffe

If you are happy to build your installer with the help file not
compressed into a cab, you can use the OriginalDatabase property to find
the file and use the WixShellExec custom action (documented in the wix3
help) to run it. 

-Original Message-
From: Sebastian Brand [mailto:sebast...@instyler.com] 
Sent: 06 May 2010 10:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Show help file during installation

A Custom Action must point to a DLL/EXE/VBScript or Jscript.

If the file must be in the MSI itself you cannot run it using a
VBScript/DLL/EXE Custom action because the .chm is not extracted yet.
You could wrap the .CHM in a small EXE and run that then...

Best regards,
Sebastian Brand
www.instyler.com | blog.sebastianbrand.com 


-Original Message-
From: Goran Brcanski [mailto:goran.brcan...@gmail.com]
Sent: Donnerstag, 6. Mai 2010 10:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Show help file during installation


Is it possible to run .chm file during installation?

I added one checkbox, and if it's checked custom action is called which
should show install guide.

I tried this:

Binary Id=InstallGuide SourceFile=InstallGuide.chm /

CustomAction  Id='ShowInstallGuide' BinaryKey=InstallGuide
ExeCommand=''
Execute='immediate' Return='asyncNoWait' /


Checkbox state is checked on Next button click:
Publish Dialog=CustomWelcomeDlg Control=Next Event=DoAction
Value=ShowInstallGuideSHOW_INSTALL_GUIDE = 1/Publish

It works if I define executable file in Binary element, but nothing
happens
for .chm or any other non executable file.

I was thinking to try calling hh.exe InstallGuide.chm but I am not sure
how
to call this when InstallGuide.chm is not on the disk but in installer.


Thanks,
Goran
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Show-help-
file-during-installation-tp5013146p5013146.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
/pre
BR style=font-size:4px;
a href = http://www.sdl.com;img src=http://www.sdl.com/images/email 
logo_150dpi-01.png alt=www.sdl.com border=0//a
BR
font face=arial  size=2 a href = http://www.sdl.com; 
style=color:005740; font-weight: boldwww.sdl.com/a
BR
BR
font face=arial  size=1 color=#736F6E
bSDL PLC confidential, all rights reserved./b
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.BR
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.BR
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.
/font



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Read file content from CA

2010-05-06 Thread Niklas Söderberg

Hi,
Yeah, I considered that option as well. Felt like duplication though (it is
actually 8-10 files I might need to read, albeit small ones), and I wasn't
entirely comfortable with that. Perhaps I will choose that solution after
all, now that I've explored the alternative.

Thanks for you opinion!

Niklas


On Thu, May 6, 2010 at 11:14, David Watson dwat...@sdl.com wrote:

 Hi,
 Couldn't you just put the file in the binary table as well as install it,
 may be simpler overall than your approach.

 Dave

 -Original Message-
 From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com]
 Sent: 06 May 2010 08:40
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Read file content from CA

 Thanks for your suggestions, but I guess I didn't emphasize enough that I
 need to read the file in an _immediate_ custom action, that is, I need to
 read it from the installation package before the file gets installed. I
 guess there's no easy way to do it, so the way I solved it was to
 temporarily extract the embedded cab-file and from there extract the file I
 need. A bit cumbersome, but it works.

 Regards,
 Niklas

 On Tue, May 4, 2010 at 16:14, dB. dbl...@dblock.org wrote:

  There's a Win32_ReadFile immediate native (C++) CA in
  http://msiext.codeplex.com. It was added in 1.2 which hasn't shipped
  yet, but is stable - http://msiext.codeplex.com/releases/view/39468.
  Note that it doesn't support encoding, so only works for ANSI files.
 
  If you're writing a managed CA yourself, well, just read the file with
  StreamReader.ReadToEnd and then set a property with the contents read.
 
  Hope it helps,
 
  -dB.
 
  dB. @ dblock.org
  Moscow|Geneva|Seattle|New York
 
 
  -Original Message-
  From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com]
  Sent: Tuesday, May 04, 2010 8:38 AM
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] Read file content from CA
 
  Is it possible to get the contents of a file from a custom action
  (managed code)? I know I can get the contents of a binary item, but is
  it possible to somehow do the same for a regular file included in the
  installation package?
  I want to do this in an immediate custom action executed in the ui
  sequence.
 
  I'm guessing no since I've searched and googled extensively, in vain,
  but I'm still rather new to wix so perhaps I've missed something.
 
  Thanks,
  Niklas
 
  --
   ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
  --
   ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 

 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 /pre
 BR style=font-size:4px;
 a href = http://www.sdl.com;img 
 src=http://www.sdl.com/images/emaillogo_150dpi-01.png; alt=
 www.sdl.com border=0//a
 BR
 font face=arial  size=2 a href = http://www.sdl.com;
 style=color:005740; font-weight: boldwww.sdl.com/a
 BR
 BR
 font face=arial  size=1 color=#736F6E
 bSDL PLC confidential, all rights reserved./b
 If you are not the intended recipient of this mail SDL requests and
 requires that you delete it without acting upon or copying any of its
 contents, and we further request that you advise us.BR
 SDL PLC is a public limited company registered in England and Wales.
  Registered number: 02675207.BR
 Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
 7DY, UK.
 /font




 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .NET Custom Action fails intermittently on some machines

2010-05-06 Thread Michael Bednarek

Thanks for your reply Dov. I am using WiX 3.0.5419.0. My VM has 1.5GB RAM and 
is otherwise idle, so I hope that it's not a memory issue!

I have been investigating this further and have been able to reproduce the 
issue with a very simple installer:

?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Product Id=aebcd909-cac6-4f5c-acaa-3ff9626aa63d Name=MyInstaller 
Language=1033 Version=1.0.0.0 Manufacturer=MyInstaller 
UpgradeCode=dc580afa-5bd9-492f-87ac-cc7df3bc4e74
Package InstallerVersion=200 Compressed=yes /
Binary Id=CustomActions 
SourceFile=$(var.MyCustomAction.TargetDir)\$(var.MyCustomAction.TargetName).CA.dll
 /
CustomAction Id=MyCustomAction BinaryKey=CustomActions 
DllEntry=MyCustomAction /
InstallExecuteSequence
  Custom Action=MyCustomAction After=FindRelatedProducts /
/InstallExecuteSequence
  /Product
/Wix

My custom action code is as follows:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;

namespace MyCustomAction
{
public class CustomActions
{
[CustomAction]
public static ActionResult MyCustomAction(Session session)
{
return ActionResult.Success;
}
}
}

The CustomAction.config file is just the default one generated by Votive.

The Windows Installer log (generated by calling msiexec with /l*v) shows the 
following:

MSI (s) (38:F8) [05:44:09:180]: Doing action: MyCustomAction
MSI (s) (38:F8) [05:44:09:180]: Note: 1: 2205 2:  3: ActionText 
Action ended 5:44:09: FindRelatedProducts. Return value 0.
MSI (s) (38:E8) [05:44:09:212]: Invoking remote custom action. DLL: 
C:\Windows\Installer\MSI5986.tmp, Entrypoint: MyCustomAction
MSI (s) (38:84) [05:44:09:212]: Generating random cookie.
MSI (s) (38:84) [05:44:09:212]: Created Custom Action Server with PID 5216 
(0x1460).
MSI (s) (38:08) [05:44:09:368]: Running as a service.
MSI (s) (38:08) [05:44:09:368]: Hello, I'm your 32bit Impersonated custom 
action server.
Action start 5:44:09: MyCustomAction.
SFXCA: Extracting custom action to temporary directory: 
C:\Windows\Installer\MSI5986.tmp-\
SFXCA: Binding to CLR version v2.0.50727
Calling custom action MyCustomAction!MyCustomAction.CustomActions.MyCustomAction
CustomAction MyCustomAction returned actual error code 1603 (note this may not 
be 100% accurate if translation happened inside sandbox)
Action ended 5:44:09: MyCustomAction. Return value 3.

Are there any other options for debugging/tracing what could be going wrong?

Thanks!

Mike

-Original Message-
From: Dov Kleinman [mailto:d...@microsoft.com] 
Sent: 04 May 2010 15:15
To: General discussion for Windows Installer XML toolset.; Michael Bednarek 
Subject: Re: [WiX-users] .NET Custom Action fails intermittently on some 
machines

Hi,

I'm facing the same problem for quite some time. Same OS (W2K8R2), same 
conditions (VM) without a decent explanation.
I have an immediate custom action gathering some info and finally setting a 
property. Sometimes it fails without a reasonable explanation.
Investigating the DFT source code suggests it may correlate to the amount of 
memory the machine has available. Do you get more failures while decreasing the 
allocated VM memory? 
What WiX build number are you using? Maybe this flaw sneaked-in in a certain 
build and if we track it we can resolve it.

Thanks,
Dov





-Original Message-
From: Michael Bednarek [mailto:michael.bedna...@eu.citrix.com] 
Sent: Tuesday, March 02, 2010 11:46 AM
To: Michael Bednarek; General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] .NET Custom Action fails intermittently on some 
machines

Update: I installed/uninstalled the product 100 times on a particular machine 
(using a script) and the problem with my custom action occurred just once out 
of those 100 attempts

From: Michael Bednarek
Sent: 02 March 2010 08:37
To: General discussion for Windows Installer XML toolset.
Subject: .NET Custom Action fails intermittently on some machines

Hi all,

Our product fails to install (seemingly at random) once every so often. Once 
this failure occurs on a given machine, it is not usually possible to reproduce 
the problem again (re-installing the product will work fine).

The machines on which the install fails are VMs which all come from the same 
base image (Windows 2008 R2 x64).

The install always fails during one of our custom actions, which is written in 
.NET using DTF. The custom action (called SetUserLanguage) is quite simple: 
it detects the .NET current culture and puts the two-letter language code of 
the culture (e.g. en) into a property called UserLanguage. According to the 
MSI logs, this code is running successfully - we see our own log statements 
appearing, and we see MSI report that the UserLanguage property has been set. 
However, an error seems to occur somewhere between the .NET code completing, 
and the MSI

Re: [WiX-users] Read file content from CA

2010-05-06 Thread Yan Sklyarenko

If it is possible in your case, I would change the build script to dump these 
files to the custom MSI table(s) and let the CA read the table(s) to pull 
necessary data and alter the behavior of the installation. Thus, you won't need 
to perform heavy operations in immediate CA. And moreover, you get the 
build-time complexity rather than install-time.

Hope this helps,

-- Yan

-Original Message-
From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com] 
Sent: Thursday, May 06, 2010 13:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Read file content from CA

Hi,
Yeah, I considered that option as well. Felt like duplication though (it is
actually 8-10 files I might need to read, albeit small ones), and I wasn't
entirely comfortable with that. Perhaps I will choose that solution after
all, now that I've explored the alternative.

Thanks for you opinion!

Niklas


On Thu, May 6, 2010 at 11:14, David Watson dwat...@sdl.com wrote:

 Hi,
 Couldn't you just put the file in the binary table as well as install it,
 may be simpler overall than your approach.

 Dave

 -Original Message-
 From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com]
 Sent: 06 May 2010 08:40
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Read file content from CA

 Thanks for your suggestions, but I guess I didn't emphasize enough that I
 need to read the file in an _immediate_ custom action, that is, I need to
 read it from the installation package before the file gets installed. I
 guess there's no easy way to do it, so the way I solved it was to
 temporarily extract the embedded cab-file and from there extract the file I
 need. A bit cumbersome, but it works.

 Regards,
 Niklas

 On Tue, May 4, 2010 at 16:14, dB. dbl...@dblock.org wrote:

  There's a Win32_ReadFile immediate native (C++) CA in
  http://msiext.codeplex.com. It was added in 1.2 which hasn't shipped
  yet, but is stable - http://msiext.codeplex.com/releases/view/39468.
  Note that it doesn't support encoding, so only works for ANSI files.
 
  If you're writing a managed CA yourself, well, just read the file with
  StreamReader.ReadToEnd and then set a property with the contents read.
 
  Hope it helps,
 
  -dB.
 
  dB. @ dblock.org
  Moscow|Geneva|Seattle|New York
 
 
  -Original Message-
  From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com]
  Sent: Tuesday, May 04, 2010 8:38 AM
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] Read file content from CA
 
  Is it possible to get the contents of a file from a custom action
  (managed code)? I know I can get the contents of a binary item, but is
  it possible to somehow do the same for a regular file included in the
  installation package?
  I want to do this in an immediate custom action executed in the ui
  sequence.
 
  I'm guessing no since I've searched and googled extensively, in vain,
  but I'm still rather new to wix so perhaps I've missed something.
 
  Thanks,
  Niklas
 
  --
   ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
  --
   ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 

 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 /pre
 BR style=font-size:4px;
 a href = http://www.sdl.com;img 
 src=http://www.sdl.com/images/emaillogo_150dpi-01.png; alt=
 www.sdl.com border=0//a
 BR
 font face=arial  size=2 a href = http://www.sdl.com;
 style=color:005740; font-weight: boldwww.sdl.com/a
 BR
 BR
 font face=arial  size=1 color=#736F6E
 bSDL PLC confidential, all rights reserved./b
 If you are not the intended recipient of this mail SDL requests and
 requires that you delete it without acting upon or copying any of its
 contents, and we further request that you advise us.BR
 SDL PLC is a public limited company registered in England and Wales.
  Registered number: 02675207.BR
 Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
 7DY, UK.
 /font




 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net

Re: [WiX-users] Read file content from CA

2010-05-06 Thread dB .

It could make an interesting custom action. 

Microsoft CAB supports extracting files from any source (disk, stream, memory, 
etc.). Elmue's cablib 
(http://www.codeproject.com/KB/files/CABCompressExtract.aspx) knows how to deal 
with all of it, for example how to extract single files from a CAB embedded as 
a resource. You could add an implementation that extracts the file directly 
from the embedded CAB in an MSI without extracting the whole thing first.

Some C++/C# work required :)

dB. @ dblock.org 
Moscow|Geneva|Seattle|New York


-Original Message-
From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com] 
Sent: Thursday, May 06, 2010 3:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Read file content from CA

Thanks for your suggestions, but I guess I didn't emphasize enough that I
need to read the file in an _immediate_ custom action, that is, I need to
read it from the installation package before the file gets installed. I
guess there's no easy way to do it, so the way I solved it was to
temporarily extract the embedded cab-file and from there extract the file I
need. A bit cumbersome, but it works.

Regards,
Niklas

On Tue, May 4, 2010 at 16:14, dB. dbl...@dblock.org wrote:

 There's a Win32_ReadFile immediate native (C++) CA in
 http://msiext.codeplex.com. It was added in 1.2 which hasn't shipped yet,
 but is stable - http://msiext.codeplex.com/releases/view/39468. Note that
 it doesn't support encoding, so only works for ANSI files.

 If you're writing a managed CA yourself, well, just read the file with
 StreamReader.ReadToEnd and then set a property with the contents read.

 Hope it helps,

 -dB.

 dB. @ dblock.org
 Moscow|Geneva|Seattle|New York


 -Original Message-
 From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com]
 Sent: Tuesday, May 04, 2010 8:38 AM
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Read file content from CA

 Is it possible to get the contents of a file from a custom action (managed
 code)? I know I can get the contents of a binary item, but is it possible
 to
 somehow do the same for a regular file included in the installation
 package?
 I want to do this in an immediate custom action executed in the ui
 sequence.

 I'm guessing no since I've searched and googled extensively, in vain, but
 I'm still rather new to wix so perhaps I've missed something.

 Thanks,
 Niklas

 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] managed custom action cannot access target directory

2010-05-06 Thread dB .

Total shot in the dark, but are you declaring the deferred CA Impersonate=No? 
Otherwise you're running as the calling user, so maybe it's something to do 
with CAS.

dB. @ dblock.org 
Moscow|Geneva|Seattle|New York



-Original Message-
From: Adam Langley [mailto:alang...@winscribe.com] 
Sent: Wednesday, May 05, 2010 11:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] managed custom action cannot access target directory

I have written a deferred CA which I need to manipulate a file that is
placed in the target-directory, at the end of the install.

 

What is weird is that the path is correctly evaluated in my logging
messages, but when I use the path to open a file, it says FILE NOT
FOUND, even though I KNOW the file is there.

I put in some extra logging, to enumerate the contents of the folder to
prove that the file DOES exist, and I got this surprising result:

 

CustomActionData: 

  APPCONFIGPATH = C:\Program
Files\Company\Client\Client.Windows.exe.config

  SECTIONTOENCRYPT = secureAppSettings

Attempting to load 'C:\Program
Files\Company\Client\Client.Windows.exe.config', to encrypt section
'secureAppSettings'.

Configuration file 'C:\Program
Files\Company\Client\Client.Windows.exe.config' was not found, have you
scheduled the CA to execute after files are installed?

Enumerating files in
'C:\Windows\assembly\GAC_MSIL\Microsoft.Deployment.WindowsInstaller\3.0.
0.0__ce35f76fcda82bad'...

  - Microsoft.Deployment.WindowsInstaller.dll

 

As you can see, I am enumerating my target folder, but as soon as I
start operating on the filesystem (such as Directory.GetFiles()), the
.net runtime resolves all my queries to the GAC path where
Microsoft.Deployment.WindowsInstaller.dll lives!!!

What is up with that? Why am I being sandboxed like this??

 

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Hide InstallDirDlg during upgrade



I'm trying to hide installation path selection dialog during an upgrade and
install to the previous INSTALLDIR path stored in the registry. But it
always installs to the default path. 

Is it a must to show InstallDirDlg always part of upgrade??

-
Andy
MSI Developer
Schneider Electric
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5014310.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] [Wix-users]Patch and Services

2010-05-06 Thread Danny

Hi all,

I am creating a patch basing on previous released version msi and new version 
one, both include a service's install and start codes,
The problem is the patch I created uninstalled previous services and installed 
the service again, even though the service file keep same with previous 
released version.

Any ideas on why the patch includes the service  operation?  I am using wix 2.0 
scripts for installer and msimsp.exe for patch generation.

Thanks,
Danny
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide InstallDirDlg during upgrade

2010-05-06 Thread Pally Sandher

Condition the InstallDirDlg Events with NOT Installed  it will only
show during the first install, not upgrades.
See
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
if you need help modifying the stock WiX UI sets.

As long as you use a RegistrySearch to set INSTALLDIR appropriately it
should be fine. If you want to be really slick you could use the
INSTALLDIR property to condition whether to show the InstallDirDlg (if
it's set by the RegistrySearch, don't show InstallDirDlg).

Palbinder Sandher 
Software Deployment  IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Andy.Kruger [mailto:appr...@gmail.com] 
Sent: 06 May 2010 15:00
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Hide InstallDirDlg during upgrade



I'm trying to hide installation path selection dialog during an upgrade
and install to the previous INSTALLDIR path stored in the registry. But
it always installs to the default path. 

Is it a must to show InstallDirDlg always part of upgrade??

-
Andy
MSI Developer
Schneider Electric
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-Insta
llDirDlg-during-upgrade-tp5014310p5014310.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide InstallDirDlg during upgrade


Okie I'm clear about the first part, 

This is what I'm doing to retain the old INSTALLDIR

  Property Id=INSTALLDIR
  RegistrySearch Id=Locate_22InstallDir Root=HKLM
Key=Software\ABC\productName\1.0 Name=InstallPath Type=raw/
/Property

CustomAction Id=SetInstallDir Property=WIXUI_INSTALLDIR
Value=[INSTALLDIR] Execute=immediate/

InstallUISequence
Custom Action=SetInstallDir After=AppSearch /Custom
/InstallUISequence

InstallExecuteSequence
Custom Action=SetInstallDir After=Launchconditions /Custom
/InstallExecuteSequence

But this doesn't work.
Upgrade always installs to the default path.
any ideas??

-
Andy
MSI Developer
Schneider Electric
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5014556.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide InstallDirDlg during upgrade

2010-05-06 Thread Pally Sandher

Post your Directory Tree where INSTALLDIR is used (not the entire thing
just a decent snippet)  the Property element you use for
WIXUI_INSTALLDIR.

Your RegistrySearch looks fine but the Custom Action may not be
necessary (also you need a capital C in LaunchConditions).

Palbinder Sandher 
Software Deployment  IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Andy.Kruger [mailto:appr...@gmail.com] 
Sent: 06 May 2010 15:44
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Hide InstallDirDlg during upgrade


Okie I'm clear about the first part, 

This is what I'm doing to retain the old INSTALLDIR

  Property Id=INSTALLDIR
  RegistrySearch Id=Locate_22InstallDir Root=HKLM
Key=Software\ABC\productName\1.0 Name=InstallPath Type=raw/
/Property

CustomAction Id=SetInstallDir Property=WIXUI_INSTALLDIR
Value=[INSTALLDIR] Execute=immediate/

InstallUISequence
Custom Action=SetInstallDir After=AppSearch /Custom
/InstallUISequence

InstallExecuteSequence
Custom Action=SetInstallDir After=Launchconditions /Custom
/InstallExecuteSequence

But this doesn't work.
Upgrade always installs to the default path.
any ideas??

-
Andy
MSI Developer
Schneider Electric
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-Insta
llDirDlg-during-upgrade-tp5014310p5014556.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Problem with AppPool and VDir during update

2010-05-06 Thread Warloki


Hello, 
I'm using the latest build of the WiX 3.5.1630.0
and I have a problem while attempt to update currently installed product.
I don't know how to avoid this that's why I here :) 

I'm trying to update my product and run in command line:
msiexec /i setupproject.msi REINSTALL=ALL REINSTALLMODE=vomus /l* error.log

Here is cut from my setup log:
Action 18:27:40: WriteIIS7ConfigChanges. Installing Config Keys and Values
WriteIIS7ConfigChanges:  Entering WriteIIS7ConfigChanges in
C:\Windows\Installer\MSIBE9B.tmp, version 3.5.1630.0
WriteIIS7ConfigChanges:  Error 0x800700b7: Failed to add appPool element
WriteIIS7ConfigChanges:  Error 0x800700b7: Failed to configure IIS appPool.
WriteIIS7ConfigChanges:  Error 0x800700b7: WriteIIS7ConfigChanges Failed.
Action ended 18:27:40: InstallFinalize. Return value 3.

As you see the problem refers to the AppPool that i've installed. I tried to
remove it mannualy before update and I saw another problem with almost the
same text but it reffered to VDir. And only after I removed VirtualDir
mannualy from IIS manager, upgrade succeeded.

And here is a section of *.wxs file with IIS related settings:
!-- Using IISExtension --
iis:WebSite Id=DefaultWebSite Description=Default Web Site
   iis:WebAddress Id=AllUnassigned Port=80 /
/iis:WebSite

DirectoryRef Id=WEBAPPDIR
Component Id=VirtualDirComponent Guid={SOMEGUID} KeyPath=yes
util:User Id=AppPoolUser CreateUser=no Name=ValidUser
Password=ValidPass/

iis:WebAppPool Id=CUSTOMAPPOOL Name=MyAppPool Identity=other
User=AppPoolUser/

iis:WebVirtualDir Id=BfsVirtualDir Alias=MyWebApp
Directory=WEBAPPDIR WebSite=DefaultWebSite
  iis:WebApplication Id=BfsWebApplication Name=Alfa
WebAppPool=CUSTOMAPPOOL /
/iis:WebVirtualDir
/Component
/DirectoryRef

If I missed something very important, please let me know. Or maybe it's a
bug... 
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-AppPool-and-VDir-during-update-tp5014897p5014897.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide InstallDirDlg during upgrade


 !-- Directory layout for the product. Also specifies the mappings between
source and target directories --
Directory Id=TARGETDIR Name=SourceDir
  Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=ABC Name=ABC
  Directory Id=INSTALLDIR Name=ProductName LongName=Product
Longname

Component Id=ABCstartup
Guid={E66765C6-B75B-418e-8425-CF727E922307}
  Shortcut Id=startupEXE Directory=StartupFolder LongName=
Testname Name=TestStat Target=[INSTALLDIR]Display.exe /
/Component
 
...

  /Directory
/Directory
  /Directory
  Directory Id=StartMenuFolder /
  Directory Id=ProgramMenuFolder LongName=ProgramMenuFolder
Name=ProgramM
Directory Id=StartupFolder Name=StartUp /   
Directory Id=ABCDIR Name=Companyname /
  /Directory
/Directory
.

 UIRef Id=WixUI_InstallDir /
UIRef Id=WixUI_ErrorProgressText / 
Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR /

And my launch condition syntax is fine.
Let me know if you need anything else



-
Andy
MSI Developer
Schneider Electric
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5015127.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Best way to 'fix' string overflow in ExeCommand for CAs

2010-05-06 Thread Navid Azimi-Garakani

I have a custom action that ends up calling an executable with a large number 
of parameters (specifically, the parameters contain fully qualified paths). 
This naturally ends up causing the ExeCommand to exceeds its length limit.

  CustomAction
  Id=ImportConfiguration
  Directory=ConfigurationFolder
  ExeCommand=...
  Return=check /

What is the best (or recommended) way of handling the scenario where you 
*cannot* reduce the length of the string directly? Do you generate a .cmd on 
the fly and execute it that way? Do you move it as proper C# custom action and 
run with the Process object?

Thanks,
Navid
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: F:\LookingGlass_Web\Loo
kingGlass\Default.aspx
Error 25531. Failed to open XML file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] db install thoughts

2010-05-06 Thread lewisv

I am working on a install app that needs to install/update a db.

The system will need to install/upgrade the database.

The first time i will need to create db (with one or more sql files),
Each time after that I will need to issue one or more scripts based on the
current version of the db.

I see how to use sqldatabase and sql script to create and upgrade the dbs.
But it just looks so complicated.

I will need two sqldatabase commands, one with integrated security one
without.
For each of the sqldatabase command i will have one of more scripts per
version. Each file needs some check that will check the db version and only
run if needed. ( This also includes some special work so that x.x.x as a
version will be understood in the db )

I was thinking,

Could i do all of this easier with a custom action.

Yes I understand that it would be a little more work to begin with, but it
seems to me it may be easier to maintain over the long term.

I was thinking of a simple custom dll that will
use create database to create the db on the server
backup my db before the install
get the db version and execute embedded sql scripts to bring it up to date

I may be shooting myself in the foot. But I am interested in knowing the
benefits/drawbacks to this approach.

The biggest advantage I see is that the code will be easier to read ( not
multiple xml components )
It will be easier to follow, since it seems this is more suited to a program
centric approach rather than a msi/database approach.
Easy to debug because i could run it without runnning the installer.

The biggest disadvantages i see, is I will be wrapping my own sql connection
stuff which bypasses the tested sqldatabase/util msi code
and i will have to change my custom action every rebuild.

Please give me some wisdom here.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/db-install-thoughts-tp5016287p5016287.html
Sent from the wix-users mailing list archive at Nabble.com.

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] db install thoughts

2010-05-06 Thread Neil Sleightholm

This is what I do:
http://neilsleightholm.blogspot.com/2008/08/executing-sqlcmd-from-wix.ht
ml

Neil

-Original Message-
From: lewisv [mailto:le...@nitorco.com] 
Sent: 06 May 2010 21:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] db install thoughts

I am working on a install app that needs to install/update a db.

The system will need to install/upgrade the database. 

The first time i will need to create db (with one or more sql files),
Each time after that I will need to issue one or more scripts based on
the
current version of the db.

I see how to use sqldatabase and sql script to create and upgrade the
dbs.
But it just looks so complicated.

I will need two sqldatabase commands, one with integrated security one
without. 
For each of the sqldatabase command i will have one of more scripts per
version. Each file needs some check that will check the db version and
only
run if needed. ( This also includes some special work so that x.x.x as a
version will be understood in the db )

I was thinking, 

Could i do all of this easier with a custom action. 

Yes I understand that it would be a little more work to begin with, but
it
seems to me it may be easier to maintain over the long term.

I was thinking of a simple custom dll that will 
use create database to create the db on the server
backup my db before the install
get the db version and execute embedded sql scripts to bring it up to
date

I may be shooting myself in the foot. But I am interested in knowing the
benefits/drawbacks to this approach.

The biggest advantage I see is that the code will be easier to read (
not
multiple xml components )
It will be easier to follow, since it seems this is more suited to a
program
centric approach rather than a msi/database approach.
Easy to debug because i could run it without runnning the installer. 

The biggest disadvantages i see, is I will be wrapping my own sql
connection
stuff which bypasses the tested sqldatabase/util msi code
and i will have to change my custom action every rebuild.

Please give me some wisdom here.

-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/db-install
-thoughts-tp5016287p5016287.html
Sent from the wix-users mailing list archive at Nabble.com.

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to retain feature selection during major upgrade?

I've followed the article in the Wix docs titled How To: Implement a Major 
Upgrade In Your Installer.

Everything works fine, except when I perform the major upgrade, it uses the 
default feature selection rather than selecting the features that were 
installed with the prior version.

So I have two features, A and B that are normally installed by default.  The 
user installs version 1 and selects only feature A.  Then some time later the 
user goes to install version 2.  I want only feature A upgraded.  The current 
functionality is to have both features enabled, which upgrades feature A and 
installs feature B.

How can I check the previous feature selection so the feature tree is loaded 
properly with the prior selections?  I use the standard CustomizeDlg from WixUI.


Thanks,

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] db install thoughts

I used to use Neil's approach - executing sqlcmd from CAQuietExec.  However, I 
quickly found that there's one major drawback - you can't control the 
installer's progress bar inside a sqlcmd script.

Many of my db scripts are quite long, so we need some interaction with the user 
or they'll think it's hung and will cancel the install.

I ended up writing a custom action.  I have much more flexibility there, which 
lets me run multiple scripts depending on different scenarios.

I did this with a c# managed custom action, which uses the .net SqlClient to 
execute the scripts.  I break up the script into separate chunks with GO 
statements.  At each GO, I can update the progress bar.  I also do some basic 
string replacement to emulate sqlcmd's variable syntax.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
(480) 374-7764 - Office | (480) 203-5693 - Cell
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: Thursday, May 06, 2010 1:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] db install thoughts

This is what I do:
http://neilsleightholm.blogspot.com/2008/08/executing-sqlcmd-from-wix.ht
ml

Neil

-Original Message-
From: lewisv [mailto:le...@nitorco.com] 
Sent: 06 May 2010 21:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] db install thoughts


I am working on a install app that needs to install/update a db.

The system will need to install/upgrade the database. 

The first time i will need to create db (with one or more sql files),
Each time after that I will need to issue one or more scripts based on
the
current version of the db.


I see how to use sqldatabase and sql script to create and upgrade the
dbs.
But it just looks so complicated.

I will need two sqldatabase commands, one with integrated security one
without. 
For each of the sqldatabase command i will have one of more scripts per
version. Each file needs some check that will check the db version and
only
run if needed. ( This also includes some special work so that x.x.x as a
version will be understood in the db )

I was thinking, 

Could i do all of this easier with a custom action. 

Yes I understand that it would be a little more work to begin with, but
it
seems to me it may be easier to maintain over the long term.

I was thinking of a simple custom dll that will 
use create database to create the db on the server
backup my db before the install
get the db version and execute embedded sql scripts to bring it up to
date

I may be shooting myself in the foot. But I am interested in knowing the
benefits/drawbacks to this approach.

The biggest advantage I see is that the code will be easier to read (
not
multiple xml components )
It will be easier to follow, since it seems this is more suited to a
program
centric approach rather than a msi/database approach.
Easy to debug because i could run it without runnning the installer. 

The biggest disadvantages i see, is I will be wrapping my own sql
connection
stuff which bypasses the tested sqldatabase/util msi code
and i will have to change my custom action every rebuild.

Please give me some wisdom here.

-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/db-install
-thoughts-tp5016287p5016287.html
Sent from the wix-users mailing list archive at Nabble.com.


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Best way to 'fix' string overflow in ExeCommand for CAs

You can use other custom actions to concatenate several properties:

CustomAction Id=MyString1 Property=MyString1 
Value=[PropA][PropB][PropC]/
CustomAction Id=MyString2 Property=MyString2 
Value=[PropD][PropE][PropF]/
CustomAction Id=MyString3 Property=MyString3 
Value=[PropG][PropH][PropI]/
CustomAction Id=MyWholeString Property=MyWholeString 
Value=[MyString1][MyString2][MyString3]/
InstallExecuteSequence
  Custom Action=MyString1 After=WhereverYouWantToStart /
  Custom Action=MyString2 After=MyString1 /
  Custom Action=MyString3 After=MyString2 /
  Custom Action=MyWholeString After=MyString3 /
  Custom Action=YourOriginalCustomAction After=MyWholeString /
/InstallExecuteSequnce

MyWholeString will end up being
[PropA][PropB][PropC][PropD][PropE][PropF][ProG][PropH][PropI]


You can do this as little or as much as needed.  Each of the three strings in 
this example can hold up to 255 characters.  That's before actually converting 
each property into its value.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com] 
Sent: Thursday, May 06, 2010 9:57 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Best way to 'fix' string overflow in ExeCommand for CAs

I have a custom action that ends up calling an executable with a large number 
of parameters (specifically, the parameters contain fully qualified paths). 
This naturally ends up causing the ExeCommand to exceeds its length limit.

  CustomAction
  Id=ImportConfiguration
  Directory=ConfigurationFolder
  ExeCommand=...
  Return=check /

What is the best (or recommended) way of handling the scenario where you 
*cannot* reduce the length of the string directly? Do you generate a .cmd on 
the fly and execute it that way? Do you move it as proper C# custom action and 
run with the Process object?

Thanks,
Navid
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

2010-05-06 Thread Mike Carlson (DEV DIV)

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8?
But their file isn't actually saved in UTF-8 format. This mismatch will cause 
MSXML (which XmlFile uses) to fail on that file, everytime - I don't remember 
with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: F:\LookingGlass_Web\Loo
kingGlass\Default.aspx
Error 25531. Failed to open XML file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] db install thoughts

2010-05-06 Thread dB .

We use the wix extensions from http://msiext.codeplex.com, including for UI 
that allows you to configure the target database connection. The current beta 
of MsiExt supports SQL parsing, so you get execution with GO statements (or 
other separator if you're trying to do Oracle for example). It supports other 
extended syntax like :a to include files, and we leverage that.

We consider the first version of the database blank. Then we write update1.sql, 
update2.sql, etc., for every new release. We have a SQL script that figures out 
that the database is version 5, and that we have the newest update10.sql. So it 
will generate a SQL script roughly like this:

:a update6.sql
:a update7.sql
...
You get the idea.

We run the result with a single ODBCExecute wix extension entry. And voila. The 
whole installer is 20 lines of wix.

dB. @ dblock.org 
Moscow|Geneva|Seattle|New York



-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com] 
Sent: Thursday, May 06, 2010 5:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] db install thoughts

I used to use Neil's approach - executing sqlcmd from CAQuietExec.  However, I 
quickly found that there's one major drawback - you can't control the 
installer's progress bar inside a sqlcmd script.

Many of my db scripts are quite long, so we need some interaction with the user 
or they'll think it's hung and will cancel the install.

I ended up writing a custom action.  I have much more flexibility there, which 
lets me run multiple scripts depending on different scenarios.

I did this with a c# managed custom action, which uses the .net SqlClient to 
execute the scripts.  I break up the script into separate chunks with GO 
statements.  At each GO, I can update the progress bar.  I also do some basic 
string replacement to emulate sqlcmd's variable syntax.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
(480) 374-7764 - Office | (480) 203-5693 - Cell
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: Thursday, May 06, 2010 1:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] db install thoughts

This is what I do:
http://neilsleightholm.blogspot.com/2008/08/executing-sqlcmd-from-wix.ht
ml

Neil

-Original Message-
From: lewisv [mailto:le...@nitorco.com] 
Sent: 06 May 2010 21:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] db install thoughts


I am working on a install app that needs to install/update a db.

The system will need to install/upgrade the database. 

The first time i will need to create db (with one or more sql files),
Each time after that I will need to issue one or more scripts based on
the
current version of the db.


I see how to use sqldatabase and sql script to create and upgrade the
dbs.
But it just looks so complicated.

I will need two sqldatabase commands, one with integrated security one
without. 
For each of the sqldatabase command i will have one of more scripts per
version. Each file needs some check that will check the db version and
only
run if needed. ( This also includes some special work so that x.x.x as a
version will be understood in the db )

I was thinking, 

Could i do all of this easier with a custom action. 

Yes I understand that it would be a little more work to begin with, but
it
seems to me it may be easier to maintain over the long term.

I was thinking of a simple custom dll that will 
use create database to create the db on the server
backup my db before the install
get the db version and execute embedded sql scripts to bring it up to
date

I may be shooting myself in the foot. But I am interested in knowing the
benefits/drawbacks to this approach.

The biggest advantage I see is that the code will be easier to read (
not
multiple xml components )
It will be easier to follow, since it seems this is more suited to a
program
centric approach rather than a msi/database approach.
Easy to debug because i could run it without runnning the installer. 

The biggest disadvantages i see, is I will be wrapping my own sql
connection
stuff which bypasses the tested sqldatabase/util msi code
and i will have to change my custom action every rebuild.

Please give me some wisdom here.

-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/db-install
-thoughts-tp5016287p5016287.html
Sent from the wix-users mailing list archive at Nabble.com.


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: 
F:\LookingGlass_Web\Loo kingGlass\Default.aspx Error 25531. Failed to open XML 
file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to 
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

Where you have:
  File=[INSTALLLOCATION][ProductName]\Default.aspx

Try this instead:
  File=[#FDEFAULTASPX]

The [#filekey] syntax will resolve to the correct location.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: 
F:\LookingGlass_Web\Loo kingGlass\Default.aspx Error 25531. Failed to open XML 
file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to 
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

The Default.aspx lacked an ?xml version=1.0 encoding=utf-8? line, but 
both Web.config files have it and are treated in exactly the same way as the 
original Default.aspx.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: 
F:\LookingGlass_Web\Loo kingGlass\Default.aspx Error 25531. Failed to open XML 
file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to 
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

Also, you should make sure the file you're editing is parsable as XML.  My 
guess is that an aspx file is not.  You would be better off moving the item 
you're trying to change to a setting in the web.config.  You can definately 
edit the web.config as xml.



Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Matt Johnson 
Sent: Thursday, May 06, 2010 2:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Where you have:
  File=[INSTALLLOCATION][ProductName]\Default.aspx

Try this instead:
  File=[#FDEFAULTASPX]

The [#filekey] syntax will resolve to the correct location.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: 
F:\LookingGlass_Web\Loo kingGlass\Default.aspx Error 25531. Failed to open XML 
file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to 
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

Using the boxed File Id's helped a lot.  It appears Default.aspx is a lost 
cause and I'll need to craft a CA to do some substitutions in the file.  Anyone 
have something like this?  As advertised, web.config seems to work fine.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com] 
Sent: Thursday, May 06, 2010 3:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Also, you should make sure the file you're editing is parsable as XML.  My 
guess is that an aspx file is not.  You would be better off moving the item 
you're trying to change to a setting in the web.config.  You can definately 
edit the web.config as xml.



Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Matt Johnson 
Sent: Thursday, May 06, 2010 2:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Where you have:
  File=[INSTALLLOCATION][ProductName]\Default.aspx

Try this instead:
  File=[#FDEFAULTASPX]

The [#filekey] syntax will resolve to the correct location.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: 
F:\LookingGlass_Web\Loo kingGlass\Default.aspx Error 25531. Failed to open XML 
file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786
MSI (s) (74!94) [11:42:32:250]: Product: LookingGlass -- Error 25531. Failed to 
open XML file F:\LookingGlass_Web\LookingGlass\Default.aspx, system error: -2147
024786

Action ended 11:42:32: InstallFinalize. Return value 3.
Action ended 11:42:33: INSTALL. Return value 3.

I've checked and Default.aspx is indeed at 
F:\LookingGlass_Web\LookingGlass\Default.aspx.  Any ideas for me to pursue?

John M. Cooper
Volt at Microsoft

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

2010-05-06 Thread Mike Carlson (DEV DIV)

Is the file you're trying to modify valid XML?

I'd really avoid writing your own CA, if at all possible. They're notorious for 
inadvertently ruining your MSI's support for rollback, uninstall, and/or 
various patch scenarios.

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 3:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Using the boxed File Id's helped a lot.  It appears Default.aspx is a lost 
cause and I'll need to craft a CA to do some substitutions in the file.  Anyone 
have something like this?  As advertised, web.config seems to work fine.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com] 
Sent: Thursday, May 06, 2010 3:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Also, you should make sure the file you're editing is parsable as XML.  My 
guess is that an aspx file is not.  You would be better off moving the item 
you're trying to change to a setting in the web.config.  You can definately 
edit the web.config as xml.

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com

-Original Message-
From: Matt Johnson 
Sent: Thursday, May 06, 2010 2:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Where you have:
  File=[INSTALLLOCATION][ProductName]\Default.aspx

Try this instead:
  File=[#FDEFAULTASPX]

The [#filekey] syntax will resolve to the correct location.

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue

ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22: PublishFeatures.
Action ended 11:42:22: PublishFeatures. Return value 1.
Action start 11:42:22: PublishProduct.
Action ended 11:42:22: PublishProduct. Return value 1.
Action start 11:42:22: InstallFinalize.
ExecXmlFile:  Error 0x8007006e: failed to load XML file: 
F:\LookingGlass_Web\Loo kingGlass\Default.aspx Error 25531. Failed to open XML 
file F:\LookingGlass_Web\LookingGlass\Default.as
px, system error: -2147024786

Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is Verified There

No, like a lot of ASP.NET config files I've seen, it's part XHTML, part 
JavaScript, and part XML.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 3:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is the file you're trying to modify valid XML?

I'd really avoid writing your own CA, if at all possible. They're notorious for 
inadvertently ruining your MSI's support for rollback, uninstall, and/or 
various patch scenarios.

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 3:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Using the boxed File Id's helped a lot.  It appears Default.aspx is a lost 
cause and I'll need to craft a CA to do some substitutions in the file.  Anyone 
have something like this?  As advertised, web.config seems to work fine.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com] 
Sent: Thursday, May 06, 2010 3:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Also, you should make sure the file you're editing is parsable as XML.  My 
guess is that an aspx file is not.  You would be better off moving the item 
you're trying to change to a setting in the web.config.  You can definately 
edit the web.config as xml.



Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Matt Johnson 
Sent: Thursday, May 06, 2010 2:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Where you have:
  File=[INSTALLLOCATION][ProductName]\Default.aspx

Try this instead:
  File=[#FDEFAULTASPX]

The [#filekey] syntax will resolve to the correct location.


Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Yes, it is definitely possible.  The Default.aspx file in an ASP.NET 
configuration file.  The two Web.config files are both for IIS7.  I'll check.

--
John M. Cooper
Volt at Microsoft

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Is it possible your XML file has an inaccurate header? I've seen people before 
with an XML header like this:
   ?xml version=1.0 encoding=UTF-8? But their file isn't actually saved 
in UTF-8 format. This mismatch will cause MSXML (which XmlFile uses) to fail on 
that file, everytime - I don't remember with what error code.

Another possibility - is it possible the permissions on a parent directory of 
this file are extremely restrictive?

Thanks,
Mike Carlson

-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is 
Verified There

Here's the portion of the WiX:

  Component Id=CDEFAULTASPX 
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
  Name=Default.aspx
  DiskId=1
  Source=$(var.WebPath)\Default.aspx /
util:XmlFile Id=DEFAULTASPXEDIT
  Action=setValue
  
ElementPath=//object/param[...@init='initParams'[\]]/@value
  File=[INSTALLLOCATION][ProductName]\Default.aspx
  SelectionLanguage=XPath
  Value='lt;asp:Literal id=InitParam 
runat=server/,ServicesServer=$(var.SQLServer)' /
  /Component

Here's a portion of the error log:

Action start 11:42:22: SchedXmlFile.
Action start 11:42:22: ExecXmlFile.
Action ended 11:42:22: ExecXmlFile. Return value 1.
Action ended 11:42:22: SchedXmlFile. Return value 1.
Action start 11:42:22: RegisterUser.
Action ended 11:42:22: RegisterUser. Return value 1.
Action start 11:42:22: RegisterProduct.
Action ended 11:42:22: RegisterProduct. Return value 1.
Action start 11:42:22:

[WiX-users] Icon on util:InternetShortcut

There is no Icon property on util:InternetShortcut.

Is there a workaround to change the icon?  I want the url shortcuts to the 
web-app I'm installing to have my applicaton's icon instead of internet 
explorer.

Thanks,

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com



--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to retain feature selection during major upgrade?

2010-05-06 Thread Michael Osmond

Matt

Do you have the action MigrateFeatureStates in your Install and UI execution 
sequences.  

Michael

-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com] 
Sent: Friday, 7 May 2010 6:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to retain feature selection during major upgrade?

I've followed the article in the Wix docs titled How To: Implement a Major 
Upgrade In Your Installer.

Everything works fine, except when I perform the major upgrade, it uses the 
default feature selection rather than selecting the features that were 
installed with the prior version.

So I have two features, A and B that are normally installed by default.  The 
user installs version 1 and selects only feature A.  Then some time later the 
user goes to install version 2.  I want only feature A upgraded.  The current 
functionality is to have both features enabled, which upgrades feature A and 
installs feature B.

How can I check the previous feature selection so the feature tree is loaded 
properly with the prior selections?  I use the standard CustomizeDlg from WixUI.


Thanks,

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to retain feature selection during major upgrade?

That looks like the problem.  Looks like I can simply specify 
UpgradeVersion/@MigrateFeatures=yes and wix will do the rest.

Thanks for pointing me in the right direction!

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au] 
Sent: Thursday, May 06, 2010 3:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to retain feature selection during major upgrade?

Matt

Do you have the action MigrateFeatureStates in your Install and UI execution 
sequences.  

Michael

-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com] 
Sent: Friday, 7 May 2010 6:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to retain feature selection during major upgrade?

I've followed the article in the Wix docs titled How To: Implement a Major 
Upgrade In Your Installer.

Everything works fine, except when I perform the major upgrade, it uses the 
default feature selection rather than selecting the features that were 
installed with the prior version.

So I have two features, A and B that are normally installed by default.  The 
user installs version 1 and selects only feature A.  Then some time later the 
user goes to install version 2.  I want only feature A upgraded.  The current 
functionality is to have both features enabled, which upgrades feature A and 
installs feature B.

How can I check the previous feature selection so the feature tree is loaded 
properly with the prior selections?  I use the standard CustomizeDlg from WixUI.


Thanks,

Matt Johnson MCPD, MCTS, MCSD, MCDBA
Director of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] IIS error during Repair Installation?

2010-05-06 Thread RoyY


Thanks for your recommendation, I tried to set ConfigureIfExists for
IIS:Website, while during repair, I still got error while configuring
existing website. Is this a common issue for WIX or I was doing something
wrong in my code? btw, I am working on 64bit server of Win2008
Here is the new Logs:

Action ended 9:38:53: InstallFiles. Return value 1.
MSI (s) (CC:28) [09:38:53:421]: Skipping action: ConfigureIIs (condition is
false)
MSI (s) (CC:28) [09:38:53:421]: Doing action: ConfigureIIs7
Action 9:38:53: ConfigureIIs7. Configuring IIS
Action start 9:38:53: ConfigureIIs7.
MSI (s) (CC:B0) [09:38:53:440]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSI9EFB.tmp, Entrypoint: ConfigureIIs7
MSI (s) (CC:B4) [09:38:53:440]: Generating random cookie.
MSI (s) (CC:B4) [09:38:53:457]: Created Custom Action Server with PID 2272
(0x8E0).
MSI (s) (CC:C8) [09:38:53:609]: Running as a service.
MSI (s) (CC:C8) [09:38:53:623]: Hello, I'm your 32bit Impersonated custom
action server.
MSI (s) (CC!DC) [09:38:53:837]: PROPERTY CHANGE: Adding
StartIIS7ConfigTransaction property. Its value is 'ScaConfigureIIs'.
MSI (s) (CC!DC) [09:38:53:843]: Doing action: StartIIS7ConfigTransaction
Action 9:38:53: StartIIS7ConfigTransaction. Starting IIS Config Transaction
Action start 9:38:53: StartIIS7ConfigTransaction.
1: Starting IIS Config Transaction 
Action ended 9:38:53: StartIIS7ConfigTransaction. Return value 1.
MSI (s) (CC!DC) [09:38:53:862]: PROPERTY CHANGE: Adding
RollbackIIS7ConfigTransaction property. Its value is 'ScaConfigureIIs'.
MSI (s) (CC!DC) [09:38:53:863]: Doing action: RollbackIIS7ConfigTransaction
Action 9:38:53: RollbackIIS7ConfigTransaction. Rolling back IIS Config
Transaction
Action start 9:38:53: RollbackIIS7ConfigTransaction.
1: Rolling back IIS Config Transaction 
Action ended 9:38:53: RollbackIIS7ConfigTransaction. Return value 1.
MSI (s) (CC!DC) [09:38:53:934]: PROPERTY CHANGE: Adding
CommitIIS7ConfigTransaction property. Its value is 'ScaConfigureIIs'.
MSI (s) (CC!DC) [09:38:53:935]: Doing action: CommitIIS7ConfigTransaction
Action 9:38:53: CommitIIS7ConfigTransaction. Committing IIS Config
Transaction
Action start 9:38:53: CommitIIS7ConfigTransaction.
1: Committing IIS Config Transaction 
Action ended 9:38:53: CommitIIS7ConfigTransaction. Return value 1.
MSI (s) (CC!DC) [09:38:54:068]: PROPERTY CHANGE: Adding
WriteIIS7ConfigChanges property. Its value is '31My test Web
Site-2147483648-2147483648-214748364840My test Web Site/240My
test Web Site//C:\Program Files\Acme250My test Web
Sitehttp:80:250My test Web Sitehttp:80:40My test Web
Site/Test240My test Web Site/Test/C:\Program Files\Acme\61My test
Web SiteTest70'.
MSI (s) (CC!DC) [09:38:54:073]: Doing action: WriteIIS7ConfigChanges
Action 9:38:54: WriteIIS7ConfigChanges. Installing Config Keys and Values
Action start 9:38:54: WriteIIS7ConfigChanges.
1: Installing Config Keys and Values 
Action ended 9:38:54: WriteIIS7ConfigChanges. Return value 1.
Action ended 9:38:54: ConfigureIIs7. Return value 1.
MSI (s) (CC:28) [09:38:54:174]: Doing action: RegisterUser
Action 9:38:54: RegisterUser. Registering user
Action start 9:38:54: RegisterUser.

...

MSI (s) (CC:28) [09:38:54:298]: Note: 1: 2262 2: DigitalSignature 3:
-2147287038 
MSI (s) (CC:28) [09:38:54:298]: SOFTWARE RESTRICTION POLICY:
C:\Users\Administrator\Desktop\testWebsite.msi is not digitally signed
MSI (s) (CC:28) [09:38:54:301]: SOFTWARE RESTRICTION POLICY:
C:\Users\Administrator\Desktop\testWebsite.msi is permitted to run at the
'unrestricted' authorization level.
MSI (s) (CC:28) [09:38:54:303]: Note: 1: 2318 2: C:\Program
Files\Acme\default.htm 
MSI (s) (CC:28) [09:38:54:311]: Executing op: CacheSizeFlush(,)
MSI (s) (CC:28) [09:38:54:311]: Executing op:
ActionStart(Name=StartIIS7ConfigTransaction,Description=Starting IIS Config
Transaction,)
Action 9:38:54: StartIIS7ConfigTransaction. Starting IIS Config Transaction
MSI (s) (CC:28) [09:38:54:351]: Executing op:
CustomActionSchedule(Action=StartIIS7ConfigTransaction,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (CC:80) [09:38:54:364]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIA297.tmp, Entrypoint: StartIIS7ConfigTransaction
MSI (s) (CC:28) [09:38:54:401]: Executing op:
ActionStart(Name=RollbackIIS7ConfigTransaction,Description=Rolling back IIS
Config Transaction,)
Action 9:38:54: RollbackIIS7ConfigTransaction. Rolling back IIS Config
Transaction
MSI (s) (CC:28) [09:38:54:403]: Executing op:
CustomActionSchedule(Action=RollbackIIS7ConfigTransaction,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (CC:28) [09:38:54:405]: Executing op:
ActionStart(Name=CommitIIS7ConfigTransaction,Description=Committing IIS
Config Transaction,)
Action 9:38:54: CommitIIS7ConfigTransaction. Committing IIS Config
Transaction
MSI (s) (CC:28) [09:38:54:407]: Executing op:

Re: [WiX-users] Problem with AppPool and VDir during update

2010-05-06 Thread RoyY


I am facing the same problem now, and it seems to be a common bug? 

I also hope to see the answer in this post
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-AppPool-and-VDir-during-update-tp5014897p5017471.html
Sent from the wix-users mailing list archive at Nabble.com.

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide InstallDirDlg during upgrade


 !-- Directory layout for the product. Also specifies the mappings between
source and target directories --
Directory Id=TARGETDIR Name=SourceDir
  Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=ABC Name=ABC
  Directory Id=INSTALLDIR Name=ProductName LongName=Product
Longname

Component Id=ABCstartup
Guid={E66765C6-B75B-418e-8425-CF727E922307}
  Shortcut Id=startupEXE Directory=StartupFolder LongName=
Testname Name=TestStat Target=[INSTALLDIR]Display.exe /
/Component
 
...

  /Directory
/Directory
  /Directory
  Directory Id=StartMenuFolder /
  Directory Id=ProgramMenuFolder LongName=ProgramMenuFolder
Name=ProgramM
Directory Id=StartupFolder Name=StartUp /   
Directory Id=ABCDIR Name=Companyname /
  /Directory
/Directory
.

 UIRef Id=WixUI_InstallDir /
UIRef Id=WixUI_ErrorProgressText / 
Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR /

And my launch condition syntax is fine.

anything I'm missing here?


-
Andy
MSI Developer
Schneider Electric
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5017562.html
Sent from the wix-users mailing list archive at Nabble.com.

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide InstallDirDlg during upgrade

Try to remove the custom action, the WIXUI_INSTALLDIR is an indirect property 
that should just contain the name of the property that shall contain the path, 
not the path itself.

Best regards,
Sebastian Brand
www.instyler.com | blog.sebastianbrand.com 




-Original Message-
From: Andy.Kruger [mailto:appr...@gmail.com] 
Sent: Freitag, 7. Mai 2010 04:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Hide InstallDirDlg during upgrade


 !-- Directory layout for the product. Also specifies the mappings between
source and target directories --
Directory Id=TARGETDIR Name=SourceDir
  Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=ABC Name=ABC
  Directory Id=INSTALLDIR Name=ProductName LongName=Product
Longname

Component Id=ABCstartup
Guid={E66765C6-B75B-418e-8425-CF727E922307}
  Shortcut Id=startupEXE Directory=StartupFolder LongName=
Testname Name=TestStat Target=[INSTALLDIR]Display.exe /
/Component
 
...

  /Directory
/Directory
  /Directory
  Directory Id=StartMenuFolder /
  Directory Id=ProgramMenuFolder LongName=ProgramMenuFolder
Name=ProgramM
Directory Id=StartupFolder Name=StartUp /   
Directory Id=ABCDIR Name=Companyname /
  /Directory
/Directory
.

 UIRef Id=WixUI_InstallDir /
UIRef Id=WixUI_ErrorProgressText / 
Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR /

And my launch condition syntax is fine.

anything I'm missing here?


-
Andy
MSI Developer
Schneider Electric
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5017562.html
Sent from the wix-users mailing list archive at Nabble.com.

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with AppPool and VDir during update

Hi,

Where is your RemoveExistingProducts scheduled? I assume the IIS stuff doesn't 
handle upgrades well depending on how the existing IIS app/vdir is removed.

If you are using Wix 3.5, check out the MajorUpgrade element, otherwise see
http://jpassing.com/2007/06/16/where-to-place-removeexistingproducts-in-a-major-msi-upgrade/
 and sequence it manually.


Best regards,
Sebastian Brand
www.instyler.com | blog.sebastianbrand.com 



-Original Message-
From: RoyY [mailto:l...@husky.ca] 
Sent: Freitag, 7. Mai 2010 03:51
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problem with AppPool and VDir during update


I am facing the same problem now, and it seems to be a common bug? 

I also hope to see the answer in this post
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-AppPool-and-VDir-during-update-tp5014897p5017471.html
Sent from the wix-users mailing list archive at Nabble.com.

--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--

___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Icon on util:InternetShortcut