Re: [WiX-users] How to add a dialog box when uninstall

[Blair]

Maybe there is a bug in the WiXUI. I have never used WiX's UI in any product
I've shipped, and we recently started shipping languages that Windows
Installer's UI doesn't support very well at all, so we dropped in-MSI UI
entirely when we went with bootstrappers to manage our UI in a unified way
for our suite (similar to what Office and Developer Division at MSFT had
already done).

Looking closely at the source code, I don't see the expected "EndDialog"
publish event. The Property is set from pushing the Remove button and
something is supposed to register that as a REMOVE=ALL type setting
(eventually) but Next is disabled in that window and no other events seem to
be triggered looking at the source code.

I need to push this back to the WiX team to see who knows how WiXUI is put
together and how maintenance-mode UI is supposed to work.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 4:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

The mail was sent before it was finished. Let me continue.

Ok, I went a little trouble to get the MaintenanceTypeDlg.wxs from the Wix
source and put it in my project. I renamed it as MyMaintenanceTypeDlg.wxs.
Then I removed this line:
ARPNOREMOVE

I also changed MyWixUI_InstallDir.wxs for this line to use the changed
MaintenanceTypeDlg:

1


Then I compiled and run. I did see the [Remove] button, but when I clicked
on it, nothing happened.

Here is the InstallUISequence table from msi:
AppSearch   50
CostInitialize  800
FileCost900
CostFinalize1000
FatalError  -3
UserExit-2
MyExitDialog-1
ExecuteAction   1300
PrepareDlg  49
ProgressDlg 1299
ResumeDlg   Installed AND (RESUME OR Preselected)   1297
WelcomeDlg  NOT Installed   1298
MaintenanceWelcomeDlg   Installed AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND 201
LaunchConditions100
FindRelatedProducts 200
ValidateProductID   700


Here is the log when I uninstalled it:
MSI (c) (94:B8) [16:20:58:774]: Doing action: MaintenanceWelcomeDlg
MSI (c) (94:B8) [16:20:58:774]: Note: 1: 2205 2:  3: ActionText 
Action 16:20:58: MaintenanceWelcomeDlg. 
Action start 16:20:58: MaintenanceWelcomeDlg.
Action 16:20:58: MaintenanceWelcomeDlg. Dialog created
MSI (c) (94:CC) [16:20:58:852]: PROPERTY CHANGE: Modifying CostingComplete
property. Its current value is '0'. Its new value: '1'.
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: Extension 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: Font 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: Class 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2727 2: 
MSI (c) (94:CC) [16:20:59:727]: Note: 1: 2205 2:  3: Error 
MSI (c) (94:CC) [16:20:59:727]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2898 
Info 2898. WixUI_Font_Title, Tahoma, 1
Action 16:20:59: MyMaintenanceTypeDlg. Dialog created
MSI (c) (94:CC) [16:21:01:805]: PROPERTY CHANGE: Adding WixUI_InstallMode
property. Its value is 'Remove'.
Action 16:21:04: CancelDlg. Dialog created
Action ended 16:21:05: MaintenanceWelcomeDlg. Return value 2.
MSI (c) (94:B8) [16:21:05:446]: Doing action: UserExit
MSI (c) (94:B8) [16:21:05:446]: Note: 1: 2205 2:  3: ActionText 
Action 16:21:05: UserExit. 
Action start 16:21:05: UserExit.
Action 16:21:05: UserExit. Dialog created
Action ended 16:21:06: UserExit. Return value 2.
Action ended 16:21:06: INSTALL. Return value 2.



Thanks.






From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 3:25:49 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

In your copy of MaintenanceTypeDlg.wxs remove the condition on the Remove
button. That is the button you want to click to uninstall from the UI.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!


Here is the InstallUISequence table:
AppSearch50
CostInitialize800
FileCost900
CostFinalize1000
FatalError-3
UserExit-2
MyExitDialog-1
ExecuteAction1300
PrepareDlg49
ProgressDlg1299
ResumeDlgInstalled AND (RESUME OR Preselected)1297
WelcomeDlgNOT Installed1298
MaintenanceWelcomeDlgInstalled AND NOT RESUME AND NOT Preselected
1296
N

Re: [WiX-users] Patch failure on XP that doesn't happen on Vista

[Blair]

TargetFile\IgnoreRange element(s) are "intended" for exactly your scenario
(you tell the system one or more sections of the binary that "don't matter"
for it to be able to assert that the file is the same before applying the
patch it). If you are using Pyro instead of PatchWiz, the IgnoreRange
element goes under the File element in building your "Updated" image (it
seems to be missing from the schema/help doc).

-Original Message-
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Tuesday, September 01, 2009 6:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch failure on XP that doesn't happen on Vista

Hi Blair,

Actually, the files are not bit-for-bit the same. The error message is
probably too generic and misleading in this case.

In the case of this particular file there are no changes in code and the
only difference is in version resource which has 4-th version number
different from the RTM version. 

IMO, that explains why PatchSize=6113,TargetSize=100198.

This is nothing unusual considering the build system that I am using, which
increments 4-th version number with each new build. Quite a few other files
have the same differences - just version resource - and they don't exhibit
this problem.

I build MSP on Server 2003 system with MSI version 3.01.4000.3959 and I
create only Release build patches.

It seems that patch application MSI version is more important than the build
system MSI version since patch applies without a glitch on Vista with
version V 4.5.6002.18005 MSI, while it fails on XP with MSI components
version 3.01.

I guess I would have to enforce both build and application MSI versions to
be the same (meaning I'll have to install 4.5 MSI on XP machines before
staring install and patching process), but at this time it is just a guess.

Thanks,

Tony

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Tuesday, September 01, 2009 6:20 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Patch failure on XP that doesn't happen on Vista

I assumed you verified that the files are bit-for-bit the same before
attempting to apply the patch.

Do you build your MSP on a Vista/Server 2008 system?

We saw this one time and it happened only with Release (not Debug) for just
one file, but didn't happen when building on XP/32-bit (I never investigated
building on either 64-bit XP or Server 2003). Our products were not allowed
on Server OSs but we did our official builds on them.

It seems that the PatchAPI binaries (described here:
http://msdn.microsoft.com/en-us/library/bb417345.aspx) are somehow different
and the Patch Apply routines are somehow sometimes different between
platforms.

For a workaround we had to mark that one file as "whole file" instead of
delta. It didn't happen every build, but it did happen for about two months
around one of our major releases.

-Original Message-
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Tuesday, September 01, 2009 2:56 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch failure on XP that doesn't happen on Vista

Applying the patch on one XP system produces the following error log for one
file (edited here to shorten the path to MYFILE.EXE):

MSI (s) (74:4C) [17:23:03:041]: Executing op:
CacheBaselineFile(Baseline=0,FileKey=MYFILE.EXE,FilePath=C:\Program
Files\..\ MYFILE.EXE,,Existing=0)
MSI (s) (74:4C) [17:23:03:103]: Executing op: PatchApply(PatchName=
MYFILE.EXE,TargetName=C:\Program Files\..\
MYFILE.EXE,PatchSize=6113,TargetSize=1001984,PerTick=0,,FileAttributes=512,P
atchAttributes=0,CheckCRC=0)
MSI (s) (74:4C) [17:23:03:135]: Re-applying security from existing file.
MSI (s) (74:4C) [17:23:03:197]: Note: 1: 2318 2: C:\Config.Msi\PF4D1.tmp
MSI (s) (74:4C) [17:23:03:244]: Note: 1: 2302 2: 0
MSI (s) (74:4C) [17:23:03:338]: Note: 1: 1328 2: C:\Program Files\...
MYFILE.EXE  3: -1072807676
MSI (s) (74:4C) [17:23:03:400]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:463]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1328
MSI (s) (74:4C) [17:23:03:494]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:541]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (74:4C) [17:23:03:619]: Product: MYProd  Error 1328. Error applying
patch to file C:\Program Files\..\ MYFILE.EXE .  It has probably been
updated by other means, and can no longer be modified by this patch.  For
more information contact your patch vendor.  System Error: -1072807676

However, applying the same patch on the same RTM on Vista computer works
without any trouble.

What more can I do to attempt to diagnose the source of the problem?

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS:
TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member
NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading
software and sub

Re: [WiX-users] DirectoryRef under a Feature tag doesn't work where it would under the Fragment...

[Blair]

Do you have access to the generator (or are willing to transform its
output)?
Change it like this:



  

  

  

  


Features can obviously contain Components but they just don't contain
Directories. Yes, I know that a DirectoryRef is allowed in some places that
Directory's aren't, but...

Your generator's model, of course, makes sense in some respects as well (we
do place Components under Directories, and we usually use DirectoryRefs when
doing so.

These usage models are, I believe (although I have no knowledge to
substantiate it), why Feature and Directory are also attributes to
Component.

You can always file a feature request.

-Original Message-
From: Curtis Jewell [mailto:lists.wix-us...@csjewell.fastmail.us] 
Sent: Tuesday, September 01, 2009 8:54 PM
To: discussion for Windows Installer XML toolset.
Subject: [WiX-users] DirectoryRef under a Feature tag doesn't work where it
would under the Fragment...

I would think that this should work, but it doesn't.  (It works without
the Feature tag, why shouldn't it work with it?)

[Yes, I know. A one-component feature doesn't seem reasonable.  It's
just automatically generated, and it was the one that got printed before
the generator bailed...]



  

  

  

  

  

--
Curtis Jewell
swords...@csjewell.fastmail.us

%DCL-E-MEM-BAD, bad memory
-VMS-F-PDGERS, pudding between the ears

[I use PC-Alpine, which deliberately does not display colors and pictures in
HTML mail]



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] DirectoryRef under a Feature tag doesn't work where it would under the Fragment...

[Curtis Jewell]

I would think that this should work, but it doesn't.  (It works without
the Feature tag, why shouldn't it work with it?)

[Yes, I know. A one-component feature doesn't seem reasonable.  It's
just automatically generated, and it was the one that got printed before
the generator bailed...]



  

  

  

  

  

--
Curtis Jewell
swords...@csjewell.fastmail.us

%DCL-E-MEM-BAD, bad memory
-VMS-F-PDGERS, pudding between the ears

[I use PC-Alpine, which deliberately does not display colors and pictures in 
HTML mail]


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch failure on XP that doesn't happen on Vista

[Tony Juricic]

Hi Blair,

Actually, the files are not bit-for-bit the same. The error message is probably 
too generic and misleading in this case.

In the case of this particular file there are no changes in code and the only 
difference is in version resource which has 4-th version number different from 
the RTM version. 

IMO, that explains why PatchSize=6113,TargetSize=100198.

This is nothing unusual considering the build system that I am using, which 
increments 4-th version number with each new build. Quite a few other files 
have the same differences - just version resource - and they don't exhibit this 
problem.

I build MSP on Server 2003 system with MSI version 3.01.4000.3959 and I create 
only Release build patches.

It seems that patch application MSI version is more important than the build 
system MSI version since patch applies without a glitch on Vista with version V 
4.5.6002.18005 MSI, while it fails on XP with MSI components version 3.01.

I guess I would have to enforce both build and application MSI versions to be 
the same (meaning I'll have to install 4.5 MSI on XP machines before staring 
install and patching process), but at this time it is just a guess.

Thanks,

Tony

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Tuesday, September 01, 2009 6:20 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Patch failure on XP that doesn't happen on Vista

I assumed you verified that the files are bit-for-bit the same before
attempting to apply the patch.

Do you build your MSP on a Vista/Server 2008 system?

We saw this one time and it happened only with Release (not Debug) for just
one file, but didn't happen when building on XP/32-bit (I never investigated
building on either 64-bit XP or Server 2003). Our products were not allowed
on Server OSs but we did our official builds on them.

It seems that the PatchAPI binaries (described here:
http://msdn.microsoft.com/en-us/library/bb417345.aspx) are somehow different
and the Patch Apply routines are somehow sometimes different between
platforms.

For a workaround we had to mark that one file as "whole file" instead of
delta. It didn't happen every build, but it did happen for about two months
around one of our major releases.

-Original Message-
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Tuesday, September 01, 2009 2:56 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch failure on XP that doesn't happen on Vista

Applying the patch on one XP system produces the following error log for one
file (edited here to shorten the path to MYFILE.EXE):

MSI (s) (74:4C) [17:23:03:041]: Executing op:
CacheBaselineFile(Baseline=0,FileKey=MYFILE.EXE,FilePath=C:\Program
Files\..\ MYFILE.EXE,,Existing=0)
MSI (s) (74:4C) [17:23:03:103]: Executing op: PatchApply(PatchName=
MYFILE.EXE,TargetName=C:\Program Files\..\
MYFILE.EXE,PatchSize=6113,TargetSize=1001984,PerTick=0,,FileAttributes=512,P
atchAttributes=0,CheckCRC=0)
MSI (s) (74:4C) [17:23:03:135]: Re-applying security from existing file.
MSI (s) (74:4C) [17:23:03:197]: Note: 1: 2318 2: C:\Config.Msi\PF4D1.tmp
MSI (s) (74:4C) [17:23:03:244]: Note: 1: 2302 2: 0
MSI (s) (74:4C) [17:23:03:338]: Note: 1: 1328 2: C:\Program Files\...
MYFILE.EXE  3: -1072807676
MSI (s) (74:4C) [17:23:03:400]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:463]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1328
MSI (s) (74:4C) [17:23:03:494]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:541]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (74:4C) [17:23:03:619]: Product: MYProd  Error 1328. Error applying
patch to file C:\Program Files\..\ MYFILE.EXE .  It has probably been
updated by other means, and can no longer be modified by this patch.  For
more information contact your patch vendor.  System Error: -1072807676

However, applying the same patch on the same RTM on Vista computer works
without any trouble.

What more can I do to attempt to diagnose the source of the problem?

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS:
TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member
NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading
software and subscription company, and TradeStation Europe Limited, a United
Kingdom, FSA-authorized introducing brokerage firm. None of these companies
provides trading or investment advice, recommendations or endorsements of
any kind. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

Re: [WiX-users] Understanding component states

[Don Pratt]

Thanks Blair and Phil.

We sequence RemoveExistingProducts before InstallInitialize, but do not 
use Side-by-Side or GAC.

I'm pretty sure we're doing major upgrade correctly.  We keep the 
UpgradeCode constant and put in a new ProductCode for each new version.  
We let WiX auto-gen the PackageCode.

One thing I should have mentioned to start with is that this isn't the 
first major upgrade we've done for this product.  Upgrade from v11.2.0 
to 11.2.1 works fine.  Upgrade from 11.2.x to 11.2.2 (the current 
release) ends up dropping this one file.

Thanks again for the help.  I know trying to troubleshoot remotely can 
be tricky.  If there are other pieces of the log file or our WiX source 
that would be helpful, just let me know.

Don

Blair wrote:
> Normally if the component was already installed the "Installed:" part of the
> spew would read Local, not Absent.
>
> Does your component use either Side-by-Side or GAC? There are known issues
> with upgrades when RemoveExistingProducts is sequenced "too early" for
> Windows Installer's interface to those technologies (fusion).
>
> You are sure this is a major upgrade. The ProductCodes are different between
> the two packages, correct?
>
> -Original Message-
> From: Wilson, Phil [mailto:phil.wil...@wonderware.com] 
> Sent: Tuesday, September 01, 2009 3:18 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Understanding component states
>
> I read that to mean that the component is already installed and doesn't need
> updating from your new setup, perhaps because the versions are identical.
> Your RemoveExistingProducts is probably sequenced to run at the end of your
> install, so it's applying update rules.  In some cases you might see a
> message something like "{guid} will not be installed because the same or a
> higher-versioned keyfile is already installed", the same situation. 
>
> Phil Wilson 
>
>
> -Original Message-
> From: Don Pratt [mailto:don.pr...@cox.net] 
> Sent: Tuesday, September 01, 2009 1:35 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Understanding component states
>
> Hi,
>
> I'm having trouble understanding why one component is failing to get 
> installed.  I'm doing a major upgrade, and this component exists in both 
> the old and new versions of my package.  If I manually uninstall the old 
> version and then do a normal install of the new version, the problem 
> component does get installed.
>
> Looking in an MSI log, during the InstallValidate action I see:
> MSI (s) (C4:94) [15:51:13:079]: Component: SPCControls_dll; Installed: 
> Absent;   Request: Local;   Action: Null
>
> I have a relatively simple installer with a single feature that contains 
> everything.  This component doesn't have any conditions.  I dark'ed this 
> MSI and our previous MSI (which handles a major upgrade just fine) and 
> they both show identical markup for the component in question.  None of 
> the other components seem to have problems.
>
> What else should I look for to understand why the action for this 
> component is getting set to 'Null'?
>
> Thanks,
> Don Pratt
>
>
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus
> on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus
> on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>   

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration

Re: [WiX-users] How to add a dialog box when uninstall

[little.forest]

The mail was sent before it was finished. Let me continue.

Ok, I went a little trouble to get the MaintenanceTypeDlg.wxs from the Wix 
source and put it in my project. I renamed it as MyMaintenanceTypeDlg.wxs. Then 
I removed this line:
ARPNOREMOVE

I also changed MyWixUI_InstallDir.wxs for this line to use the changed 
MaintenanceTypeDlg:

1


Then I compiled and run. I did see the [Remove] button, but when I clicked on 
it, nothing happened.

Here is the InstallUISequence table from msi:
AppSearch   50
CostInitialize  800
FileCost900
CostFinalize1000
FatalError  -3
UserExit-2
MyExitDialog-1
ExecuteAction   1300
PrepareDlg  49
ProgressDlg 1299
ResumeDlg   Installed AND (RESUME OR Preselected)   1297
WelcomeDlg  NOT Installed   1298
MaintenanceWelcomeDlg   Installed AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND 201
LaunchConditions100
FindRelatedProducts 200
ValidateProductID   700


Here is the log when I uninstalled it:
MSI (c) (94:B8) [16:20:58:774]: Doing action: MaintenanceWelcomeDlg
MSI (c) (94:B8) [16:20:58:774]: Note: 1: 2205 2:  3: ActionText 
Action 16:20:58: MaintenanceWelcomeDlg. 
Action start 16:20:58: MaintenanceWelcomeDlg.
Action 16:20:58: MaintenanceWelcomeDlg. Dialog created
MSI (c) (94:CC) [16:20:58:852]: PROPERTY CHANGE: Modifying CostingComplete 
property. Its current value is '0'. Its new value: '1'.
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: Extension 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: Font 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2205 2:  3: Class 
MSI (c) (94:CC) [16:20:58:852]: Note: 1: 2727 2: 
MSI (c) (94:CC) [16:20:59:727]: Note: 1: 2205 2:  3: Error 
MSI (c) (94:CC) [16:20:59:727]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` 
FROM `Error` WHERE `Error` = 2898 
Info 2898. WixUI_Font_Title, Tahoma, 1
Action 16:20:59: MyMaintenanceTypeDlg. Dialog created
MSI (c) (94:CC) [16:21:01:805]: PROPERTY CHANGE: Adding WixUI_InstallMode 
property. Its value is 'Remove'.
Action 16:21:04: CancelDlg. Dialog created
Action ended 16:21:05: MaintenanceWelcomeDlg. Return value 2.
MSI (c) (94:B8) [16:21:05:446]: Doing action: UserExit
MSI (c) (94:B8) [16:21:05:446]: Note: 1: 2205 2:  3: ActionText 
Action 16:21:05: UserExit. 
Action start 16:21:05: UserExit.
Action 16:21:05: UserExit. Dialog created
Action ended 16:21:06: UserExit. Return value 2.
Action ended 16:21:06: INSTALL. Return value 2.



Thanks.






From: Blair 
To: General discussion for Windows Installer XML toolset. 

Sent: Tuesday, September 1, 2009 3:25:49 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

In your copy of MaintenanceTypeDlg.wxs remove the condition on the Remove
button. That is the button you want to click to uninstall from the UI.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!


Here is the InstallUISequence table:
AppSearch50
CostInitialize800
FileCost900
CostFinalize1000
FatalError-3
UserExit-2
MyExitDialog-1
ExecuteAction1300
PrepareDlg49
ProgressDlg1299
ResumeDlgInstalled AND (RESUME OR Preselected)1297
WelcomeDlgNOT Installed1298
MaintenanceWelcomeDlgInstalled AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND201
LaunchConditions100
FindRelatedProducts200
ValidateProductID700


Here is the log when I run msi again to try to uninstall it. What I did were
just: start the msi, saw the 'Welcome to the app 3.0 Setup Wizard', clicked
[Next] button, clicked [Change] button, nothing happened though. I then
click the [Cancel] to exit:
MSI (c) (A0:F8) [15:01:14:290]: Doing action: MaintenanceWelcomeDlg
MSI (c) (A0:F8) [15:01:14:290]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:14: MaintenanceWelcomeDlg. 
Action start 15:01:14: MaintenanceWelcomeDlg.
Action 15:01:14: MaintenanceWelcomeDlg. Dialog created
MSI (c) (A0:38) [15:01:14:352]: PROPERTY CHANGE: Modifying CostingComplete
property. Its current value is '0'. Its new value: '1'.
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (A0:38) [15:01:14:352]: No

Re: [WiX-users] How to add a dialog box when uninstall

[little.forest]

Ok, I went a little trouble to get the MaintenanceTypeDlg.wxs from the Wix 
source and put it in my project. I renamed it as MyMaintenanceTypeDlg.wxs. I 
also changed MyWixUI_InstallDir.wxs for this line:


AppSearch   50
CostInitialize  800
FileCost900
CostFinalize1000
FatalError  -3
UserExit-2
MyExitDialog-1
ExecuteAction   1300
PrepareDlg  49
ProgressDlg 1299
ResumeDlg   Installed AND (RESUME OR Preselected)   1297
WelcomeDlg  NOT Installed   1298
MaintenanceWelcomeDlg   Installed AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND 201
LaunchConditions100
FindRelatedProducts 200
ValidateProductID   700






From: Blair 
To: General discussion for Windows Installer XML toolset. 

Sent: Tuesday, September 1, 2009 3:25:49 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

In your copy of MaintenanceTypeDlg.wxs remove the condition on the Remove
button. That is the button you want to click to uninstall from the UI.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!


Here is the InstallUISequence table:
AppSearch50
CostInitialize800
FileCost900
CostFinalize1000
FatalError-3
UserExit-2
MyExitDialog-1
ExecuteAction1300
PrepareDlg49
ProgressDlg1299
ResumeDlgInstalled AND (RESUME OR Preselected)1297
WelcomeDlgNOT Installed1298
MaintenanceWelcomeDlgInstalled AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND201
LaunchConditions100
FindRelatedProducts200
ValidateProductID700


Here is the log when I run msi again to try to uninstall it. What I did were
just: start the msi, saw the 'Welcome to the app 3.0 Setup Wizard', clicked
[Next] button, clicked [Change] button, nothing happened though. I then
click the [Cancel] to exit:
MSI (c) (A0:F8) [15:01:14:290]: Doing action: MaintenanceWelcomeDlg
MSI (c) (A0:F8) [15:01:14:290]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:14: MaintenanceWelcomeDlg. 
Action start 15:01:14: MaintenanceWelcomeDlg.
Action 15:01:14: MaintenanceWelcomeDlg. Dialog created
MSI (c) (A0:38) [15:01:14:352]: PROPERTY CHANGE: Modifying CostingComplete
property. Its current value is '0'. Its new value: '1'.
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Extension 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Font 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Class 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2727 2: 
MSI (c) (A0:38) [15:01:15:352]: Note: 1: 2205 2:  3: Error 
MSI (c) (A0:38) [15:01:15:352]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2898 
Info 2898. WixUI_Font_Title, Tahoma, 1
Action 15:01:15: MaintenanceTypeDlg. Dialog created
MSI (c) (A0:38) [15:01:16:884]: PROPERTY CHANGE: Adding WixUI_InstallMode
property. Its value is 'Change'.
Action 15:01:20: CancelDlg. Dialog created
Action ended 15:01:21: MaintenanceWelcomeDlg. Return value 2.
MSI (c) (A0:F8) [15:01:21:634]: Doing action: UserExit
MSI (c) (A0:F8) [15:01:21:634]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:21: UserExit. 
Action start 15:01:21: UserExit.
Action 15:01:21: UserExit. Dialog created
Action ended 15:01:22: UserExit. Return value 2.
Action ended 15:01:22: INSTALL. Return value 2.







From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 2:28:12 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

>From Orca, what is in your InstallUISequence table?

What does a verbose debug log look like in the (client) phase? Does the
MaintenanceWelcomeDlg text show up at all?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 2:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair.


Sure, I totally agree that we should make it work first.

So I just added that MaintenanceWelcomeDlg line and tried. When
uninstalling, I hit the "Change" button, still nothing happens. Is there
something else I can try?

Many thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 12:45:48 PM
Subj

Re: [WiX-users] How to add a dialog box when uninstall

[Blair]

In your copy of MaintenanceTypeDlg.wxs remove the condition on the Remove
button. That is the button you want to click to uninstall from the UI.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 3:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!


Here is the InstallUISequence table:
AppSearch   50
CostInitialize  800
FileCost900
CostFinalize1000
FatalError  -3
UserExit-2
MyExitDialog-1
ExecuteAction   1300
PrepareDlg  49
ProgressDlg 1299
ResumeDlg   Installed AND (RESUME OR Preselected)   1297
WelcomeDlg  NOT Installed   1298
MaintenanceWelcomeDlg   Installed AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND 201
LaunchConditions100
FindRelatedProducts 200
ValidateProductID   700


Here is the log when I run msi again to try to uninstall it. What I did were
just: start the msi, saw the 'Welcome to the app 3.0 Setup Wizard', clicked
[Next] button, clicked [Change] button, nothing happened though. I then
click the [Cancel] to exit:
MSI (c) (A0:F8) [15:01:14:290]: Doing action: MaintenanceWelcomeDlg
MSI (c) (A0:F8) [15:01:14:290]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:14: MaintenanceWelcomeDlg. 
Action start 15:01:14: MaintenanceWelcomeDlg.
Action 15:01:14: MaintenanceWelcomeDlg. Dialog created
MSI (c) (A0:38) [15:01:14:352]: PROPERTY CHANGE: Modifying CostingComplete
property. Its current value is '0'. Its new value: '1'.
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Extension 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Font 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Class 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2727 2: 
MSI (c) (A0:38) [15:01:15:352]: Note: 1: 2205 2:  3: Error 
MSI (c) (A0:38) [15:01:15:352]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2898 
Info 2898. WixUI_Font_Title, Tahoma, 1
Action 15:01:15: MaintenanceTypeDlg. Dialog created
MSI (c) (A0:38) [15:01:16:884]: PROPERTY CHANGE: Adding WixUI_InstallMode
property. Its value is 'Change'.
Action 15:01:20: CancelDlg. Dialog created
Action ended 15:01:21: MaintenanceWelcomeDlg. Return value 2.
MSI (c) (A0:F8) [15:01:21:634]: Doing action: UserExit
MSI (c) (A0:F8) [15:01:21:634]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:21: UserExit. 
Action start 15:01:21: UserExit.
Action 15:01:21: UserExit. Dialog created
Action ended 15:01:22: UserExit. Return value 2.
Action ended 15:01:22: INSTALL. Return value 2.







From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 2:28:12 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

>From Orca, what is in your InstallUISequence table?

What does a verbose debug log look like in the (client) phase? Does the
MaintenanceWelcomeDlg text show up at all?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 2:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair.


Sure, I totally agree that we should make it work first.

So I just added that MaintenanceWelcomeDlg line and tried. When
uninstalling, I hit the "Change" button, still nothing happens. Is there
something else I can try?

Many thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 12:45:48 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Not sure why this would be needed, but try adding mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 10:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!

I checked, there is this line in WixUI_InstallDir.wxs:


So I removed this line. And added these two lines in my main wxs:




I Built it and installed it. After that, I double clicked the msi again, I
see the "Repair" and "Remove" buttons are grayed out, the "Change" button is
clickable. I clicked the 'Change' button, but there is nothing happening.

What should I do the make "Change" button work? Also, is there other ways to
trigger uninstallation process by not double clicking the original msi file?
For our end users, I guess no one would do the uninstallation by clicking
the msi file. The reason for that is, they may ju

Re: [WiX-users] Understanding component states

[Blair]

Normally if the component was already installed the "Installed:" part of the
spew would read Local, not Absent.

Does your component use either Side-by-Side or GAC? There are known issues
with upgrades when RemoveExistingProducts is sequenced "too early" for
Windows Installer's interface to those technologies (fusion).

You are sure this is a major upgrade. The ProductCodes are different between
the two packages, correct?

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com] 
Sent: Tuesday, September 01, 2009 3:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Understanding component states

I read that to mean that the component is already installed and doesn't need
updating from your new setup, perhaps because the versions are identical.
Your RemoveExistingProducts is probably sequenced to run at the end of your
install, so it's applying update rules.  In some cases you might see a
message something like "{guid} will not be installed because the same or a
higher-versioned keyfile is already installed", the same situation. 

Phil Wilson 


-Original Message-
From: Don Pratt [mailto:don.pr...@cox.net] 
Sent: Tuesday, September 01, 2009 1:35 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Understanding component states

Hi,

I'm having trouble understanding why one component is failing to get 
installed.  I'm doing a major upgrade, and this component exists in both 
the old and new versions of my package.  If I manually uninstall the old 
version and then do a normal install of the new version, the problem 
component does get installed.

Looking in an MSI log, during the InstallValidate action I see:
MSI (s) (C4:94) [15:51:13:079]: Component: SPCControls_dll; Installed: 
Absent;   Request: Local;   Action: Null

I have a relatively simple installer with a single feature that contains 
everything.  This component doesn't have any conditions.  I dark'ed this 
MSI and our previous MSI (which handles a major upgrade just fine) and 
they both show identical markup for the component in question.  None of 
the other components seem to have problems.

What else should I look for to understand why the action for this 
component is getting set to 'Null'?

Thanks,
Don Pratt



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch failure on XP that doesn't happen on Vista

[Blair]

I assumed you verified that the files are bit-for-bit the same before
attempting to apply the patch.

Do you build your MSP on a Vista/Server 2008 system?

We saw this one time and it happened only with Release (not Debug) for just
one file, but didn't happen when building on XP/32-bit (I never investigated
building on either 64-bit XP or Server 2003). Our products were not allowed
on Server OSs but we did our official builds on them.

It seems that the PatchAPI binaries (described here:
http://msdn.microsoft.com/en-us/library/bb417345.aspx) are somehow different
and the Patch Apply routines are somehow sometimes different between
platforms.

For a workaround we had to mark that one file as "whole file" instead of
delta. It didn't happen every build, but it did happen for about two months
around one of our major releases.

-Original Message-
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Tuesday, September 01, 2009 2:56 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch failure on XP that doesn't happen on Vista

Applying the patch on one XP system produces the following error log for one
file (edited here to shorten the path to MYFILE.EXE):

MSI (s) (74:4C) [17:23:03:041]: Executing op:
CacheBaselineFile(Baseline=0,FileKey=MYFILE.EXE,FilePath=C:\Program
Files\..\ MYFILE.EXE,,Existing=0)
MSI (s) (74:4C) [17:23:03:103]: Executing op: PatchApply(PatchName=
MYFILE.EXE,TargetName=C:\Program Files\..\
MYFILE.EXE,PatchSize=6113,TargetSize=1001984,PerTick=0,,FileAttributes=512,P
atchAttributes=0,CheckCRC=0)
MSI (s) (74:4C) [17:23:03:135]: Re-applying security from existing file.
MSI (s) (74:4C) [17:23:03:197]: Note: 1: 2318 2: C:\Config.Msi\PF4D1.tmp
MSI (s) (74:4C) [17:23:03:244]: Note: 1: 2302 2: 0
MSI (s) (74:4C) [17:23:03:338]: Note: 1: 1328 2: C:\Program Files\...
MYFILE.EXE  3: -1072807676
MSI (s) (74:4C) [17:23:03:400]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:463]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1328
MSI (s) (74:4C) [17:23:03:494]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:541]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (74:4C) [17:23:03:619]: Product: MYProd  Error 1328. Error applying
patch to file C:\Program Files\..\ MYFILE.EXE .  It has probably been
updated by other means, and can no longer be modified by this patch.  For
more information contact your patch vendor.  System Error: -1072807676

However, applying the same patch on the same RTM on Vista computer works
without any trouble.

What more can I do to attempt to diagnose the source of the problem?

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS:
TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member
NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading
software and subscription company, and TradeStation Europe Limited, a United
Kingdom, FSA-authorized introducing brokerage firm. None of these companies
provides trading or investment advice, recommendations or endorsements of
any kind. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Understanding component states

[Wilson, Phil]

I read that to mean that the component is already installed and doesn't need 
updating from your new setup, perhaps because the versions are identical. Your 
RemoveExistingProducts is probably sequenced to run at the end of your install, 
so it's applying update rules.  In some cases you might see a message something 
like "{guid} will not be installed because the same or a higher-versioned 
keyfile is already installed", the same situation. 

Phil Wilson 


-Original Message-
From: Don Pratt [mailto:don.pr...@cox.net] 
Sent: Tuesday, September 01, 2009 1:35 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Understanding component states

Hi,

I'm having trouble understanding why one component is failing to get 
installed.  I'm doing a major upgrade, and this component exists in both 
the old and new versions of my package.  If I manually uninstall the old 
version and then do a normal install of the new version, the problem 
component does get installed.

Looking in an MSI log, during the InstallValidate action I see:
MSI (s) (C4:94) [15:51:13:079]: Component: SPCControls_dll; Installed: 
Absent;   Request: Local;   Action: Null

I have a relatively simple installer with a single feature that contains 
everything.  This component doesn't have any conditions.  I dark'ed this 
MSI and our previous MSI (which handles a major upgrade just fine) and 
they both show identical markup for the component in question.  None of 
the other components seem to have problems.

What else should I look for to understand why the action for this 
component is getting set to 'Null'?

Thanks,
Don Pratt


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to add a dialog box when uninstall

[little.forest]

Thanks Blair!


Here is the InstallUISequence table:
AppSearch   50
CostInitialize  800
FileCost900
CostFinalize1000
FatalError  -3
UserExit-2
MyExitDialog-1
ExecuteAction   1300
PrepareDlg  49
ProgressDlg 1299
ResumeDlg   Installed AND (RESUME OR Preselected)   1297
WelcomeDlg  NOT Installed   1298
MaintenanceWelcomeDlg   Installed AND NOT RESUME AND NOT Preselected1296
NewerVersionDetectedNEWAPPFOUND 201
LaunchConditions100
FindRelatedProducts 200
ValidateProductID   700


Here is the log when I run msi again to try to uninstall it. What I did were 
just: start the msi, saw the 'Welcome to the app 3.0 Setup Wizard', clicked 
[Next] button, clicked [Change] button, nothing happened though. I then click 
the [Cancel] to exit:
MSI (c) (A0:F8) [15:01:14:290]: Doing action: MaintenanceWelcomeDlg
MSI (c) (A0:F8) [15:01:14:290]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:14: MaintenanceWelcomeDlg. 
Action start 15:01:14: MaintenanceWelcomeDlg.
Action 15:01:14: MaintenanceWelcomeDlg. Dialog created
MSI (c) (A0:38) [15:01:14:352]: PROPERTY CHANGE: Modifying CostingComplete 
property. Its current value is '0'. Its new value: '1'.
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Extension 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Font 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2205 2:  3: Class 
MSI (c) (A0:38) [15:01:14:352]: Note: 1: 2727 2: 
MSI (c) (A0:38) [15:01:15:352]: Note: 1: 2205 2:  3: Error 
MSI (c) (A0:38) [15:01:15:352]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` 
FROM `Error` WHERE `Error` = 2898 
Info 2898. WixUI_Font_Title, Tahoma, 1
Action 15:01:15: MaintenanceTypeDlg. Dialog created
MSI (c) (A0:38) [15:01:16:884]: PROPERTY CHANGE: Adding WixUI_InstallMode 
property. Its value is 'Change'.
Action 15:01:20: CancelDlg. Dialog created
Action ended 15:01:21: MaintenanceWelcomeDlg. Return value 2.
MSI (c) (A0:F8) [15:01:21:634]: Doing action: UserExit
MSI (c) (A0:F8) [15:01:21:634]: Note: 1: 2205 2:  3: ActionText 
Action 15:01:21: UserExit. 
Action start 15:01:21: UserExit.
Action 15:01:21: UserExit. Dialog created
Action ended 15:01:22: UserExit. Return value 2.
Action ended 15:01:22: INSTALL. Return value 2.







From: Blair 
To: General discussion for Windows Installer XML toolset. 

Sent: Tuesday, September 1, 2009 2:28:12 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

>From Orca, what is in your InstallUISequence table?

What does a verbose debug log look like in the (client) phase? Does the
MaintenanceWelcomeDlg text show up at all?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 2:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair.


Sure, I totally agree that we should make it work first.

So I just added that MaintenanceWelcomeDlg line and tried. When
uninstalling, I hit the "Change" button, still nothing happens. Is there
something else I can try?

Many thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 12:45:48 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Not sure why this would be needed, but try adding mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 10:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!

I checked, there is this line in WixUI_InstallDir.wxs:


So I removed this line. And added these two lines in my main wxs:




I Built it and installed it. After that, I double clicked the msi again, I
see the "Repair" and "Remove" buttons are grayed out, the "Change" button is
clickable. I clicked the 'Change' button, but there is nothing happening.

What should I do the make "Change" button work? Also, is there other ways to
trigger uninstallation process by not double clicking the original msi file?
For our end users, I guess no one would do the uninstallation by clicking
the msi file. The reason for that is, they may just download the file to a
temp download folder or so, install it, and then forget about the msi file
location. If now we tell them to "double click the original msi to uninstall
it", it'll be not that practical. Ideally, uninstalling the application by
clicking the shortcut in [Start]->[All Programs] system menu. Is it
possible?
Thanks.




From: Blai

[WiX-users] Patch failure on XP that doesn't happen on Vista

[Tony Juricic]

Applying the patch on one XP system produces the following error log for one  
file (edited here to shorten the path to MYFILE.EXE):

MSI (s) (74:4C) [17:23:03:041]: Executing op: 
CacheBaselineFile(Baseline=0,FileKey=MYFILE.EXE,FilePath=C:\Program Files\..\ 
MYFILE.EXE,,Existing=0)
MSI (s) (74:4C) [17:23:03:103]: Executing op: PatchApply(PatchName= 
MYFILE.EXE,TargetName=C:\Program Files\..\ 
MYFILE.EXE,PatchSize=6113,TargetSize=1001984,PerTick=0,,FileAttributes=512,PatchAttributes=0,CheckCRC=0)
MSI (s) (74:4C) [17:23:03:135]: Re-applying security from existing file.
MSI (s) (74:4C) [17:23:03:197]: Note: 1: 2318 2: C:\Config.Msi\PF4D1.tmp
MSI (s) (74:4C) [17:23:03:244]: Note: 1: 2302 2: 0
MSI (s) (74:4C) [17:23:03:338]: Note: 1: 1328 2: C:\Program Files\... 
MYFILE.EXE  3: -1072807676
MSI (s) (74:4C) [17:23:03:400]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:463]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` 
FROM `Error` WHERE `Error` = 1328
MSI (s) (74:4C) [17:23:03:494]: Note: 1: 2205 2:  3: Error
MSI (s) (74:4C) [17:23:03:541]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` 
FROM `Error` WHERE `Error` = 1709
MSI (s) (74:4C) [17:23:03:619]: Product: MYProd  Error 1328. Error applying 
patch to file C:\Program Files\..\ MYFILE.EXE .  It has probably been updated 
by other means, and can no longer be modified by this patch.  For more 
information contact your patch vendor.  System Error: -1072807676

However, applying the same patch on the same RTM on Vista computer works 
without any trouble.

What more can I do to attempt to diagnose the source of the problem?

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom action from a dialog

[Oscar Newkerk]

That was the problem.  I changed the value of Indirect to "no" and it works as 
expected.  

Thanks for all the help.


Oscar


-Original Message-
From: Richard [mailto:legal...@xmission.com] 
Sent: Tuesday, September 01, 2009 11:18 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom action from a dialog


In article <95aea6e05b3fec40ab4a1dda76a5fca82414c9f...@usmail.unifysquare.com>,
Oscar Newkerk   writes:

> Property(C): PIDKEY = None
> Property(C): None = "the PID value I entered"

This is the hallmark of an indirect property: instead of containing
the value it contains the name of the property that contains the value.

Is your PIDKEY property configured as indirect in the control?
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 

  Legalize Adulthood! 



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to add a dialog box when uninstall

[Blair]

>From Orca, what is in your InstallUISequence table?

What does a verbose debug log look like in the (client) phase? Does the
MaintenanceWelcomeDlg text show up at all?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 2:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair.


Sure, I totally agree that we should make it work first.

So I just added that MaintenanceWelcomeDlg line and tried. When
uninstalling, I hit the "Change" button, still nothing happens. Is there
something else I can try?

Many thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Tuesday, September 1, 2009 12:45:48 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Not sure why this would be needed, but try adding mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 10:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!

I checked, there is this line in WixUI_InstallDir.wxs:


So I removed this line. And added these two lines in my main wxs:




I Built it and installed it. After that, I double clicked the msi again, I
see the "Repair" and "Remove" buttons are grayed out, the "Change" button is
clickable. I clicked the 'Change' button, but there is nothing happening.

What should I do the make "Change" button work? Also, is there other ways to
trigger uninstallation process by not double clicking the original msi file?
For our end users, I guess no one would do the uninstallation by clicking
the msi file. The reason for that is, they may just download the file to a
temp download folder or so, install it, and then forget about the msi file
location. If now we tell them to "double click the original msi to uninstall
it", it'll be not that practical. Ideally, uninstalling the application by
clicking the shortcut in [Start]->[All Programs] system menu. Is it
possible?
Thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 7:50:10 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

If "Change" is grayed out you will not get the installer UI you are looking
for. Is ARPNOMODIFY set perchance?

After you install, what do you see if you double-click the MSI again? You
should get the "Change" experience, which is your starting point to show a
modal dialog during your uninstall experience.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Monday, August 31, 2009 5:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

By the way, I added this: 

Then I run the msi again, and I saw the "Change" and "Remove" buttons were
grey out. There was only the "Repair" button available. Is this correct?
Also, if I run uninstallation from [start]->[All Programs], I didn't even
see this UI. I only saw the basic uninstallation progress bar.
Thanks.




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 5:07:42 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

I kept searching for the answer about this issue. But I couldn't find any
example to make it work.
Can you Wix experts point me out? What else I need to do to show UI in
uninstallation, namely, "enable maintenance mode"? And further how to add a
radio button etc. to enable "remove user data option" during uninstallation?

(Uninstallation: I mean, the end user clicks the uninstall shortcut from
[start]=>[All Programs]. I don't mean the end user re-run the msi again, or
through ARP, or through command line - because normally all of our end users
don't run uninstallation these ways.)




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 4:19:01 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Hi Aris,

Thanks! I added this in code, then the "Remove" button is gone in ARP:


But the uninstallation is still the simple progress bar. Could you please
tell me how to "enable maintenance mode"?

Thanks.




From: Aris J. Green 
To: General discussion for Windows Installer XML toolset.

Sent: Thursday, August 27, 2009 10:20:29 AM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Disable uninstall from Add/Remove Programs, enable maintenance mode,
which will show a GUI during uninstall.  Then allow user to uninstall
from maintenance, typically through a radio button selection that sets
REMOVE=ALL.  The you can prompt the user for what you need (e.g. a SQL
password to drop a database, etc.)

Set up the s

Re: [WiX-users] How to add a dialog box when uninstall

[little.forest]

Thanks Blair.


Sure, I totally agree that we should make it work first.

So I just added that MaintenanceWelcomeDlg line and tried. When uninstalling, I 
hit the "Change" button, still nothing happens. Is there something else I can 
try?

Many thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset. 

Sent: Tuesday, September 1, 2009 12:45:48 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Not sure why this would be needed, but try adding mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 10:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!

I checked, there is this line in WixUI_InstallDir.wxs:


So I removed this line. And added these two lines in my main wxs:




I Built it and installed it. After that, I double clicked the msi again, I
see the "Repair" and "Remove" buttons are grayed out, the "Change" button is
clickable. I clicked the 'Change' button, but there is nothing happening.

What should I do the make "Change" button work? Also, is there other ways to
trigger uninstallation process by not double clicking the original msi file?
For our end users, I guess no one would do the uninstallation by clicking
the msi file. The reason for that is, they may just download the file to a
temp download folder or so, install it, and then forget about the msi file
location. If now we tell them to "double click the original msi to uninstall
it", it'll be not that practical. Ideally, uninstalling the application by
clicking the shortcut in [Start]->[All Programs] system menu. Is it
possible?
Thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 7:50:10 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

If "Change" is grayed out you will not get the installer UI you are looking
for. Is ARPNOMODIFY set perchance?

After you install, what do you see if you double-click the MSI again? You
should get the "Change" experience, which is your starting point to show a
modal dialog during your uninstall experience.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Monday, August 31, 2009 5:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

By the way, I added this: 

Then I run the msi again, and I saw the "Change" and "Remove" buttons were
grey out. There was only the "Repair" button available. Is this correct?
Also, if I run uninstallation from [start]->[All Programs], I didn't even
see this UI. I only saw the basic uninstallation progress bar.
Thanks.




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 5:07:42 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

I kept searching for the answer about this issue. But I couldn't find any
example to make it work.
Can you Wix experts point me out? What else I need to do to show UI in
uninstallation, namely, "enable maintenance mode"? And further how to add a
radio button etc. to enable "remove user data option" during uninstallation?

(Uninstallation: I mean, the end user clicks the uninstall shortcut from
[start]=>[All Programs]. I don't mean the end user re-run the msi again, or
through ARP, or through command line - because normally all of our end users
don't run uninstallation these ways.)




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 4:19:01 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Hi Aris,

Thanks! I added this in code, then the "Remove" button is gone in ARP:


But the uninstallation is still the simple progress bar. Could you please
tell me how to "enable maintenance mode"?

Thanks.




From: Aris J. Green 
To: General discussion for Windows Installer XML toolset.

Sent: Thursday, August 27, 2009 10:20:29 AM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Disable uninstall from Add/Remove Programs, enable maintenance mode,
which will show a GUI during uninstall.  Then allow user to uninstall
from maintenance, typically through a radio button selection that sets
REMOVE=ALL.  The you can prompt the user for what you need (e.g. a SQL
password to drop a database, etc.)

Set up the silent uninstall  to proceed from the command line silently
if you want this feature by passing in the proper parameters from the
command line (e.g. "SAPWD=
SERVER=").  But you won't be able to run this from
ARP although.

Regards,
greenaj

On Wed, 2009-08-26 at 09:18 +0200, Sebastian Brand (Instyler Software)
wrote:

> Hello,
> 
> Windows Installer executes uninstall in Silent mode (no UI) mode only. To
> show

[WiX-users] Understanding component states

[Don Pratt]

Hi,

I'm having trouble understanding why one component is failing to get 
installed.  I'm doing a major upgrade, and this component exists in both 
the old and new versions of my package.  If I manually uninstall the old 
version and then do a normal install of the new version, the problem 
component does get installed.

Looking in an MSI log, during the InstallValidate action I see:
MSI (s) (C4:94) [15:51:13:079]: Component: SPCControls_dll; Installed: 
Absent;   Request: Local;   Action: Null

I have a relatively simple installer with a single feature that contains 
everything.  This component doesn't have any conditions.  I dark'ed this 
MSI and our previous MSI (which handles a major upgrade just fine) and 
they both show identical markup for the component in question.  None of 
the other components seem to have problems.

What else should I look for to understand why the action for this 
component is getting set to 'Null'?

Thanks,
Don Pratt


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Backup an existing file

[Blair]

You can always test it out :)

Let us know what happens

-Original Message-
From: Alexander Shevchuk (Volt) [mailto:a-ale...@microsoft.com] 
Sent: Tuesday, September 01, 2009 10:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Backup an existing file

Hi Hicholas,

 will be translated to a record in the MoveFile table
(http://msdn.microsoft.com/en-us/library/aa370055(VS.85).aspx) and will be
processed by MoveFiles action
(http://msdn.microsoft.com/en-us/library/aa370054(VS.85).aspx). The very
last statement in the MoveFiles Action description:

"Files that are moved or copied by the MoveFiles action are not deleted when
the product is uninstalled."

I assume the same applies to rollback.

Alex



-Original Message-
From: Nicholas Makin [mailto:nma...@opentext.com] 
Sent: Tuesday, September 01, 2009 9:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Backup an existing file

I have been unable to find information on a simple thing maybe someone can
point me in the right direction:

If a given file exits (something.dll) I would like to create a backup of the
current version of the file (something.uniqueInstallID.bak) and if the
install is rolled back or upon uninstall I would like to restore this file.

I looked at the CopyFile Element but I am not sure of how it behaves during
a rollback or uninstall.

Thanks,

Nicholas

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to add a dialog box when uninstall

[Blair]

Not sure why this would be needed, but try adding mailto:little.for...@ymail.com] 
Sent: Tuesday, September 01, 2009 10:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Thanks Blair!

I checked, there is this line in WixUI_InstallDir.wxs:


So I removed this line. And added these two lines in my main wxs:




I Built it and installed it. After that, I double clicked the msi again, I
see the "Repair" and "Remove" buttons are grayed out, the "Change" button is
clickable. I clicked the 'Change' button, but there is nothing happening.

What should I do the make "Change" button work? Also, is there other ways to
trigger uninstallation process by not double clicking the original msi file?
For our end users, I guess no one would do the uninstallation by clicking
the msi file. The reason for that is, they may just download the file to a
temp download folder or so, install it, and then forget about the msi file
location. If now we tell them to "double click the original msi to uninstall
it", it'll be not that practical. Ideally, uninstalling the application by
clicking the shortcut in [Start]->[All Programs] system menu. Is it
possible?
Thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 7:50:10 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

If "Change" is grayed out you will not get the installer UI you are looking
for. Is ARPNOMODIFY set perchance?

After you install, what do you see if you double-click the MSI again? You
should get the "Change" experience, which is your starting point to show a
modal dialog during your uninstall experience.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Monday, August 31, 2009 5:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

By the way, I added this: 

Then I run the msi again, and I saw the "Change" and "Remove" buttons were
grey out. There was only the "Repair" button available. Is this correct?
Also, if I run uninstallation from [start]->[All Programs], I didn't even
see this UI. I only saw the basic uninstallation progress bar.
Thanks.




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 5:07:42 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

I kept searching for the answer about this issue. But I couldn't find any
example to make it work.
Can you Wix experts point me out? What else I need to do to show UI in
uninstallation, namely, "enable maintenance mode"? And further how to add a
radio button etc. to enable "remove user data option" during uninstallation?

(Uninstallation: I mean, the end user clicks the uninstall shortcut from
[start]=>[All Programs]. I don't mean the end user re-run the msi again, or
through ARP, or through command line - because normally all of our end users
don't run uninstallation these ways.)




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 4:19:01 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Hi Aris,

Thanks! I added this in code, then the "Remove" button is gone in ARP:


But the uninstallation is still the simple progress bar. Could you please
tell me how to "enable maintenance mode"?

Thanks.




From: Aris J. Green 
To: General discussion for Windows Installer XML toolset.

Sent: Thursday, August 27, 2009 10:20:29 AM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Disable uninstall from Add/Remove Programs, enable maintenance mode,
which will show a GUI during uninstall.  Then allow user to uninstall
from maintenance, typically through a radio button selection that sets
REMOVE=ALL.  The you can prompt the user for what you need (e.g. a SQL
password to drop a database, etc.)

Set up the silent uninstall  to proceed from the command line silently
if you want this feature by passing in the proper parameters from the
command line (e.g. "SAPWD=
SERVER=").  But you won't be able to run this from
ARP although.

Regards,
greenaj

On Wed, 2009-08-26 at 09:18 +0200, Sebastian Brand (Instyler Software)
wrote:

> Hello,
> 
> Windows Installer executes uninstall in Silent mode (no UI) mode only. To
> show a dialog, you'll have to create a custom action to show a dialog,
then
> schedule that during uninstall.
> 
> 
> Best regards,
> Sebastian Brand
> 
> Instyler Setup - Creating WiX-based MSI installations, elegantly.
> http://www.instyler.com
> 
> 
> -Original Message-
> From: little.forest [mailto:little.for...@ymail.com] 
> Sent: Wednesday, August 26, 2009 09:04
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] How to add a dialog box when uninsta

Re: [WiX-users] packa...@installerversion

[Blair]

>From http://msdn.microsoft.com/en-us/library/aa370570(VS.85).aspx (the link
I sent earlier)

"The Page Count Summary property contains the minimum installer version
required by the installation package. For a minimum of Windows Installer
2.0, this property must be set to the integer 200. For a minimum of Windows
Installer 3.0, this property must be set to the integer 300. For a minimum
of Windows Installer 3.1, this property must be set to 301. For a minimum of
Windows Installer 4.5, this property must be set to 405. For a minimum of
Windows Installer 5.0, this property must be set to 500."

This one paragraph answers both of your questions, Steve.

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: Tuesday, September 01, 2009 10:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packa...@installerversion

>> I thought this property is used to enforce the minimum version of
Windows Installer required to run the MSI.  
Yes that is correct.

The number is calculated as major * 100 + minor. So 2.0 is 200, 3.0 is
300, 4.5 is 405 and 5.0 is 500.

Neil

-Original Message-
From: Steve Lessard [mailto:sless...@microsoft.com] 
Sent: 01 September 2009 10:32
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packa...@installerversion

Maybe I am have the wrong impression of what this property is used for.
I thought this property is used to enforce the minimum version of
Windows Installer required to run the MSI.  Is that not correct?

If it is correct, what are the possible values for currently released
versions of Windows Installer?  In most examples I've found the values
are 200 or 300.  Is 450 the correct value for Windows Installer 4.5?  Is
500 the correct value for Windows Installer 5.0?




-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Monday, August 31, 2009 8:51 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] packa...@installerversion

The Package element populates the MSI's Summary Information Stream.

The InstallerVersion attribute populates the "Page Count Summary
Property"
(http://msdn.microsoft.com/en-us/library/aa370570(VS.85).aspx) (aka, the
Minimum Installer Version) of MSI files.

According to
(http://msdn.microsoft.com/en-us/library/aa372045(VS.85).aspx)
it is of type VT_I4 (aka 32-bit signed integer).

-Original Message-
From: Steve Lessard [mailto:sless...@microsoft.com]
Sent: Monday, August 31, 2009 6:54 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] packa...@installerversion




--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] hoping for confirmation

[Amy Rosewater]

Ah thank you!  I knew I must be missing something simple.

Amy

-Original Message-
From: Alexander Shevchuk (Volt) [mailto:a-ale...@microsoft.com] 
Sent: Tuesday, September 01, 2009 11:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] hoping for confirmation

Hi Amy,

Did you set UpgradeVersion/@MigrateFeatures to "yes" on product you want
to upgrade?

Alex




-Original Message-
From: Amy Rosewater [mailto:arosewa...@spectrumhr.com] 
Sent: Tuesday, September 01, 2009 9:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] hoping for confirmation

Hi All,

 

I am working on some minor issues in a major upgrade.  :)  I was hoping
someone could tell me a little about the MigrateFeatureStates action
when you have an installer that permits multiple embedded transforms of
the product code.

 

My install is in wix v3.  I have a custom action which modifies the
property I use to keep track of the product codes of already installed
applications (in the Upgrade table).  My property is OLDAPPFOUND.  With
verbose logging, I can see that the OLDAPPFOUND property gets set to a
series of product codes, one for each installed instance of my
application.  However, since I want to only upgrade one specific
instance, I later set the OLDAPPFOUND property to the product code for
the specific instance I want to upgrade.  This definitely works as I
want.

 

However, currently, I have my custom action SetOLDAPPFOUND scheduled
after MigrateFeatureStates in the InstallExecuteSequence.  The result
seems to be that despite what features were selected for install in the
product being upgraded, the install that runs for the new product is
trying to install all the features that are default selected when the
install begins.  I suspect this is related to the schedule of my
SetOLDAPPFOUND action relative to MigrateFeatureStates.  Can anyone tell
me if my suspicions are correct.  Would changing the schedule of these
two actions relative to one another make it so it would only install the
same features for the new app as it had for the old one?

 

Thanks,

 

Amy

 

Amy Rosewater VanMatre

SPECTRUM Human Resource Systems Corporation

707 17th Street Suite 3800

Denver CO, 80202

303.592.3403

arosewa...@spectrumhr.com

 


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Creating database table via DTF - SQL syntax

[Tony Juricic]

It was the length of the string in second 'Value' column - it must be at most 
255 characters. 

-Original Message-
From: Tony Juricic 
Sent: Tuesday, September 01, 2009 2:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating database table via DTF - SQL syntax

This is probably not DTF specific issue. I have code to add a table to MSP file:

using (Database db = new Database(file, DatabaseOpenMode.Transact))
{
   ColumnInfo[] arrc = new ColumnInfo[2]
   {
 new ColumnInfo("Key", typeof(string), 32, true),
 new ColumnInfo("Value", typeof(string), 256, false)
   };
   List pk = new List() { "Key" };
   TableInfo ti = new TableInfo("_MyTable", arrc, pk);
   db.Tables.Add(ti);
   db.Commit();
}

This code throws exception:
Microsoft.Deployment.WindowsInstaller.BadQuerySyntaxException: SQL query syntax 
invalid or unsupported. Database:
Invalid or missing query string: CREATE TABLE `_MyTable` (`Key` CHAR(32) NOT 
NULL, `Value` CHAR(256)  PRIMARY KEY `Key`).

My problem is that I am unable to see what is wrong with this query. It seems 
fine according to this spec:
http://msdn.microsoft.com/en-us/library/aa372021(VS.85).aspx


TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.


TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom action from a dialog

[Oscar Newkerk]

That's a code fragment from my custom action written in C#. It's the accessor 
to the property value with the Id PIDKEY.

Thanks

Oscar


-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com] 
Sent: Tuesday, September 01, 2009 10:31 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom action from a dialog

>> In the custom action code session["PIDKEY"] is null.   

Why the quotes around PIDKEY?  

Phil Wilson 

-Original Message-
From: Oscar Newkerk [mailto:osc...@unifysquare.com] 
Sent: Tuesday, September 01, 2009 8:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom action from a dialog

I finally figured out that the Log messages were just not going to show up and 
wrote a property to see some debug info.

Now I'm seeing something even weirder.  Wix version:  3.0.5419.0

I have a custom UI sequence that I based on the standard WixUI_InstallDir 
sequence.

In my product.wix I declare a couple of properties and reference the dialog 
sequence:







In the custom dialog to validate the PID I hook my custom action to the "Next" 
control.  The custom action 
uses the value of PIDKEY as the key and sets a property "VALIDATEKEY" to 
indicate the result.


1






In the custom action code session["PIDKEY"] is null.  However, session["None"] 
returns the value entered in the Key control.

I figured this out looking in the setup log file where I found this:

Property(C): PIDKEY = None
Property(C): None = "the PID value I entered"

Any idea what I'm doing wrong with the properties?

Thanks

Oscar

-Original Message-
From: Richard [mailto:legal...@xmission.com] 
Sent: Monday, August 31, 2009 3:57 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom action from a dialog


1) When you invoke a CA through a dialog control event, the messages
you attempt to write to the log don't end up in the log.  You can work
around this for debugging by using MessageBox or OutputDebugString to
write out logging information.

2) When you invoke a CA through a dialog control event, and the CA
sets properties, the dialog processing logic in the MSI runtime
doesn't realize you've changed properties and it doesn't re-evaluate
subsequent event conditions using the new property value.  You can
work around this by inserting a phony event that sets the property to
its value, i.e. Foo = [Foo].
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 

  Legalize Adulthood! 



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users





--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom action from a dialog

[Richard]

In article <95aea6e05b3fec40ab4a1dda76a5fca82414c9f...@usmail.unifysquare.com>,
Oscar Newkerk   writes:

> Property(C): PIDKEY = None
> Property(C): None = "the PID value I entered"

This is the hallmark of an indirect property: instead of containing
the value it contains the name of the property that contains the value.

Is your PIDKEY property configured as indirect in the control?
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 

  Legalize Adulthood! 

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Creating database table via DTF - SQL syntax

[Tony Juricic]

This is probably not DTF specific issue. I have code to add a table to MSP file:

using (Database db = new Database(file, DatabaseOpenMode.Transact))
{
   ColumnInfo[] arrc = new ColumnInfo[2]
   {
 new ColumnInfo("Key", typeof(string), 32, true),
 new ColumnInfo("Value", typeof(string), 256, false)
   };
   List pk = new List() { "Key" };
   TableInfo ti = new TableInfo("_MyTable", arrc, pk);
   db.Tables.Add(ti);
   db.Commit();
}

This code throws exception:
Microsoft.Deployment.WindowsInstaller.BadQuerySyntaxException: SQL query syntax 
invalid or unsupported. Database:
Invalid or missing query string: CREATE TABLE `_MyTable` (`Key` CHAR(32) NOT 
NULL, `Value` CHAR(256)  PRIMARY KEY `Key`).

My problem is that I am unable to see what is wrong with this query. It seems 
fine according to this spec:
http://msdn.microsoft.com/en-us/library/aa372021(VS.85).aspx


TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Burn Documentation

[Jason Jibben]

I know it's early, but I'm looking for some documentation on Burn.  I have a 
project that sounds right up Burn's alley, and looking forward to seeing what 
Burn can do.

I keep up to date with Rob's and boB's blogs, and downloaded WiX 3.5 (Latest 
weekly release), including source.  Specifically samples on making the setup 
manifest, and a sample setup.

Thanks.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to add a dialog box when uninstall

[little.forest]

Thanks Blair!

I checked, there is this line in WixUI_InstallDir.wxs:


So I removed this line. And added these two lines in my main wxs:




I Built it and installed it. After that, I double clicked the msi again, I see 
the "Repair" and "Remove" buttons are grayed out, the "Change" button is 
clickable. I clicked the 'Change' button, but there is nothing happening.

What should I do the make "Change" button work? Also, is there other ways to 
trigger uninstallation process by not double clicking the original msi file? 
For our end users, I guess no one would do the uninstallation by clicking the 
msi file. The reason for that is, they may just download the file to a temp 
download folder or so, install it, and then forget about the msi file location. 
If now we tell them to "double click the original msi to uninstall it", it'll 
be not that practical. Ideally, uninstalling the application by clicking the 
shortcut in [Start]->[All Programs] system menu. Is it possible?
Thanks.




From: Blair 
To: General discussion for Windows Installer XML toolset. 

Sent: Monday, August 31, 2009 7:50:10 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

If "Change" is grayed out you will not get the installer UI you are looking
for. Is ARPNOMODIFY set perchance?

After you install, what do you see if you double-click the MSI again? You
should get the "Change" experience, which is your starting point to show a
modal dialog during your uninstall experience.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Monday, August 31, 2009 5:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add a dialog box when uninstall

By the way, I added this: 

Then I run the msi again, and I saw the "Change" and "Remove" buttons were
grey out. There was only the "Repair" button available. Is this correct?
Also, if I run uninstallation from [start]->[All Programs], I didn't even
see this UI. I only saw the basic uninstallation progress bar.
Thanks.




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 5:07:42 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

I kept searching for the answer about this issue. But I couldn't find any
example to make it work.
Can you Wix experts point me out? What else I need to do to show UI in
uninstallation, namely, "enable maintenance mode"? And further how to add a
radio button etc. to enable "remove user data option" during uninstallation?

(Uninstallation: I mean, the end user clicks the uninstall shortcut from
[start]=>[All Programs]. I don't mean the end user re-run the msi again, or
through ARP, or through command line - because normally all of our end users
don't run uninstallation these ways.)




From: little.forest 
To: General discussion for Windows Installer XML toolset.

Sent: Monday, August 31, 2009 4:19:01 PM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Hi Aris,

Thanks! I added this in code, then the "Remove" button is gone in ARP:


But the uninstallation is still the simple progress bar. Could you please
tell me how to "enable maintenance mode"?

Thanks.




From: Aris J. Green 
To: General discussion for Windows Installer XML toolset.

Sent: Thursday, August 27, 2009 10:20:29 AM
Subject: Re: [WiX-users] How to add a dialog box when uninstall

Disable uninstall from Add/Remove Programs, enable maintenance mode,
which will show a GUI during uninstall.  Then allow user to uninstall
from maintenance, typically through a radio button selection that sets
REMOVE=ALL.  The you can prompt the user for what you need (e.g. a SQL
password to drop a database, etc.)

Set up the silent uninstall  to proceed from the command line silently
if you want this feature by passing in the proper parameters from the
command line (e.g. "SAPWD=
SERVER=").  But you won't be able to run this from
ARP although.

Regards,
greenaj

On Wed, 2009-08-26 at 09:18 +0200, Sebastian Brand (Instyler Software)
wrote:

> Hello,
> 
> Windows Installer executes uninstall in Silent mode (no UI) mode only. To
> show a dialog, you'll have to create a custom action to show a dialog,
then
> schedule that during uninstall.
> 
> 
> Best regards,
> Sebastian Brand
> 
> Instyler Setup - Creating WiX-based MSI installations, elegantly.
> http://www.instyler.com
> 
> 
> -Original Message-
> From: little.forest [mailto:little.for...@ymail.com] 
> Sent: Wednesday, August 26, 2009 09:04
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] How to add a dialog box when uninstall
> 
> Hi,
> 
> We're using WiX 3.0. How to add a dialog box when uninstall? 
> 
> We'd like to ask the end user if they want to delete their settings files
in
> AppData\Company\Product folder. If the answer is Yes, then we'll need to
> d

Re: [WiX-users] Custom action from a dialog

[Wilson, Phil]

>> In the custom action code session["PIDKEY"] is null.   

Why the quotes around PIDKEY?  

Phil Wilson 

-Original Message-
From: Oscar Newkerk [mailto:osc...@unifysquare.com] 
Sent: Tuesday, September 01, 2009 8:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom action from a dialog

I finally figured out that the Log messages were just not going to show up and 
wrote a property to see some debug info.

Now I'm seeing something even weirder.  Wix version:  3.0.5419.0

I have a custom UI sequence that I based on the standard WixUI_InstallDir 
sequence.

In my product.wix I declare a couple of properties and reference the dialog 
sequence:







In the custom dialog to validate the PID I hook my custom action to the "Next" 
control.  The custom action 
uses the value of PIDKEY as the key and sets a property "VALIDATEKEY" to 
indicate the result.


1






In the custom action code session["PIDKEY"] is null.  However, session["None"] 
returns the value entered in the Key control.

I figured this out looking in the setup log file where I found this:

Property(C): PIDKEY = None
Property(C): None = "the PID value I entered"

Any idea what I'm doing wrong with the properties?

Thanks

Oscar

-Original Message-
From: Richard [mailto:legal...@xmission.com] 
Sent: Monday, August 31, 2009 3:57 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom action from a dialog


1) When you invoke a CA through a dialog control event, the messages
you attempt to write to the log don't end up in the log.  You can work
around this for debugging by using MessageBox or OutputDebugString to
write out logging information.

2) When you invoke a CA through a dialog control event, and the CA
sets properties, the dialog processing logic in the MSI runtime
doesn't realize you've changed properties and it doesn't re-evaluate
subsequent event conditions using the new property value.  You can
work around this by inserting a phony event that sets the property to
its value, i.e. Foo = [Foo].
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 

  Legalize Adulthood! 



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] hoping for confirmation

[Alexander Shevchuk (Volt)]

Hi Amy,

Did you set UpgradeVersion/@MigrateFeatures to "yes" on product you want to 
upgrade?

Alex




-Original Message-
From: Amy Rosewater [mailto:arosewa...@spectrumhr.com] 
Sent: Tuesday, September 01, 2009 9:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] hoping for confirmation

Hi All,

 

I am working on some minor issues in a major upgrade.  :)  I was hoping
someone could tell me a little about the MigrateFeatureStates action
when you have an installer that permits multiple embedded transforms of
the product code.

 

My install is in wix v3.  I have a custom action which modifies the
property I use to keep track of the product codes of already installed
applications (in the Upgrade table).  My property is OLDAPPFOUND.  With
verbose logging, I can see that the OLDAPPFOUND property gets set to a
series of product codes, one for each installed instance of my
application.  However, since I want to only upgrade one specific
instance, I later set the OLDAPPFOUND property to the product code for
the specific instance I want to upgrade.  This definitely works as I
want.

 

However, currently, I have my custom action SetOLDAPPFOUND scheduled
after MigrateFeatureStates in the InstallExecuteSequence.  The result
seems to be that despite what features were selected for install in the
product being upgraded, the install that runs for the new product is
trying to install all the features that are default selected when the
install begins.  I suspect this is related to the schedule of my
SetOLDAPPFOUND action relative to MigrateFeatureStates.  Can anyone tell
me if my suspicions are correct.  Would changing the schedule of these
two actions relative to one another make it so it would only install the
same features for the new app as it had for the old one?

 

Thanks,

 

Amy

 

Amy Rosewater VanMatre

SPECTRUM Human Resource Systems Corporation

707 17th Street Suite 3800

Denver CO, 80202

303.592.3403

arosewa...@spectrumhr.com

 

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Backup an existing file

[Alexander Shevchuk (Volt)]

Hi Hicholas,

 will be translated to a record in the MoveFile table 
(http://msdn.microsoft.com/en-us/library/aa370055(VS.85).aspx) and will be 
processed by MoveFiles action 
(http://msdn.microsoft.com/en-us/library/aa370054(VS.85).aspx). The very last 
statement in the MoveFiles Action description:

"Files that are moved or copied by the MoveFiles action are not deleted when 
the product is uninstalled."

I assume the same applies to rollback.

Alex



-Original Message-
From: Nicholas Makin [mailto:nma...@opentext.com] 
Sent: Tuesday, September 01, 2009 9:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Backup an existing file

I have been unable to find information on a simple thing maybe someone can 
point me in the right direction:

If a given file exits (something.dll) I would like to create a backup of the 
current version of the file (something.uniqueInstallID.bak) and if the install 
is rolled back or upon uninstall I would like to restore this file.

I looked at the CopyFile Element but I am not sure of how it behaves during a 
rollback or uninstall.

Thanks,

Nicholas
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] packa...@installerversion

[Neil Sleightholm]

>> I thought this property is used to enforce the minimum version of
Windows Installer required to run the MSI.  
Yes that is correct.

The number is calculated as major * 100 + minor. So 2.0 is 200, 3.0 is
300, 4.5 is 405 and 5.0 is 500.

Neil

-Original Message-
From: Steve Lessard [mailto:sless...@microsoft.com] 
Sent: 01 September 2009 10:32
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packa...@installerversion

Maybe I am have the wrong impression of what this property is used for.
I thought this property is used to enforce the minimum version of
Windows Installer required to run the MSI.  Is that not correct?

If it is correct, what are the possible values for currently released
versions of Windows Installer?  In most examples I've found the values
are 200 or 300.  Is 450 the correct value for Windows Installer 4.5?  Is
500 the correct value for Windows Installer 5.0?




-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Monday, August 31, 2009 8:51 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] packa...@installerversion

The Package element populates the MSI's Summary Information Stream.

The InstallerVersion attribute populates the "Page Count Summary
Property"
(http://msdn.microsoft.com/en-us/library/aa370570(VS.85).aspx) (aka, the
Minimum Installer Version) of MSI files.

According to
(http://msdn.microsoft.com/en-us/library/aa372045(VS.85).aspx)
it is of type VT_I4 (aka 32-bit signed integer).

-Original Message-
From: Steve Lessard [mailto:sless...@microsoft.com]
Sent: Monday, August 31, 2009 6:54 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] packa...@installerversion




--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Backup an existing file

[Nicholas Makin]

I have been unable to find information on a simple thing maybe someone can 
point me in the right direction:

If a given file exits (something.dll) I would like to create a backup of the 
current version of the file (something.uniqueInstallID.bak) and if the install 
is rolled back or upon uninstall I would like to restore this file.

I looked at the CopyFile Element but I am not sure of how it behaves during a 
rollback or uninstall.

Thanks,

Nicholas
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] hoping for confirmation

[Amy Rosewater]

Hi All,

 

I am working on some minor issues in a major upgrade.  :)  I was hoping
someone could tell me a little about the MigrateFeatureStates action
when you have an installer that permits multiple embedded transforms of
the product code.

 

My install is in wix v3.  I have a custom action which modifies the
property I use to keep track of the product codes of already installed
applications (in the Upgrade table).  My property is OLDAPPFOUND.  With
verbose logging, I can see that the OLDAPPFOUND property gets set to a
series of product codes, one for each installed instance of my
application.  However, since I want to only upgrade one specific
instance, I later set the OLDAPPFOUND property to the product code for
the specific instance I want to upgrade.  This definitely works as I
want.

 

However, currently, I have my custom action SetOLDAPPFOUND scheduled
after MigrateFeatureStates in the InstallExecuteSequence.  The result
seems to be that despite what features were selected for install in the
product being upgraded, the install that runs for the new product is
trying to install all the features that are default selected when the
install begins.  I suspect this is related to the schedule of my
SetOLDAPPFOUND action relative to MigrateFeatureStates.  Can anyone tell
me if my suspicions are correct.  Would changing the schedule of these
two actions relative to one another make it so it would only install the
same features for the new app as it had for the old one?

 

Thanks,

 

Amy

 

Amy Rosewater VanMatre

SPECTRUM Human Resource Systems Corporation

707 17th Street Suite 3800

Denver CO, 80202

303.592.3403

arosewa...@spectrumhr.com

 

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Failed while processing WebDirs

[Yan Sklyarenko]

Sure, here you go:

   
   
   

-- Yan


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Tuesday, September 01, 2009 7:04 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

Thanks - could you also paste the contents of IIS6newsite.wxi?

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, September 01, 2009 8:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

Hi Mike,

Thanks for your feedback.
Here is the excerpt from my authoring:

...
  
 IISMAJORVERSION = "#6" AND
CREATE_IIS_SITE
 
 



 
  
...

There are a number of iis:WebSite elements, but all of them are wrapped
in a component. 
Please, let me know if the snippet above doesn't contain what you were
asking for.

NOTE: it is reproduced when I'm creating a new site. If a user chooses
to use existent site, everything goes fine.

Thank you!

-- Yan


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Tuesday, September 01, 2009 6:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

Could you post appropriate excerpts from your authoring, if possible?

Is it possible you have at least one web locator record involved here (a
web element with no associated component)? This looks exactly like the
issue where a web element is trying to install to a location found by a
web locator record, but the web locator couldn't find what it was
looking for on the local machine.

Thanks,
Mike Carlson

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, September 01, 2009 7:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

I forgot to mention: I use the released version of WiX 3.0.5419.0.
Thanks in advance for any help.

-- Yan


-Original Message-
From: Yan Sklyarenko 
Sent: Tuesday, September 01, 2009 2:53 PM
To: wix-users@lists.sourceforge.net
Subject: Failed while processing WebDirs

Hello WiX community,

I have faced with the following error in my installation project. I have
a component, which contains a web site, which in its turn contains a
WebDir element. Hence, the plan is to create a web site on install with
WebDir.
However, when I try to install this package, it fails with the following
error:

...
ConfigureIIsExec:  A matching web object in memory was found, but the
web object in memory has no associated base
ConfigureIIsExec:  Error 0x80070002: Failed to find Web base
ConfigureIIsExec:  Error 0x80070002: Failed to get base of web for
WebDir
ConfigureIIsExec:  Error 0x80070002: failed while processing WebDirs
Error 26003. Failed while processing WebDirs.  (-2147024894 )
...

I'm sure the folder pointed by WebDir exists when the action executes. 
What is the problem here? It seems that the newly created website is not
committed to the metabase, when it is requested by the WebDir servicing
code...

Has anyone seen this before? Any workaround?

Thanks,

-- Yan



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-D

Re: [WiX-users] Failed while processing WebDirs

[Mike Carlson (DEV DIV)]

Thanks - could you also paste the contents of IIS6newsite.wxi?

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, September 01, 2009 8:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

Hi Mike,

Thanks for your feedback.
Here is the excerpt from my authoring:

...
  
 IISMAJORVERSION = "#6" AND
CREATE_IIS_SITE
 
 



 
  
...

There are a number of iis:WebSite elements, but all of them are wrapped
in a component. 
Please, let me know if the snippet above doesn't contain what you were
asking for.

NOTE: it is reproduced when I'm creating a new site. If a user chooses
to use existent site, everything goes fine.

Thank you!

-- Yan


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Tuesday, September 01, 2009 6:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

Could you post appropriate excerpts from your authoring, if possible?

Is it possible you have at least one web locator record involved here (a
web element with no associated component)? This looks exactly like the
issue where a web element is trying to install to a location found by a
web locator record, but the web locator couldn't find what it was
looking for on the local machine.

Thanks,
Mike Carlson

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, September 01, 2009 7:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

I forgot to mention: I use the released version of WiX 3.0.5419.0.
Thanks in advance for any help.

-- Yan


-Original Message-
From: Yan Sklyarenko 
Sent: Tuesday, September 01, 2009 2:53 PM
To: wix-users@lists.sourceforge.net
Subject: Failed while processing WebDirs

Hello WiX community,

I have faced with the following error in my installation project. I have
a component, which contains a web site, which in its turn contains a
WebDir element. Hence, the plan is to create a web site on install with
WebDir.
However, when I try to install this package, it fails with the following
error:

...
ConfigureIIsExec:  A matching web object in memory was found, but the
web object in memory has no associated base
ConfigureIIsExec:  Error 0x80070002: Failed to find Web base
ConfigureIIsExec:  Error 0x80070002: Failed to get base of web for
WebDir
ConfigureIIsExec:  Error 0x80070002: failed while processing WebDirs
Error 26003. Failed while processing WebDirs.  (-2147024894 )
...

I'm sure the folder pointed by WebDir exists when the action executes. 
What is the problem here? It seems that the newly created website is not
committed to the metabase, when it is requested by the WebDir servicing
code...

Has anyone seen this before? Any workaround?

Thanks,

-- Yan



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists

Re: [WiX-users] Custom action from a dialog

[Oscar Newkerk]

I finally figured out that the Log messages were just not going to show up and 
wrote a property to see some debug info.

Now I'm seeing something even weirder.  Wix version:  3.0.5419.0

I have a custom UI sequence that I based on the standard WixUI_InstallDir 
sequence.

In my product.wix I declare a couple of properties and reference the dialog 
sequence:







In the custom dialog to validate the PID I hook my custom action to the "Next" 
control.  The custom action 
uses the value of PIDKEY as the key and sets a property "VALIDATEKEY" to 
indicate the result.


1






In the custom action code session["PIDKEY"] is null.  However, session["None"] 
returns the value entered in the Key control.

I figured this out looking in the setup log file where I found this:

Property(C): PIDKEY = None
Property(C): None = "the PID value I entered"

Any idea what I'm doing wrong with the properties?

Thanks

Oscar

-Original Message-
From: Richard [mailto:legal...@xmission.com] 
Sent: Monday, August 31, 2009 3:57 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom action from a dialog


1) When you invoke a CA through a dialog control event, the messages
you attempt to write to the log don't end up in the log.  You can work
around this for debugging by using MessageBox or OutputDebugString to
write out logging information.

2) When you invoke a CA through a dialog control event, and the CA
sets properties, the dialog processing logic in the MSI runtime
doesn't realize you've changed properties and it doesn't re-evaluate
subsequent event conditions using the new property value.  You can
work around this by inserting a phony event that sets the property to
its value, i.e. Foo = [Foo].
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 

  Legalize Adulthood! 



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Failed while processing WebDirs

[Yan Sklyarenko]

Hi Mike,

Thanks for your feedback.
Here is the excerpt from my authoring:

...
  
 IISMAJORVERSION = "#6" AND
CREATE_IIS_SITE
 
 



 
  
...

There are a number of iis:WebSite elements, but all of them are wrapped
in a component. 
Please, let me know if the snippet above doesn't contain what you were
asking for.

NOTE: it is reproduced when I'm creating a new site. If a user chooses
to use existent site, everything goes fine.

Thank you!

-- Yan


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Tuesday, September 01, 2009 6:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

Could you post appropriate excerpts from your authoring, if possible?

Is it possible you have at least one web locator record involved here (a
web element with no associated component)? This looks exactly like the
issue where a web element is trying to install to a location found by a
web locator record, but the web locator couldn't find what it was
looking for on the local machine.

Thanks,
Mike Carlson

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, September 01, 2009 7:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

I forgot to mention: I use the released version of WiX 3.0.5419.0.
Thanks in advance for any help.

-- Yan


-Original Message-
From: Yan Sklyarenko 
Sent: Tuesday, September 01, 2009 2:53 PM
To: wix-users@lists.sourceforge.net
Subject: Failed while processing WebDirs

Hello WiX community,

I have faced with the following error in my installation project. I have
a component, which contains a web site, which in its turn contains a
WebDir element. Hence, the plan is to create a web site on install with
WebDir.
However, when I try to install this package, it fails with the following
error:

...
ConfigureIIsExec:  A matching web object in memory was found, but the
web object in memory has no associated base
ConfigureIIsExec:  Error 0x80070002: Failed to find Web base
ConfigureIIsExec:  Error 0x80070002: Failed to get base of web for
WebDir
ConfigureIIsExec:  Error 0x80070002: failed while processing WebDirs
Error 26003. Failed while processing WebDirs.  (-2147024894 )
...

I'm sure the folder pointed by WebDir exists when the action executes. 
What is the problem here? It seems that the newly created website is not
committed to the metabase, when it is requested by the WebDir servicing
code...

Has anyone seen this before? Any workaround?

Thanks,

-- Yan



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integration and deployment - and
focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Failed while processing WebDirs

[Mike Carlson (DEV DIV)]

Could you post appropriate excerpts from your authoring, if possible?

Is it possible you have at least one web locator record involved here (a web 
element with no associated component)? This looks exactly like the issue where 
a web element is trying to install to a location found by a web locator record, 
but the web locator couldn't find what it was looking for on the local machine.

Thanks,
Mike Carlson

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, September 01, 2009 7:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Failed while processing WebDirs

I forgot to mention: I use the released version of WiX 3.0.5419.0.
Thanks in advance for any help.

-- Yan


-Original Message-
From: Yan Sklyarenko 
Sent: Tuesday, September 01, 2009 2:53 PM
To: wix-users@lists.sourceforge.net
Subject: Failed while processing WebDirs

Hello WiX community,

I have faced with the following error in my installation project. I have
a component, which contains a web site, which in its turn contains a
WebDir element. Hence, the plan is to create a web site on install with
WebDir.
However, when I try to install this package, it fails with the following
error:

...
ConfigureIIsExec:  A matching web object in memory was found, but the
web object in memory has no associated base
ConfigureIIsExec:  Error 0x80070002: Failed to find Web base
ConfigureIIsExec:  Error 0x80070002: Failed to get base of web for
WebDir
ConfigureIIsExec:  Error 0x80070002: failed while processing WebDirs
Error 26003. Failed while processing WebDirs.  (-2147024894 )
...

I'm sure the folder pointed by WebDir exists when the action executes. 
What is the problem here? It seems that the newly created website is not
committed to the metabase, when it is requested by the WebDir servicing
code...

Has anyone seen this before? Any workaround?

Thanks,

-- Yan


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Failed while processing WebDirs

[Yan Sklyarenko]

I forgot to mention: I use the released version of WiX 3.0.5419.0.
Thanks in advance for any help.

-- Yan


-Original Message-
From: Yan Sklyarenko 
Sent: Tuesday, September 01, 2009 2:53 PM
To: wix-users@lists.sourceforge.net
Subject: Failed while processing WebDirs

Hello WiX community,

I have faced with the following error in my installation project. I have
a component, which contains a web site, which in its turn contains a
WebDir element. Hence, the plan is to create a web site on install with
WebDir.
However, when I try to install this package, it fails with the following
error:

...
ConfigureIIsExec:  A matching web object in memory was found, but the
web object in memory has no associated base
ConfigureIIsExec:  Error 0x80070002: Failed to find Web base
ConfigureIIsExec:  Error 0x80070002: Failed to get base of web for
WebDir
ConfigureIIsExec:  Error 0x80070002: failed while processing WebDirs
Error 26003. Failed while processing WebDirs.  (-2147024894 )
...

I'm sure the folder pointed by WebDir exists when the action executes. 
What is the problem here? It seems that the newly created website is not
committed to the metabase, when it is requested by the WebDir servicing
code...

Has anyone seen this before? Any workaround?

Thanks,

-- Yan


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to check the prerequisite software install?

[Sebastian Brand (Instyler Software)]

Hi,

Add a  right under . The message in the @Message
attribute will be shown whenever the condition is false, and setup is
aborted. 
The condition should contain a Property that gets initialized with
 or  to find a registry value or file from the
other software to identify if it is installed.

Example:


   
  

ADOBEREADER9INSTALLED
  <...>



Best regards,
Sebastian Brand

Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com


-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com] 
Sent: Tuesday, September 01, 2009 14:46
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to check the prerequisite software install?

Hi Wix-users,
 
My software needs another software (Sybase) as the prerequisite.
Therefore I need to check whether Sybase has been installed in the machine
and show the warning message if it is not installed. How can I define the
condition in the installer?
 
Best regards,
 
 
Chunyan

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to check the prerequisite software install?

[Jiang, Chunyan (GE Healthcare)]

Hi Wix-users,
 
My software needs another software (Sybase) as the prerequisite.
Therefore I need to check whether Sybase has been installed in the
machine and show the warning message if it is not installed. How can I
define the condition in the installer?
 
Best regards,
 
 
Chunyan
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Failed while processing WebDirs

[Yan Sklyarenko]

Hello WiX community,

I have faced with the following error in my installation project. I have
a component, which contains a web site, which in its turn contains a
WebDir element. Hence, the plan is to create a web site on install with
WebDir.
However, when I try to install this package, it fails with the following
error:

...
ConfigureIIsExec:  A matching web object in memory was found, but the
web object in memory has no associated base
ConfigureIIsExec:  Error 0x80070002: Failed to find Web base
ConfigureIIsExec:  Error 0x80070002: Failed to get base of web for
WebDir
ConfigureIIsExec:  Error 0x80070002: failed while processing WebDirs
Error 26003. Failed while processing WebDirs.  (-2147024894 )
...

I'm sure the folder pointed by WebDir exists when the action executes. 
What is the problem here? It seems that the newly created website is not
committed to the metabase, when it is requested by the WebDir servicing
code...

Has anyone seen this before? Any workaround?

Thanks,

-- Yan


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MsiViewModify vs. MsiSetProperty

[Yan Sklyarenko]

Thanks a lot, Blair! You were absolutely right!
If I use MsiSetProperty, I can see in the log file that the property is
set within my custom action. Otherwise (in case of MsiViewModify) the
property doesn't get set and it is set later to the default value - in
my case, the drive root which has the most of free space.

Thanks again for your help!

-- Yan


-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Wednesday, August 19, 2009 12:11 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] MsiViewModify vs. MsiSetProperty

A debug verbose log may tell you when different properties were set, so
that
is a good start. It may depend on your particular version of MSI, etc.

The directory table itself is resolved during CostFinalize, but any
properties it makes use of may have been set before then (such as
TARGETDIR/ROOTDRIVE/ProgramFilesFolder/etc.) and would come from the
session
properties instead of directly from the property table.

I don't know when the Property table is processed (which would insert
each
non-empty entry into the current session). It is possible that table is
processed very early on, which would mean that adding temporary rows to
the
Property table would only influence changes to a different sequence
(e.g.
from UI to Execute). However, not all session values come from the
Property
table.

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Tuesday, August 18, 2009 1:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MsiViewModify vs. MsiSetProperty

Thanks for the answer.
The custom action was placed before CostFinalize, I didn't change this
position. 
 
>> which is gradually built up a query at a time
I'm not sure I understand this...  could you please explain?
 
>> It is all a matter of your position in your sequence
I'm populating the Directory table before CostFinalize, which should be
ok I
think - the directories are not resolved by this time, right?
 
-- Yan


From: Blair [mailto:os...@live.com]
Sent: Tue 8/18/2009 23:39
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] MsiViewModify vs. MsiSetProperty



Changing the database view will change all future queries into that
database. Changing the current property set (which is gradually built up
a
query at a time) will change all future uses of that property.

It is all a matter of your position in your sequence (and where the
actions
before and after you are getting their data from).

-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Tuesday, August 18, 2009 1:13 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MsiViewModify vs. MsiSetProperty

Hello MSI gurus,

I've faced with an interesting issue, which is now a kind of academic
interest for me.
I had to modify the MSI tables from an immediate custom action using
DTF. I
was using View.Modify method with InsertTemporary option, as it is the
only
way to "change" the MSI database at runtime. All the tables required
were
addressed by this technique, including Property.

However, I mentioned that my custom action behaves incorrectly. I've
been
setting a property containing the disk root (e.g. D:\) and then
referenced
that property from Directory table. But in the log file that property
fell
back to a disk root with the most of free space (as if the TARGETDIR
wasn't
set).
When I changed the property set operation from View.Modify to
session["PROP_NAME"] = "D:\", everything started working correctly.

So, my question is what's the difference between MsiViewModify and
MsiSetProperty? And are there any recommendations where to use each?

Thank you.

-- Yan


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus
on what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus
on what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users





--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day 
trial. Simplify your report design, integra

Re: [WiX-users] packa...@installerversion

[Steve Lessard]

Maybe I am have the wrong impression of what this property is used for.  I 
thought this property is used to enforce the minimum version of Windows 
Installer required to run the MSI.  Is that not correct?

If it is correct, what are the possible values for currently released versions 
of Windows Installer?  In most examples I've found the values are 200 or 300.  
Is 450 the correct value for Windows Installer 4.5?  Is 500 the correct value 
for Windows Installer 5.0?




-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Monday, August 31, 2009 8:51 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] packa...@installerversion

The Package element populates the MSI's Summary Information Stream.

The InstallerVersion attribute populates the "Page Count Summary Property"
(http://msdn.microsoft.com/en-us/library/aa370570(VS.85).aspx) (aka, the 
Minimum Installer Version) of MSI files.

According to (http://msdn.microsoft.com/en-us/library/aa372045(VS.85).aspx)
it is of type VT_I4 (aka 32-bit signed integer).

-Original Message-
From: Steve Lessard [mailto:sless...@microsoft.com]
Sent: Monday, August 31, 2009 6:54 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] packa...@installerversion



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users