date:20131106

I thought that might be the issue as well. I can't find another reference.
So, I made a new solution that only contains a brand new WiX installer
project.  The same build errors occur.

1. New 2012 solution, single WiX v3.7 (.msi) project
2. Added manufacturer and uppper-cased UpgradeCode in the skeleton
Product.wxs
3. copied WixUI_Minimal.wxs to the project folder and renamed it to
WiXUI_Minimal_Modified.wxs.  Added WiXUI_Minimal_Modified.wxs to the
project.
4. Edited WiXUI_Minimal_Modified.wxs so that its UI element Id now reads
UI Id=WixUI_Minimal_Modified
5. Added UIRef Id=WixUI_Minimal_Modified/ to Product.wxs
6. Clean/Rebuild, results in these errors...

...
...\WiXUITester\WixUI_Minimal_Modified.wxs(35,0): error LGHT0094:
Unresolved reference to symbol 'Dialog:ErrorDlg' in section 'Fragment:'.
...\WiXUITester\WiXUITester\WixUI_Minimal_Modified.wxs(36,0): error
LGHT0094: Unresolved reference to symbol 'Dialog:FatalError' in section
'Fragment:'.
...

7. Add dll reference to C:\Program Files (x86)\WiX Toolset
v3.7\bin\\WixUIExtension.dll
8. Clean/Rebuild, results in these errors...

...
...\WiXUITester\WiXUITester\WixUI_Minimal_Modified.wxs(56,0): error
LGHT0091: Duplicate symbol
'ControlEvent:WelcomeDlg/Next/NewDialog/VerifyReadyDlg/Installed AND PATCH'
found. This typically means that an Id is duplicated. Check to make sure
all your identifiers of a given type (File, Component, Feature) are unique.
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(56,0):
error LGHT0092: Location of symbol related to previous error.
...\WiXUITester\WiXUITester\WixUI_Minimal_Modified.wxs(33,0): error
LGHT0091: Duplicate symbol 'Property:WixUI_Mode' found. This typically
means that an Id is duplicated. Check to make sure all your identifiers of
a given type (File, Component, Feature) are unique.
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(33,0):
error LGHT0092: Location of symbol related to previous error.
...

I would have expected my above greenfield approach to have worked.  Maybe
some sort of environment thing?




On Tue, Nov 5, 2013 at 11:34 PM, Blair Murri os...@live.com wrote:

 Search your entire installer source code and make sure there isn't another
 UIRef pointing to WixUI_Minimal lurking around in there anywhere. You
 can't reference both.

  Date: Tue, 5 Nov 2013 17:26:51 -0500
  From: yellowjacketl...@gmail.com
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Modifying a stock WixUI sequence
 clarification...[P]
 
  Thanks that's what I thought...
 
  Here's what I've done...
 
  I copied WixUI_Minimal.wxs into my project and renamed it to
  WixUI_Minimal_Modified.wxs.  Then I changed the UI's Id attribute to
 read...
 
  UI Id=WixUI_Minimal_Modified
 
  In my Product.wxs I added...
 
  UIRef Id=WixUI_Minimal_Modified/
 
  If I build I get a bunch of errors about missing dialogs (ErrorDlg,
  FatalError, etc.).  So, I add a dll reference to WixUIExtension.
 
  Now I get a bunch of duplicate symbol errors with WixUI_Minimal.wxs.
 
  ...
  ...\MyProject\WixUI_Minimal_Modified.wxs(70,0): error LGHT0091: Duplicate
  symbol 'ControlEvent:WelcomeDlg/Next/NewDialog/VerifyReadyDlg/Installed
 AND
  PATCH' found. This typically means that an Id is duplicated. Check to
 make
  sure all your identifiers of a given type (File, Component, Feature) are
  unique.
 
 E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(56,0):
  error LGHT0092: Location of symbol related to previous error.
  ...
 
  I must have missed a step somewhere... any ideas?
 
 
 
  On Tue, Nov 5, 2013 at 4:58 PM, Steven Ogilvie steven.ogil...@titus.com
 wrote:
 
   Classification: Public
   No you don't need to physically copy the wxs file, you just need to
 copy
   the UI element from that wxs file into your code. Then you need to add
   your dialog I.e.
   DialogRef Id=MyNewDlg/
  
   You can substitute your dialog for the LicenseAgreementDlg dialog...
  
   i.e.
  
   UI Id=WixUI_MYCOMPANYInstallDir
 TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
 TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
 TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
   Bold=yes /
  
 Property Id=DefaultUIFont Value=WixUI_Font_Normal /
 Property Id=WixUI_Mode Value=InstallDir /
  
 DialogRef Id=BrowseDlg /
 DialogRef Id=DiskCostDlg /
 DialogRef Id=ErrorDlg /
 DialogRef Id=FatalError /
 DialogRef Id=FilesInUse /
 DialogRef Id=MsiRMFilesInUse /
 DialogRef Id=PrepareDlg /
 DialogRef Id=ProgressDlg /
 DialogRef Id=ResumeDlg /
 DialogRef Id=UserExit /
  
 Publish Dialog=BrowseDlg Control=OK Event=DoAction
   Value=WixUIValidatePath Order=31/Publish
 Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
   Value=InvalidDirDlg
   Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish
  
 Publish Dialog=ExitDialog

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-11-06 Thread Tobias Erichsen

Hi,

thanks for that input as well.  My driver's inf-file does not contain any 
RunOnce entries.
So I assume that burn is doing that somewhere...

Could Rob or Bob possibly chime in on this?  I'd gladly do some more 
digging/debugging,
but as I still do not fully understand the overall architecture on how burn  
MSIs interact
during the installation-process, I'd be glad to get some pointers on where to 
focus my
search...

Best regards,
Tobias


Von: tj leigh [tjle...@outlook.com]
Gesendet: Mittwoch, 6. November 2013 12:25
Bis: wix-users@lists.sourceforge.net
Betreff: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) 
opens second burn's window.

http://blogs.msdn.com/b/junfeng/archive/2006/09/19/761765.aspx says this:

Be careful about RunOnce registry key: It may run before system restart.

According to KB 281829, RunOnce registry key will run in the following cases:

1. At the end of installation through InstallFromHinfSection even in the cases 
where you must restart the computer.

2. After the default processing of DIF_INSTALLDEVICE even if you must restart 
the computer (with the exception of server-side processing).

3. After the system has been restarted.

This means, RunOnce registry key entries may be executed immediately after a 
device driver installation, which may happen at any given time.

---
Hi Blair,

thanks for the input.  I let the whole thing run while also using Process 
Monitor to log all
processes being created and you were right:

The last rtpMIDISetup.exe process (showing the erroneous dialog) is 
instantiated from
runonce.exe, which itself is instantiated from MsiExec.exe...

The whole chain goes like this:

services.exe
msiexec.exe /V
msiexec.exe  -Embedding F815A8F1DDE9C0C1DB2AB19224A4B71C M Global\MSI
runonce.exe -r
rtpMIDISetup.exe /burn.log.append 
C:\DOKUME~1\ADMINI~1\LOKALE~1\Temp\rtpMIDI_20131106100345.log /burn.runonce

I still don't know what actually causes this - it is definately not my WIX-code 
or CA installing the driver
(at least not consciously).  What do you mean by reloading some profile?

Best regards,
Tobias

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Bundle installing VS - returns 0x80048bc7

2013-11-06 Thread rowbot

Hi,

Got a bundle that installs VS2012 or VS2013 Shells..

I've noticed that sometimes, we get a 0x80048bc7 (pending restart required)

It seems to be if VS updated some .NET framework components...

Our bundle doesn't catch it as 3010 etc... so what does 0x80048bc7 translate
to?

In the VS admin guide
(http://msdn.microsoft.com/en-us/library/vstudio/ee225238.aspx) it's not
translated into a 4-digit error code..

Thanks,




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-installing-VS-returns-0x80048bc7-tp7590319.html
Sent from the wix-users mailing list archive at Nabble.com.

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Classification: Public
You don't need to ADD the WXS file to your project, you only need to copy the 
UI element from that file...
Nor do you need to physically copy it to your project either...

If you follow the steps I provided below you will be fine...

1. in your PRODUCT.WXS file add the UI element:
UI Id=WixUI_MYInstallDir
  TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
  TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
  TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes /

  Property Id=DefaultUIFont Value=WixUI_Font_Normal /
  Property Id=WixUI_Mode Value=InstallDir /

  DialogRef Id=BrowseDlg /
  DialogRef Id=DiskCostDlg /
  DialogRef Id=ErrorDlg /
  DialogRef Id=FatalError /
  DialogRef Id=FilesInUse /
  DialogRef Id=MsiRMFilesInUse /
  DialogRef Id=PrepareDlg /
  DialogRef Id=ProgressDlg /
  DialogRef Id=ResumeDlg /
  DialogRef Id=UserExit /

  Publish Dialog=BrowseDlg Control=OK Event=DoAction 
Value=WixUIValidatePath Order=31/Publish
  Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog 
Value=InvalidDirDlg 
Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish

  Publish Dialog=ExitDialog Control=Finish Event=EndDialog 
Value=Return Order=9991/Publish

  Publish Dialog=WelcomeDlg Control=Next Event=NewDialog 
Value=LicenseAgreementDlgNOT Installed/Publish
  Publish Dialog=WelcomeDlg Control=Next Event=NewDialog 
Value=VerifyReadyDlgInstalled AND PATCH/Publish

  Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog 
Value=WelcomeDlg1/Publish
  Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog 
Value=VerifyReadyDlgLicenseAccepted = 1/Publish

  Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog 
Value=LicenseAgreementDlg Order=1NOT Installed/Publish
  Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog 
Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
  Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog 
Value=WelcomeDlg Order=2Installed AND PATCH/Publish

  Publish Dialog=MaintenanceWelcomeDlg Control=Next Event=NewDialog 
Value=MaintenanceTypeDlg1/Publish

  Publish Dialog=MaintenanceTypeDlg Control=RepairButton 
Event=NewDialog Value=VerifyReadyDlg1/Publish
  Publish Dialog=MaintenanceTypeDlg Control=RemoveButton 
Event=NewDialog Value=VerifyReadyDlg1/Publish
  Publish Dialog=MaintenanceTypeDlg Control=Back Event=NewDialog 
Value=MaintenanceWelcomeDlg1/Publish

/UI

UIRef Id=WixUI_Common /

2. Substitute your new dialog for LicenseAgreementDlg so you have a Next and 
Back action for it:
  Publish Dialog= MyNewDlg  Control=Back Event=NewDialog 
Value=WelcomeDlg1/Publish
  Publish Dialog= MyNewDlg  Control=Next Event=NewDialog 
Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to the list of 
dialogs:
DialogRef Id=MyNewDlg /
4. make sure you have a Back action for your dialog in the VerifyReadyDlg:
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog Value= 
MyNewDlg  Order=1NOT Installed/Publish

5. Add your new MyNewDlg.wxs to your project.

Steve

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: November-06-13 7:36 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

I thought that might be the issue as well. I can't find another reference.
So, I made a new solution that only contains a brand new WiX installer project. 
 The same build errors occur.

1. New 2012 solution, single WiX v3.7 (.msi) project 2. Added manufacturer and 
uppper-cased UpgradeCode in the skeleton Product.wxs 3. copied 
WixUI_Minimal.wxs to the project folder and renamed it to 
WiXUI_Minimal_Modified.wxs.  Added WiXUI_Minimal_Modified.wxs to the project.
4. Edited WiXUI_Minimal_Modified.wxs so that its UI element Id now reads UI 
Id=WixUI_Minimal_Modified 5. Added UIRef Id=WixUI_Minimal_Modified/ to 
Product.wxs 6. Clean/Rebuild, results in these errors...

...
...\WiXUITester\WixUI_Minimal_Modified.wxs(35,0): error LGHT0094:
Unresolved reference to symbol 'Dialog:ErrorDlg' in section 'Fragment:'.
...\WiXUITester\WiXUITester\WixUI_Minimal_Modified.wxs(36,0): error
LGHT0094: Unresolved reference to symbol 'Dialog:FatalError' in section 
'Fragment:'.
...

7. Add dll reference to C:\Program Files (x86)\WiX Toolset 
v3.7\bin\\WixUIExtension.dll 8. Clean/Rebuild, results in these errors...

...
...\WiXUITester\WiXUITester\WixUI_Minimal_Modified.wxs(56,0): error
LGHT0091: Duplicate symbol
'ControlEvent:WelcomeDlg/Next/NewDialog/VerifyReadyDlg/Installed AND PATCH'
found. This typically means that an Id is duplicated. Check to make sure all 
your identifiers of a given type (File, Component, Feature) are unique.
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(56,0):
error LGHT0092: Location of symbol related to previous error.

[WiX-users] Inserting a dialog when user click on the Advanced button

2013-11-06 Thread Pierre-Alain GALTIER

Hello,

I have a custom dialog box that I’ve successfully inserted between the 
LicenseAgreementDlg and InstallDirDlg using WixUI_InstallDir template.
Now I want to use the WixUI_Advanced template and insert the same dialogbox 
when user press the “Advanced” or “Install” buttons.

… and I failed 

I added the following line but didn’t show my dialog when user click on 
Advanced button and I do not understand the reason :
  Publish Dialog=AdvancedWelcomeEulaDlg Control=Advanced 
Event=NewDialog Value=VIV_SelectArchDlgLicenseAccepted = 1/Publish

Any advise ?

Thanks



Pierre-Alain GALTIER
Responsable Pôle Informatique  Technologie
IT Department Manager
pierre-alain.galt...@vivelys.com | www.vivelys.com
Tel. +33 (0)4 67 85 68 43 | Fax +33 (0)4 67 85 68 41


--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] platform x86 vs AnyCPU problems

2013-11-06 Thread Phill Hogland

If I understand the issue, I would go to each of the two project files
(Prod.*proj and TEST.*proj), right click on each file and select 'Unload',
then right click and select Edit Prod.wixproj (or TEST.wixproj). Then
compare the working to the non-working file. It sounds like your OutputName
element in the 'global' (top most) PropertyGroup has been overwritten to
'Any CPU' (which is a possible value VS might pass into $(Platform) MSBuild
property).

I was working on a similar issue in my build process recently, because I
have a mixture of wix, C#, and C++ projects which require different platform
specifications. In the course of doing that I came across the chm (and
Candle /? output) which indicates that Package/@Platform (and -d:Platform)
is discouraged (or deprecated) and that -arch is prefered. So I added the
InstallerPlatform element to my project files and set it to x64 in the
situation where I needed the -arch=x64.

When you finish editing a .*proj file you need to close it and then right
click and 'reload' it. I have also found that if you change any .target or
.prop file that is imported by the project, you really need to close the
solution and re-open the solution (so I often do that anyway just to make
sure that I know that my new changes have been loaded prior to testing
them). If you do not close and reopen the solution, imported targets stay
in memory and do not reflect changes made after they were first loaded (at
least that is the behavior of VS2010).

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/platform-x86-vs-AnyCPU-problems-tp7590303p7590322.html
Sent from the wix-users mailing list archive at Nabble.com.

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Inserting a dialog when user click on the Advanced button [P]

Classification: Public
What does the MSI logging reveal? ( to enable MSI logging  check this out: 
http://support.microsoft.com/kb/223300)

-Original Message-
From: Pierre-Alain GALTIER [mailto:pierre-alain.galt...@vivelys.com]
Sent: November-06-13 8:58 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Inserting a dialog when user click on the Advanced button

Hello,

I have a custom dialog box that I’ve successfully inserted between the 
LicenseAgreementDlg and InstallDirDlg using WixUI_InstallDir template.
Now I want to use the WixUI_Advanced template and insert the same dialogbox 
when user press the “Advanced” or “Install” buttons.

… and I failed L

I added the following line but didn’t show my dialog when user click on 
Advanced button and I do not understand the reason :
  Publish Dialog=AdvancedWelcomeEulaDlg Control=Advanced 
Event=NewDialog Value=VIV_SelectArchDlgLicenseAccepted = 1/Publish

Any advise ?

Thanks



Pierre-Alain GALTIER
Responsable Pôle Informatique  Technologie IT Department Manager 
pierre-alain.galt...@vivelys.com | www.vivelys.com Tel. +33 (0)4 67 85 68 43 | 
Fax +33 (0)4 67 85 68 41


--
November Webinars for C, C++, Fortran Developers Accelerate application 
performance with scalable programming models. Explore techniques for threading, 
error checking, porting, and tuning. Get the most from the latest Intel 
processors and coprocessors. See abstracts and register 
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 
This message has been marked as Public by Steven Ogilvie on November-06-13 
9:17:48 AM.

The above classification labels were added to the message by TITUS Message 
Classification. For more information visit www.titus.com.

 


--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Ugh!  This makes no sense to me...

I moved my UIRef in my Product.wxs outside of the Product section and
added to its own fragment in the Product.wxs file

  Fragment
UIRef Id=WixUI_Minimal_Modified/
  /Fragment

And removed the reference to WixUIExtension.dll, now it builds?  WTF?

Why did moving the UIRef outside of the Product section change the
behavior?


On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 You don't need to ADD the WXS file to your project, you only need to
 copy the UI element from that file...
 Nor do you need to physically copy it to your project either...

 If you follow the steps I provided below you will be fine...

 1. in your PRODUCT.WXS file add the UI element:
 UI Id=WixUI_MYInstallDir
   TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
   TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
   TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
 Bold=yes /

   Property Id=DefaultUIFont Value=WixUI_Font_Normal /
   Property Id=WixUI_Mode Value=InstallDir /

   DialogRef Id=BrowseDlg /
   DialogRef Id=DiskCostDlg /
   DialogRef Id=ErrorDlg /
   DialogRef Id=FatalError /
   DialogRef Id=FilesInUse /
   DialogRef Id=MsiRMFilesInUse /
   DialogRef Id=PrepareDlg /
   DialogRef Id=ProgressDlg /
   DialogRef Id=ResumeDlg /
   DialogRef Id=UserExit /

   Publish Dialog=BrowseDlg Control=OK Event=DoAction
 Value=WixUIValidatePath Order=31/Publish
   Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
 Value=InvalidDirDlg
 Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish

   Publish Dialog=ExitDialog Control=Finish Event=EndDialog
 Value=Return Order=9991/Publish

   Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=LicenseAgreementDlgNOT Installed/Publish
   Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=VerifyReadyDlgInstalled AND PATCH/Publish

   Publish Dialog=LicenseAgreementDlg Control=Back
 Event=NewDialog Value=WelcomeDlg1/Publish
   Publish Dialog=LicenseAgreementDlg Control=Next
 Event=NewDialog Value=VerifyReadyDlgLicenseAccepted = 1/Publish

   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=LicenseAgreementDlg Order=1NOT Installed/Publish
   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=WelcomeDlg Order=2Installed AND PATCH/Publish

   Publish Dialog=MaintenanceWelcomeDlg Control=Next
 Event=NewDialog Value=MaintenanceTypeDlg1/Publish

   Publish Dialog=MaintenanceTypeDlg Control=RepairButton
 Event=NewDialog Value=VerifyReadyDlg1/Publish
   Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
 Event=NewDialog Value=VerifyReadyDlg1/Publish
   Publish Dialog=MaintenanceTypeDlg Control=Back
 Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish

 /UI

 UIRef Id=WixUI_Common /

 2. Substitute your new dialog for LicenseAgreementDlg so you have a Next
 and Back action for it:
   Publish Dialog= MyNewDlg  Control=Back Event=NewDialog
 Value=WelcomeDlg1/Publish
   Publish Dialog= MyNewDlg  Control=Next Event=NewDialog
 Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to the
 list of dialogs:
 DialogRef Id=MyNewDlg /
 4. make sure you have a Back action for your dialog in the VerifyReadyDlg:
 Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog Value=
 MyNewDlg  Order=1NOT Installed/Publish

 5. Add your new MyNewDlg.wxs to your project.

 Steve

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 7:36 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 I thought that might be the issue as well. I can't find another reference.
 So, I made a new solution that only contains a brand new WiX installer
 project.  The same build errors occur.

 1. New 2012 solution, single WiX v3.7 (.msi) project 2. Added manufacturer
 and uppper-cased UpgradeCode in the skeleton Product.wxs 3. copied
 WixUI_Minimal.wxs to the project folder and renamed it to
 WiXUI_Minimal_Modified.wxs.  Added WiXUI_Minimal_Modified.wxs to the
 project.
 4. Edited WiXUI_Minimal_Modified.wxs so that its UI element Id now reads
 UI Id=WixUI_Minimal_Modified 5. Added UIRef
 Id=WixUI_Minimal_Modified/ to Product.wxs 6. Clean/Rebuild, results in
 these errors...

 ...
 ...\WiXUITester\WixUI_Minimal_Modified.wxs(35,0): error LGHT0094:
 Unresolved reference to symbol 'Dialog:ErrorDlg' in section 'Fragment:'.
 ...\WiXUITester\WiXUITester\WixUI_Minimal_Modified.wxs(36,0): error
 LGHT0094: Unresolved reference to symbol 'Dialog:FatalError' in section
 'Fragment:'.
 ...

 7. Add dll reference to C:\Program Files (x86)\WiX Toolset
 v3.7\bin\\WixUIExtension.dll 8. Clean/Rebuild, results in these

Re: [WiX-users] Inserting a dialog when user click on the Advanced button [P]

2013-11-06 Thread Pierre-Alain GALTIER

Thank you

When I hit the Advanced button in the Welcome Eula Dialogbox, the next dialog 
box is InstallDir and the logging said :

Action 15:57:31: AdvancedWelcomeEulaDlg. 
Action start 15:57:31: AdvancedWelcomeEulaDlg.
Info 2898.For WixUI_Font_Title textstyle, the system created a 'Tahoma' font, 
in 0 character set, of 14 pixels height.
Action 15:57:32: AdvancedWelcomeEulaDlg. Dialog created
MSI (c) (44:14) [15:57:32:054]: Note: 1: 2205 2:  3: _RemoveFilePath 
MSI (c) (44:14) [15:57:32:058]: PROPERTY CHANGE: Modifying CostingComplete 
property. Its current value is '0'. Its new value: '1'.
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: Extension 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: Font 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: Class 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: TypeLib 
MSI (c) (44:14) [15:57:32:059]: Note: 1: 2727 2:  
MSI (c) (44:48) [15:57:34:894]: PROPERTY CHANGE: Adding LicenseAccepted 
property. Its value is '1'.
Action 15:57:36: InstallDirDlg. Dialog created


I could see my Dialog box only if I hit the Back button of the InstallDirDlg 
Dialog

Then the log said:
Action 16:01:39: AdvancedWelcomeEulaDlg. Dialog created
MSI (c) (D4:40) [16:01:39:968]: Note: 1: 2205 2:  3: _RemoveFilePath 
MSI (c) (D4:40) [16:01:39:972]: PROPERTY CHANGE: Modifying 
CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: Extension 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: Font 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: Class 
MSI (c) (D4:40) [16:01:39:972]: Note: 1: 2205 2:  3: TypeLib 
MSI (c) (D4:40) [16:01:39:973]: Note: 1: 2727 2:  
MSI (c) (D4:3C) [16:01:42:065]: PROPERTY CHANGE: Adding LicenseAccepted 
property. Its value is '1'.
Action 16:01:44: InstallDirDlg. Dialog created
I hit the back button...
Action 16:01:45: VIV_SelectArchDlg. Dialog created


Thank you for your help



Pierre-Alain GALTIER
Responsable Pôle Informatique  Technologie
IT Department Manager
pierre-alain.galt...@vivelys.com | www.vivelys.com
Tel. +33 (0)4 67 85 68 43 | Fax +33 (0)4 67 85 68 41

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: Wednesday, November 6, 2013 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Inserting a dialog when user click on the Advanced 
button [P]

Classification: Public
What does the MSI logging reveal? ( to enable MSI logging  check this out: 
http://support.microsoft.com/kb/223300)

-Original Message-
From: Pierre-Alain GALTIER [mailto:pierre-alain.galt...@vivelys.com]
Sent: November-06-13 8:58 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Inserting a dialog when user click on the Advanced button

Hello,

I have a custom dialog box that I’ve successfully inserted between the 
LicenseAgreementDlg and InstallDirDlg using WixUI_InstallDir template.
Now I want to use the WixUI_Advanced template and insert the same dialogbox 
when user press the “Advanced” or “Install” buttons.

… and I failed L

I added the following line but didn’t show my dialog when user click on 
Advanced button and I do not understand the reason :
  Publish Dialog=AdvancedWelcomeEulaDlg Control=Advanced 
Event=NewDialog Value=VIV_SelectArchDlgLicenseAccepted = 1/Publish

Any advise ?

Thanks



Pierre-Alain GALTIER
Responsable Pôle Informatique  Technologie IT Department Manager 
pierre-alain.galt...@vivelys.com | www.vivelys.com Tel. +33 (0)4 67 85 68 43 | 
Fax +33 (0)4 67 85 68 41


--
November Webinars for C, C++, Fortran Developers Accelerate application 
performance with scalable programming models. Explore techniques for threading, 
error checking, porting, and tuning. Get the most from the latest Intel 
processors and coprocessors. See abstracts and register 
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 
This message has been marked as Public by Steven Ogilvie on November-06-13 
9:17:48 AM.

The above classification labels were added to the message by TITUS Message 
Classification. For more

Re: [WiX-users] Inserting a dialog when user click on theAdvanced button [P]

2013-11-06 Thread Pierre-Alain GALTIER

The whole fragment is :

UI Id=myWixUI
  Property Id=VIV_SelectArchDlg_Back Value=AdvancedWelcomeEulaDlg /
  Property Id=VIV_SelectArchDlg_Next Value=InstallDirDlg /

  Publish Dialog=AdvancedWelcomeEulaDlg Control=Advanced 
Event=NewDialog Value=VIV_SelectArchDlgLicenseAccepted = 1/Publish
  Publish Dialog=InstallDirDlg Control=Back Event=NewDialog 
Value=VIV_SelectArchDlg1/Publish
  
  !-- 
==
   --
  !-- === Select Visio PLC architecture dialog 
 == --
  !-- ===  
 == 
--
  !-- ===  Buttons:
   == --
  !-- ===  [Back]  -   
 == --
  !-- ===  [Next]  -   
 == --
  !-- ===  [Cancel]-   
 == --
  !-- ===  
 == --
  !-- 
==
   --
  Dialog Id=VIV_SelectArchDlg Width=370 Height=270 
Title=!(loc.AdvancedWelcomeEulaDlg_Title) NoMinimize=yes
Control Id=BannerBitmap Type=Bitmap X=0 Y=0 Width=370 
Height=44 TabSkip=no Text=!(loc.InstallDirDlgBannerBitmap) /
Control Id=Title Type=Text X=15 Y=6 Width=200 Height=15 
Transparent=yes NoPrefix=yes
  Text[DlgTitleFont]Visio PLC type/Text
/Control
Control Id=Description Type=Text X=25 Y=23 Width=300 
Height=15 Transparent=yes NoPrefix=yes
  TextSelect your Visio PLC type/Text
/Control
Control Id=BannerLine Type=Line X=0 Y=44 Width=370 
Height=0 /

Control Id=RadioButtonGroupID Type=RadioButtonGroup X=30 Y=94 
Width=305 Height=100 Property=VIV_PLCTYPE
  RadioButtonGroup Property=VIV_PLCTYPE
RadioButton Value=SIEMENS X=0 Y=0 Width=200 Height=10 
Text=Siemens /
RadioButton Value=TWIDO X=0 Y=20 Width=200 Height=10 
Text=Twido (Schneider) /
  /RadioButtonGroup
/Control

Control Id=Back Type=PushButton X=180 Y=243 Width=56 
Height=17 Text=!(loc.WixUIBack)
  Publish Event=NewDialog 
Value=[VIV_SelectArchDlg_Back]![CDATA[1]]/Publish
/Control
Control Id=Next Type=PushButton X=236 Y=243 Width=56 
Height=17 Default=yes Text=!(loc.WixUINext)
  Publish Event=NewDialog 
Value=[VIV_SelectArchDlg_Next]![CDATA[CostingComplete = 1 AND VIV_PLCTYPE 
 ]]/Publish
  Publish Event=SpawnWaitDialog 
Value=WaitForCostingDlg![CDATA[CostingComplete = 1]]/Publish
/Control
Control Id=Cancel Type=PushButton X=304 Y=243 Width=56 
Height=17 Cancel=yes Text=!(loc.WixUICancel)
  Publish Event=SpawnDialog Value=CancelDlg![CDATA[1]]/Publish
/Control
Control Id=BottomLine Type=Line X=0 Y=234 Width=370 
Height=0 /
  /Dialog
/UI


Pierre-Alain GALTIER
Responsable Pôle Informatique  Technologie
IT Department Manager
pierre-alain.galt...@vivelys.com | www.vivelys.com
Tel. +33 (0)4 67 85 68 43 | Fax +33 (0)4 67 85 68 41


-Original Message-
From: Pierre-Alain GALTIER [mailto:pierre-alain.galt...@vivelys.com] 
Sent: Wednesday, November 6, 2013 4:05 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Inserting a dialog when user click on theAdvanced 
button [P]

Thank you

When I hit the Advanced button in the Welcome Eula Dialogbox, the next dialog 
box is InstallDir and the logging said :

Action 15:57:31: AdvancedWelcomeEulaDlg. 
Action start 15:57:31: AdvancedWelcomeEulaDlg.
Info 2898.For WixUI_Font_Title textstyle, the system created a 'Tahoma' font, 
in 0 character set, of 14 pixels height.
Action 15:57:32: AdvancedWelcomeEulaDlg. Dialog created
MSI (c) (44:14) [15:57:32:054]: Note: 1: 2205 2:  3: _RemoveFilePath 
MSI (c) (44:14) [15:57:32:058]: PROPERTY CHANGE: Modifying CostingComplete 
property. Its current value is '0'. Its new value: '1'.
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: BindImage 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: ProgId 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: PublishComponent 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: SelfReg 
MSI (c) (44:14) [15:57:32:058]: Note: 1: 2205 2:  3: Extension 
MSI (c) (44:14)

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Ignore my last message.  That didn't work after all, as none of the dialogs
appear in the ui sequence table. So...

I did what Steve suggested and copied the contents WixUI_Minimal into my
Product.wxs (and placed it inside the Product tags).  And then renamed
the Id on the UI element to WixUI_Minimal_Modified.  I have not even
bothered to create my own dialog.wxs and/or insert it into the copied
sequence.

I get the same build errors.  dup symbols if the wixuiextension.dll is
included or missing dialogs if it is not.

Any ideas?  I know this shouldn't be hard from reading the docs and/or
Nick's book, but I must be missing something obvious.  I don't have any
issues if I build a custom ui sequence.



On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 You don't need to ADD the WXS file to your project, you only need to
 copy the UI element from that file...
 Nor do you need to physically copy it to your project either...

 If you follow the steps I provided below you will be fine...

 1. in your PRODUCT.WXS file add the UI element:
 UI Id=WixUI_MYInstallDir
   TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
   TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
   TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
 Bold=yes /

   Property Id=DefaultUIFont Value=WixUI_Font_Normal /
   Property Id=WixUI_Mode Value=InstallDir /

   DialogRef Id=BrowseDlg /
   DialogRef Id=DiskCostDlg /
   DialogRef Id=ErrorDlg /
   DialogRef Id=FatalError /
   DialogRef Id=FilesInUse /
   DialogRef Id=MsiRMFilesInUse /
   DialogRef Id=PrepareDlg /
   DialogRef Id=ProgressDlg /
   DialogRef Id=ResumeDlg /
   DialogRef Id=UserExit /

   Publish Dialog=BrowseDlg Control=OK Event=DoAction
 Value=WixUIValidatePath Order=31/Publish
   Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
 Value=InvalidDirDlg
 Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish

   Publish Dialog=ExitDialog Control=Finish Event=EndDialog
 Value=Return Order=9991/Publish

   Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=LicenseAgreementDlgNOT Installed/Publish
   Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=VerifyReadyDlgInstalled AND PATCH/Publish

   Publish Dialog=LicenseAgreementDlg Control=Back
 Event=NewDialog Value=WelcomeDlg1/Publish
   Publish Dialog=LicenseAgreementDlg Control=Next
 Event=NewDialog Value=VerifyReadyDlgLicenseAccepted = 1/Publish

   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=LicenseAgreementDlg Order=1NOT Installed/Publish
   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=WelcomeDlg Order=2Installed AND PATCH/Publish

   Publish Dialog=MaintenanceWelcomeDlg Control=Next
 Event=NewDialog Value=MaintenanceTypeDlg1/Publish

   Publish Dialog=MaintenanceTypeDlg Control=RepairButton
 Event=NewDialog Value=VerifyReadyDlg1/Publish
   Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
 Event=NewDialog Value=VerifyReadyDlg1/Publish
   Publish Dialog=MaintenanceTypeDlg Control=Back
 Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish

 /UI

 UIRef Id=WixUI_Common /

 2. Substitute your new dialog for LicenseAgreementDlg so you have a Next
 and Back action for it:
   Publish Dialog= MyNewDlg  Control=Back Event=NewDialog
 Value=WelcomeDlg1/Publish
   Publish Dialog= MyNewDlg  Control=Next Event=NewDialog
 Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to the
 list of dialogs:
 DialogRef Id=MyNewDlg /
 4. make sure you have a Back action for your dialog in the VerifyReadyDlg:
 Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog Value=
 MyNewDlg  Order=1NOT Installed/Publish

 5. Add your new MyNewDlg.wxs to your project.

 Steve

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 7:36 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 I thought that might be the issue as well. I can't find another reference.
 So, I made a new solution that only contains a brand new WiX installer
 project.  The same build errors occur.

 1. New 2012 solution, single WiX v3.7 (.msi) project 2. Added manufacturer
 and uppper-cased UpgradeCode in the skeleton Product.wxs 3. copied
 WixUI_Minimal.wxs to the project folder and renamed it to
 WiXUI_Minimal_Modified.wxs.  Added WiXUI_Minimal_Modified.wxs to the
 project.
 4. Edited WiXUI_Minimal_Modified.wxs so that its UI element Id now reads
 UI Id=WixUI_Minimal_Modified 5. Added UIRef
 Id=WixUI_Minimal_Modified/ to Product.wxs 6. Clean/Rebuild, results in
 these errors...

 ...
 ...\WiXUITester\WixUI_Minimal_Modified.wxs(35,0): error LGHT0094:
 Unresolved reference

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Classification: Public
Did you remove the WixUI_Minimal.wxs from your project?
I have WixUIExtension referenced in my setup project...

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: November-06-13 11:37 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Ignore my last message.  That didn't work after all, as none of the dialogs 
appear in the ui sequence table. So...

I did what Steve suggested and copied the contents WixUI_Minimal into my 
Product.wxs (and placed it inside the Product tags).  And then renamed the Id 
on the UI element to WixUI_Minimal_Modified.  I have not even bothered to 
create my own dialog.wxs and/or insert it into the copied sequence.

I get the same build errors.  dup symbols if the wixuiextension.dll is included 
or missing dialogs if it is not.

Any ideas?  I know this shouldn't be hard from reading the docs and/or Nick's 
book, but I must be missing something obvious.  I don't have any issues if I 
build a custom ui sequence.

On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 You don't need to ADD the WXS file to your project, you only need to 
 copy the UI element from that file...
 Nor do you need to physically copy it to your project either...

 If you follow the steps I provided below you will be fine...

 1. in your PRODUCT.WXS file add the UI element:
 UI Id=WixUI_MYInstallDir
   TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
   TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
   TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
 Bold=yes /

   Property Id=DefaultUIFont Value=WixUI_Font_Normal /
   Property Id=WixUI_Mode Value=InstallDir /

   DialogRef Id=BrowseDlg /
   DialogRef Id=DiskCostDlg /
   DialogRef Id=ErrorDlg /
   DialogRef Id=FatalError /
   DialogRef Id=FilesInUse /
   DialogRef Id=MsiRMFilesInUse /
   DialogRef Id=PrepareDlg /
   DialogRef Id=ProgressDlg /
   DialogRef Id=ResumeDlg /
   DialogRef Id=UserExit /

   Publish Dialog=BrowseDlg Control=OK Event=DoAction
 Value=WixUIValidatePath Order=31/Publish
   Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
 Value=InvalidDirDlg
 Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish

   Publish Dialog=ExitDialog Control=Finish Event=EndDialog
 Value=Return Order=9991/Publish

   Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=LicenseAgreementDlgNOT Installed/Publish
   Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=VerifyReadyDlgInstalled AND PATCH/Publish

   Publish Dialog=LicenseAgreementDlg Control=Back
 Event=NewDialog Value=WelcomeDlg1/Publish
   Publish Dialog=LicenseAgreementDlg Control=Next
 Event=NewDialog Value=VerifyReadyDlgLicenseAccepted = 
 1/Publish

   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=LicenseAgreementDlg Order=1NOT Installed/Publish
   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
   Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=WelcomeDlg Order=2Installed AND PATCH/Publish

   Publish Dialog=MaintenanceWelcomeDlg Control=Next
 Event=NewDialog Value=MaintenanceTypeDlg1/Publish

   Publish Dialog=MaintenanceTypeDlg Control=RepairButton
 Event=NewDialog Value=VerifyReadyDlg1/Publish
   Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
 Event=NewDialog Value=VerifyReadyDlg1/Publish
   Publish Dialog=MaintenanceTypeDlg Control=Back
 Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish

 /UI

 UIRef Id=WixUI_Common /

 2. Substitute your new dialog for LicenseAgreementDlg so you have a 
 Next and Back action for it:
   Publish Dialog= MyNewDlg  Control=Back Event=NewDialog
 Value=WelcomeDlg1/Publish
   Publish Dialog= MyNewDlg  Control=Next Event=NewDialog
 Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to 
 the list of dialogs:
 DialogRef Id=MyNewDlg /
 4. make sure you have a Back action for your dialog in the VerifyReadyDlg:
 Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog Value=
 MyNewDlg  Order=1NOT Installed/Publish

 5. Add your new MyNewDlg.wxs to your project.

 Steve

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 7:36 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 I thought that might be the issue as well. I can't find another reference.
 So, I made a new solution that only contains a brand new WiX installer 
 project.  The same build errors occur.

 1. New 2012 solution, single WiX v3.7 (.msi) project 2. Added 
 manufacturer and uppper-cased UpgradeCode in the skeleton Product.wxs 
 3. copied WixUI_Minimal.wxs to the project folder and renamed it to

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

If you look at the duplicate id error messages, IMO, it is a conflict with
WixUIExtension as the file path for the conflict is from the WiX build
server, not my machine.


On Wed, Nov 6, 2013 at 1:00 PM, Tony yellowjacketl...@gmail.com wrote:

 It was never in my project.


 On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie 
 steven.ogil...@titus.comwrote:

 Classification: Public
 Did you remove the WixUI_Minimal.wxs from your project?
 I have WixUIExtension referenced in my setup project...

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 11:37 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence
 clarification... [P]

 Ignore my last message.  That didn't work after all, as none of the
 dialogs appear in the ui sequence table. So...

 I did what Steve suggested and copied the contents WixUI_Minimal into my
 Product.wxs (and placed it inside the Product tags).  And then renamed
 the Id on the UI element to WixUI_Minimal_Modified.  I have not even
 bothered to create my own dialog.wxs and/or insert it into the copied
 sequence.

 I get the same build errors.  dup symbols if the wixuiextension.dll is
 included or missing dialogs if it is not.

 Any ideas?  I know this shouldn't be hard from reading the docs and/or
 Nick's book, but I must be missing something obvious.  I don't have any
 issues if I build a custom ui sequence.



 On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie steven.ogil...@titus.com
 wrote:

  Classification: Public
  You don't need to ADD the WXS file to your project, you only need to
  copy the UI element from that file...
  Nor do you need to physically copy it to your project either...
 
  If you follow the steps I provided below you will be fine...
 
  1. in your PRODUCT.WXS file add the UI element:
  UI Id=WixUI_MYInstallDir
TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
  Bold=yes /
 
Property Id=DefaultUIFont Value=WixUI_Font_Normal /
Property Id=WixUI_Mode Value=InstallDir /
 
DialogRef Id=BrowseDlg /
DialogRef Id=DiskCostDlg /
DialogRef Id=ErrorDlg /
DialogRef Id=FatalError /
DialogRef Id=FilesInUse /
DialogRef Id=MsiRMFilesInUse /
DialogRef Id=PrepareDlg /
DialogRef Id=ProgressDlg /
DialogRef Id=ResumeDlg /
DialogRef Id=UserExit /
 
Publish Dialog=BrowseDlg Control=OK Event=DoAction
  Value=WixUIValidatePath Order=31/Publish
Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
  Value=InvalidDirDlg
  Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish
 
Publish Dialog=ExitDialog Control=Finish Event=EndDialog
  Value=Return Order=9991/Publish
 
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
  Value=LicenseAgreementDlgNOT Installed/Publish
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
  Value=VerifyReadyDlgInstalled AND PATCH/Publish
 
Publish Dialog=LicenseAgreementDlg Control=Back
  Event=NewDialog Value=WelcomeDlg1/Publish
Publish Dialog=LicenseAgreementDlg Control=Next
  Event=NewDialog Value=VerifyReadyDlgLicenseAccepted =
  1/Publish
 
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=LicenseAgreementDlg Order=1NOT Installed/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=WelcomeDlg Order=2Installed AND PATCH/Publish
 
Publish Dialog=MaintenanceWelcomeDlg Control=Next
  Event=NewDialog Value=MaintenanceTypeDlg1/Publish
 
Publish Dialog=MaintenanceTypeDlg Control=RepairButton
  Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
  Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=Back
  Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish
 
  /UI
 
  UIRef Id=WixUI_Common /
 
  2. Substitute your new dialog for LicenseAgreementDlg so you have a
  Next and Back action for it:
Publish Dialog= MyNewDlg  Control=Back Event=NewDialog
  Value=WelcomeDlg1/Publish
Publish Dialog= MyNewDlg  Control=Next Event=NewDialog
  Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to
  the list of dialogs:
  DialogRef Id=MyNewDlg /
  4. make sure you have a Back action for your dialog in the
 VerifyReadyDlg:
  Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=
  MyNewDlg  Order=1NOT Installed/Publish
 
  5. Add your new MyNewDlg.wxs to your project.
 
  Steve
 
  -Original Message-
  From: Tony [mailto:yellowjacketl...@gmail.com]
  Sent: November-06-13 7:36 AM
  To: General discussion about the WiX toolset.
  Subject: Re:

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

It was never in my project.


On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 Did you remove the WixUI_Minimal.wxs from your project?
 I have WixUIExtension referenced in my setup project...

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 11:37 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 Ignore my last message.  That didn't work after all, as none of the
 dialogs appear in the ui sequence table. So...

 I did what Steve suggested and copied the contents WixUI_Minimal into my
 Product.wxs (and placed it inside the Product tags).  And then renamed
 the Id on the UI element to WixUI_Minimal_Modified.  I have not even
 bothered to create my own dialog.wxs and/or insert it into the copied
 sequence.

 I get the same build errors.  dup symbols if the wixuiextension.dll is
 included or missing dialogs if it is not.

 Any ideas?  I know this shouldn't be hard from reading the docs and/or
 Nick's book, but I must be missing something obvious.  I don't have any
 issues if I build a custom ui sequence.



 On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie steven.ogil...@titus.com
 wrote:

  Classification: Public
  You don't need to ADD the WXS file to your project, you only need to
  copy the UI element from that file...
  Nor do you need to physically copy it to your project either...
 
  If you follow the steps I provided below you will be fine...
 
  1. in your PRODUCT.WXS file add the UI element:
  UI Id=WixUI_MYInstallDir
TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
  Bold=yes /
 
Property Id=DefaultUIFont Value=WixUI_Font_Normal /
Property Id=WixUI_Mode Value=InstallDir /
 
DialogRef Id=BrowseDlg /
DialogRef Id=DiskCostDlg /
DialogRef Id=ErrorDlg /
DialogRef Id=FatalError /
DialogRef Id=FilesInUse /
DialogRef Id=MsiRMFilesInUse /
DialogRef Id=PrepareDlg /
DialogRef Id=ProgressDlg /
DialogRef Id=ResumeDlg /
DialogRef Id=UserExit /
 
Publish Dialog=BrowseDlg Control=OK Event=DoAction
  Value=WixUIValidatePath Order=31/Publish
Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
  Value=InvalidDirDlg
  Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish
 
Publish Dialog=ExitDialog Control=Finish Event=EndDialog
  Value=Return Order=9991/Publish
 
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
  Value=LicenseAgreementDlgNOT Installed/Publish
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
  Value=VerifyReadyDlgInstalled AND PATCH/Publish
 
Publish Dialog=LicenseAgreementDlg Control=Back
  Event=NewDialog Value=WelcomeDlg1/Publish
Publish Dialog=LicenseAgreementDlg Control=Next
  Event=NewDialog Value=VerifyReadyDlgLicenseAccepted =
  1/Publish
 
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=LicenseAgreementDlg Order=1NOT Installed/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=WelcomeDlg Order=2Installed AND PATCH/Publish
 
Publish Dialog=MaintenanceWelcomeDlg Control=Next
  Event=NewDialog Value=MaintenanceTypeDlg1/Publish
 
Publish Dialog=MaintenanceTypeDlg Control=RepairButton
  Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
  Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=Back
  Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish
 
  /UI
 
  UIRef Id=WixUI_Common /
 
  2. Substitute your new dialog for LicenseAgreementDlg so you have a
  Next and Back action for it:
Publish Dialog= MyNewDlg  Control=Back Event=NewDialog
  Value=WelcomeDlg1/Publish
Publish Dialog= MyNewDlg  Control=Next Event=NewDialog
  Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to
  the list of dialogs:
  DialogRef Id=MyNewDlg /
  4. make sure you have a Back action for your dialog in the
 VerifyReadyDlg:
  Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog Value=
  MyNewDlg  Order=1NOT Installed/Publish
 
  5. Add your new MyNewDlg.wxs to your project.
 
  Steve
 
  -Original Message-
  From: Tony [mailto:yellowjacketl...@gmail.com]
  Sent: November-06-13 7:36 AM
  To: General discussion about the WiX toolset.
  Subject: Re: [WiX-users] Modifying a stock WixUI sequence
 clarification...
  [P]
 
  I thought that might be the issue as well. I can't find another
 reference.
  So, I made a new solution that only contains a brand new WiX installer
  project.  The same build

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Classification: Public
This is from your post below:

3. copied WixUI_Minimal.wxs to the project folder and 
  renamed it to WiXUI_Minimal_Modified.wxs.  Added 
  WiXUI_Minimal_Modified.wxs to the project.

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: November-06-13 1:00 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

It was never in my project.


On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 Did you remove the WixUI_Minimal.wxs from your project?
 I have WixUIExtension referenced in my setup project...

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 11:37 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 Ignore my last message.  That didn't work after all, as none of the 
 dialogs appear in the ui sequence table. So...

 I did what Steve suggested and copied the contents WixUI_Minimal into 
 my Product.wxs (and placed it inside the Product tags).  And then 
 renamed the Id on the UI element to WixUI_Minimal_Modified.  I have 
 not even bothered to create my own dialog.wxs and/or insert it into 
 the copied sequence.

 I get the same build errors.  dup symbols if the wixuiextension.dll is 
 included or missing dialogs if it is not.

 Any ideas?  I know this shouldn't be hard from reading the docs and/or 
 Nick's book, but I must be missing something obvious.  I don't have 
 any issues if I build a custom ui sequence.



 On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie 
 steven.ogil...@titus.com
 wrote:

  Classification: Public
  You don't need to ADD the WXS file to your project, you only need to 
  copy the UI element from that file...
  Nor do you need to physically copy it to your project either...
 
  If you follow the steps I provided below you will be fine...
 
  1. in your PRODUCT.WXS file add the UI element:
  UI Id=WixUI_MYInstallDir
TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
  Bold=yes /
 
Property Id=DefaultUIFont Value=WixUI_Font_Normal /
Property Id=WixUI_Mode Value=InstallDir /
 
DialogRef Id=BrowseDlg /
DialogRef Id=DiskCostDlg /
DialogRef Id=ErrorDlg /
DialogRef Id=FatalError /
DialogRef Id=FilesInUse /
DialogRef Id=MsiRMFilesInUse /
DialogRef Id=PrepareDlg /
DialogRef Id=ProgressDlg /
DialogRef Id=ResumeDlg /
DialogRef Id=UserExit /
 
Publish Dialog=BrowseDlg Control=OK Event=DoAction
  Value=WixUIValidatePath Order=31/Publish
Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
  Value=InvalidDirDlg
  Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish
 
Publish Dialog=ExitDialog Control=Finish Event=EndDialog
  Value=Return Order=9991/Publish
 
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
  Value=LicenseAgreementDlgNOT Installed/Publish
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
  Value=VerifyReadyDlgInstalled AND PATCH/Publish
 
Publish Dialog=LicenseAgreementDlg Control=Back
  Event=NewDialog Value=WelcomeDlg1/Publish
Publish Dialog=LicenseAgreementDlg Control=Next
  Event=NewDialog Value=VerifyReadyDlgLicenseAccepted = 
  1/Publish
 
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=LicenseAgreementDlg Order=1NOT Installed/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=MaintenanceTypeDlg Order=2Installed AND NOT PATCH/Publish
Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
  Value=WelcomeDlg Order=2Installed AND PATCH/Publish
 
Publish Dialog=MaintenanceWelcomeDlg Control=Next
  Event=NewDialog Value=MaintenanceTypeDlg1/Publish
 
Publish Dialog=MaintenanceTypeDlg Control=RepairButton
  Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=RemoveButton
  Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=MaintenanceTypeDlg Control=Back
  Event=NewDialog Value=MaintenanceWelcomeDlg1/Publish
 
  /UI
 
  UIRef Id=WixUI_Common /
 
  2. Substitute your new dialog for LicenseAgreementDlg so you have a 
  Next and Back action for it:
Publish Dialog= MyNewDlg  Control=Back Event=NewDialog
  Value=WelcomeDlg1/Publish
Publish Dialog= MyNewDlg  Control=Next Event=NewDialog
  Value=VerifyReadyDlgLicenseAccepted = 1/Publish 3. add it to 
  the list of dialogs:
  DialogRef Id=MyNewDlg /
  4. make sure you have a Back action for your dialog in the
 VerifyReadyDlg:
  Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog Value=
  MyNewDlg  Order=1NOT Installed/Publish
 
  5. Add your new MyNewDlg.wxs to

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Classification: Public
If you read the docs from WIX it is easy:

Inserting a custom dialog into a built-in dialog set You can add custom dialogs 
to the UI sequence in a built-in WixUI dialog set. To do so, you must define a 
UI/ element for your new dialog. Then, you must copy the contents of the 
Fragment/ that includes the definition of the dialog set that you want to 
customize from the WiX source code to your project. Finally, you must modify 
the Publish/ elements to define the exact dialog sequence that you want in 
your installation experience.

For example, to insert a dialog named SpecialDlg between the WelcomeDlg and the 
LicenseAgreementDlg in the WixUI_InstallDir dialog set, you would do the 
following:

Define the appearance of the SpecialDlg in a UI/ element in your project.

Copy the full contents of the Fragment/ defined in WixUI_InstallDir.wxs in 
the WiX source code to your project.

Add Publish/ elements that define the Back and Next events for the 
SpecialDlg. For example:
Publish Dialog=SpecialDlg Control=Back Event=NewDialog 
Value=WelcomeDlg1/Publish Publish Dialog=SpecialDlg Control=Next 
Event=NewDialog Value=LicenseAgreementDlg1/Publish

Change the Publish/ element that is used to add a Next event to the 
WelcomeDlg to go to the SpecialDlg instead of the LicenseAgreementDlg. For 
example:
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog 
Value=SpecialDlg1/Publish

Change the Publish/ element that is used to add a Back event to the 
LicenseAgreementDlg to go to the SpecialDlg instead of the WelcomeDlg. For 
example:
Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog 
Value=SpecialDlg1/Publish

Steve
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: November-06-13 1:09 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

Classification: Public
This is from your post below:

3. copied WixUI_Minimal.wxs to the project folder and 
  renamed it to WiXUI_Minimal_Modified.wxs.  Added 
  WiXUI_Minimal_Modified.wxs to the project.

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: November-06-13 1:00 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

It was never in my project.


On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 Did you remove the WixUI_Minimal.wxs from your project?
 I have WixUIExtension referenced in my setup project...

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 11:37 AM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 Ignore my last message.  That didn't work after all, as none of the 
 dialogs appear in the ui sequence table. So...

 I did what Steve suggested and copied the contents WixUI_Minimal into 
 my Product.wxs (and placed it inside the Product tags).  And then 
 renamed the Id on the UI element to WixUI_Minimal_Modified.  I have 
 not even bothered to create my own dialog.wxs and/or insert it into 
 the copied sequence.

 I get the same build errors.  dup symbols if the wixuiextension.dll is 
 included or missing dialogs if it is not.

 Any ideas?  I know this shouldn't be hard from reading the docs and/or 
 Nick's book, but I must be missing something obvious.  I don't have 
 any issues if I build a custom ui sequence.



 On Wed, Nov 6, 2013 at 8:45 AM, Steven Ogilvie 
 steven.ogil...@titus.com
 wrote:

  Classification: Public
  You don't need to ADD the WXS file to your project, you only need to 
  copy the UI element from that file...
  Nor do you need to physically copy it to your project either...
 
  If you follow the steps I provided below you will be fine...
 
  1. in your PRODUCT.WXS file add the UI element:
  UI Id=WixUI_MYInstallDir
TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 /
TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9
  Bold=yes /
 
Property Id=DefaultUIFont Value=WixUI_Font_Normal /
Property Id=WixUI_Mode Value=InstallDir /
 
DialogRef Id=BrowseDlg /
DialogRef Id=DiskCostDlg /
DialogRef Id=ErrorDlg /
DialogRef Id=FatalError /
DialogRef Id=FilesInUse /
DialogRef Id=MsiRMFilesInUse /
DialogRef Id=PrepareDlg /
DialogRef Id=ProgressDlg /
DialogRef Id=ResumeDlg /
DialogRef Id=UserExit /
 
Publish Dialog=BrowseDlg Control=OK Event=DoAction
  Value=WixUIValidatePath Order=31/Publish
Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog
  Value=InvalidDirDlg
  Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish
 
Publish Dialog=ExitDialog Control=Finish Event=EndDialog
  Value=Return Order=9991/Publish

Re: [WiX-users] Managed Custom Action which call win 32 dll, possible?

2013-11-06 Thread tom


Thanks.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Custom-Action-which-call-win-32-dll-possible-tp7590295p7590335.html
Sent from the wix-users mailing list archive at Nabble.com.

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

This works, but I have no idea why as most of the lines that had conflicts
prior to the changes are still present

1. Setup virgin project/solution
2. copied contents of wixui_minimal.wxs into my product.wxs
3. set manufacture and uppercased upgrade code
4. added a single file to install (product.wxs)
5. removed all references to WelcomeEulaDlg, by changing the ui sequence to
read this...

  InstallUISequence
Show Dialog=WelcomeDlg Before=ProgressDlg1/Show
  /InstallUISequence

6.  Changed the condition on the WelcomeDlg Next button like this...

Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
Value=VerifyReadyDlg1/Publish

7. clean/rebuild

Run the .msi and I see the welcome dialog!  Woot!

That said, the other 'Publish' entries remain unchanged as does the
Property WixUI_Mode.  ***All of which were generating duplicate error
before.***

I now have two virgin built projects one as described earlier in the thread
and one with the few changes I made above.  Only the one with 2-3 changes
described above builds.  I don't get it.  Why don't I see this error?  That
line hasn't changed?

C:\Users\me\Documents\Visual Studio
2012\Projects\WiXUITester2\WiXUITester2\uistuff.wxs(10,0): error LGHT0091:
Duplicate symbol 'Property:WixUI_Mode' found. This typically means that an
Id is duplicated. Check to make sure all your identifiers of a given type
(File, Component, Feature) are unique.
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(33,0):
error LGHT0092: Location of symbol related to previous error.

or this error...

C:\Users\me\Documents\Visual Studio
2012\Projects\WiXUITester2\WiXUITester2\uistuff.wxs(31,0): error LGHT0091:
Duplicate symbol
'ControlEvent:MaintenanceTypeDlg/Back/NewDialog/MaintenanceWelcomeDlg/1'
found. This typically means that an Id is duplicated. Check to make sure
all your identifiers of a given type (File, Component, Feature) are unique.
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(54,0):
error LGHT0092: Location of symbol related to previous error.



On Wed, Nov 6, 2013 at 1:16 PM, Steven Ogilvie steven.ogil...@titus.comwrote:

 Classification: Public
 If you read the docs from WIX it is easy:

 Inserting a custom dialog into a built-in dialog set You can add custom
 dialogs to the UI sequence in a built-in WixUI dialog set. To do so, you
 must define a UI/ element for your new dialog. Then, you must copy the
 contents of the Fragment/ that includes the definition of the dialog set
 that you want to customize from the WiX source code to your project.
 Finally, you must modify the Publish/ elements to define the exact dialog
 sequence that you want in your installation experience.

 For example, to insert a dialog named SpecialDlg between the WelcomeDlg
 and the LicenseAgreementDlg in the WixUI_InstallDir dialog set, you would
 do the following:

 Define the appearance of the SpecialDlg in a UI/ element in your project.

 Copy the full contents of the Fragment/ defined in WixUI_InstallDir.wxs
 in the WiX source code to your project.

 Add Publish/ elements that define the Back and Next events for the
 SpecialDlg. For example:
 Publish Dialog=SpecialDlg Control=Back Event=NewDialog
 Value=WelcomeDlg1/Publish Publish Dialog=SpecialDlg Control=Next
 Event=NewDialog Value=LicenseAgreementDlg1/Publish

 Change the Publish/ element that is used to add a Next event to the
 WelcomeDlg to go to the SpecialDlg instead of the LicenseAgreementDlg. For
 example:
 Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=SpecialDlg1/Publish

 Change the Publish/ element that is used to add a Back event to the
 LicenseAgreementDlg to go to the SpecialDlg instead of the WelcomeDlg. For
 example:
 Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog
 Value=SpecialDlg1/Publish

 Steve
 -Original Message-
 From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
 Sent: November-06-13 1:09 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 Classification: Public
 This is from your post below:

 3. copied WixUI_Minimal.wxs to the project folder and
   renamed it to WiXUI_Minimal_Modified.wxs.  Added
   WiXUI_Minimal_Modified.wxs to the project.

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 1:00 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence clarification...
 [P]

 It was never in my project.


 On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie steven.ogil...@titus.com
 wrote:

  Classification: Public
  Did you remove the WixUI_Minimal.wxs from your project?
  I have WixUIExtension referenced in my setup project...
 
  -Original Message-
  From: Tony [mailto:yellowjacketl...@gmail.com]
  Sent: November-06-13 11:37 AM
  To: General discussion about the WiX toolset.
  Subject: Re: [WiX-users] Modifying a stock

Re: [WiX-users] Modifying a stock WixUI sequence clarification... [P]

I should have said this in my last messsage...

Thanks for all of the help and patience.


On Wed, Nov 6, 2013 at 3:03 PM, Tony yellowjacketl...@gmail.com wrote:

 This works, but I have no idea why as most of the lines that had conflicts
 prior to the changes are still present

 1. Setup virgin project/solution
 2. copied contents of wixui_minimal.wxs into my product.wxs
 3. set manufacture and uppercased upgrade code
 4. added a single file to install (product.wxs)
 5. removed all references to WelcomeEulaDlg, by changing the ui sequence
 to read this...

   InstallUISequence
 Show Dialog=WelcomeDlg Before=ProgressDlg1/Show
   /InstallUISequence

 6.  Changed the condition on the WelcomeDlg Next button like this...

 Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=VerifyReadyDlg1/Publish

 7. clean/rebuild

 Run the .msi and I see the welcome dialog!  Woot!

 That said, the other 'Publish' entries remain unchanged as does the
 Property WixUI_Mode.  ***All of which were generating duplicate error
 before.***

 I now have two virgin built projects one as described earlier in the
 thread and one with the few changes I made above.  Only the one with 2-3
 changes described above builds.  I don't get it.  Why don't I see this
 error?  That line hasn't changed?

 C:\Users\me\Documents\Visual Studio
 2012\Projects\WiXUITester2\WiXUITester2\uistuff.wxs(10,0): error LGHT0091:
 Duplicate symbol 'Property:WixUI_Mode' found. This typically means that an
 Id is duplicated. Check to make sure all your identifiers of a given type
 (File, Component, Feature) are unique.

 E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(33,0):
 error LGHT0092: Location of symbol related to previous error.

 or this error...

 C:\Users\me\Documents\Visual Studio
 2012\Projects\WiXUITester2\WiXUITester2\uistuff.wxs(31,0): error LGHT0091:
 Duplicate symbol
 'ControlEvent:MaintenanceTypeDlg/Back/NewDialog/MaintenanceWelcomeDlg/1'
 found. This typically means that an Id is duplicated. Check to make sure
 all your identifiers of a given type (File, Component, Feature) are unique.
 E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(54,0):
 error LGHT0092: Location of symbol related to previous error.



 On Wed, Nov 6, 2013 at 1:16 PM, Steven Ogilvie 
 steven.ogil...@titus.comwrote:

 Classification: Public
 If you read the docs from WIX it is easy:

 Inserting a custom dialog into a built-in dialog set You can add custom
 dialogs to the UI sequence in a built-in WixUI dialog set. To do so, you
 must define a UI/ element for your new dialog. Then, you must copy the
 contents of the Fragment/ that includes the definition of the dialog set
 that you want to customize from the WiX source code to your project.
 Finally, you must modify the Publish/ elements to define the exact dialog
 sequence that you want in your installation experience.

 For example, to insert a dialog named SpecialDlg between the WelcomeDlg
 and the LicenseAgreementDlg in the WixUI_InstallDir dialog set, you would
 do the following:

 Define the appearance of the SpecialDlg in a UI/ element in your
 project.

 Copy the full contents of the Fragment/ defined in WixUI_InstallDir.wxs
 in the WiX source code to your project.

 Add Publish/ elements that define the Back and Next events for the
 SpecialDlg. For example:
 Publish Dialog=SpecialDlg Control=Back Event=NewDialog
 Value=WelcomeDlg1/Publish Publish Dialog=SpecialDlg Control=Next
 Event=NewDialog Value=LicenseAgreementDlg1/Publish

 Change the Publish/ element that is used to add a Next event to the
 WelcomeDlg to go to the SpecialDlg instead of the LicenseAgreementDlg. For
 example:
 Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
 Value=SpecialDlg1/Publish

 Change the Publish/ element that is used to add a Back event to the
 LicenseAgreementDlg to go to the SpecialDlg instead of the WelcomeDlg. For
 example:
 Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog
 Value=SpecialDlg1/Publish

 Steve
 -Original Message-
 From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
 Sent: November-06-13 1:09 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence
 clarification... [P]

 Classification: Public
 This is from your post below:

 3. copied WixUI_Minimal.wxs to the project folder and
   renamed it to WiXUI_Minimal_Modified.wxs.  Added
   WiXUI_Minimal_Modified.wxs to the project.

 -Original Message-
 From: Tony [mailto:yellowjacketl...@gmail.com]
 Sent: November-06-13 1:00 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] Modifying a stock WixUI sequence
 clarification... [P]

 It was never in my project.


 On Wed, Nov 6, 2013 at 11:52 AM, Steven Ogilvie steven.ogil...@titus.com
 wrote:

  Classification: Public
  Did you remove the WixUI_Minimal.wxs from your project?
  I have WixUIExtension referenced in my setup project...

Re: [WiX-users] WixPdbPath property

2013-11-06 Thread cknoll

Just to close the loop on this, WiX 3.8 will be removing WixPdbPath:
http://wixtoolset.org/issues/4152/


robmen wrote
 Many people move it to a drop location that is laid out identically as the
 build machine with a different root. We can work with that. pyro already
 has support for such gymnastics when using bindpaths.
 
 
 On Fri, Dec 28, 2012 at 8:42 PM, Alex Ivanoff lt;

 aivanoff@

 gt; wrote:
 
 Exactly my point: how often do you build an installer and not move it to
 some drop location?

 -Original Message-
 From: Rob Mensching [mailto:

 rob@

 ]
 Sent: Friday, December 28, 2012 10:52
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] WixPdbPath property

 If for some reason that is sensitive information for you, you can
 suppress
 the information. The property would not be as helpful if you copy into a
 completely different tree on the drop location.


 On Mon, Dec 24, 2012 at 10:06 PM, Alex Ivanoff lt;

 aivanoff@

 gt;
 wrote:

  This property contains a full local path, which may contain sensitive
  information. What value does the full path have after the file was
  copied from the build server to a drop location?
 
 
  On Dec 24, 2012, at 23:50 , Rob Mensching lt;

 rob@

 gt; wrote:
 
   Property to help tools find the .wixpdbs in (hopefully) near future.
   If
  it
   was off by default, 99.9% of people wouldn't have it on when they
   needed.
   
 smile/
  
  
   On Mon, Dec 24, 2012 at 9:19 PM, Alex Ivanoff lt;

 aivanoff@

 gt;
  wrote:
  
   WiX 3.6.3303.
  
   I just noticed WixPdbPath property in Property table of all of our
   installers. I know it can be suppressed using SuppressBuildInfo,
   but
  why is
   it on by default?
  
  
  
  --
  
   LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
   Remotely access PCs and mobile devices and provide instant support
   Improve your efficiency, and focus on delivering more value-add
   services Discover what IT Professionals Know. Rescue delivers
   http://p.sf.net/sfu/logmein_12329d2d
   ___
   WiX-users mailing list
   

 WiX-users@.sourceforge

   https://lists.sourceforge.net/lists/listinfo/wix-users
  
  
  
  
   --
   virtually,
  
 Rob Mensching
 http://RobMensching.com LLC
  
  --
  
   LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
   Remotely access PCs and mobile devices and provide instant support
   Improve your efficiency, and focus on delivering more value-add
   services Discover what IT Professionals Know. Rescue delivers
   http://p.sf.net/sfu/logmein_12329d2d
   ___
   WiX-users mailing list
   

 WiX-users@.sourceforge

   https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 
  --
   LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free
  Trial Remotely access PCs and mobile devices and provide instant
  support Improve your efficiency, and focus on delivering more
  value-add services Discover what IT Professionals Know. Rescue
  delivers http://p.sf.net/sfu/logmein_12329d2d
  ___
  WiX-users mailing list
  

 WiX-users@.sourceforge

  https://lists.sourceforge.net/lists/listinfo/wix-users
 



 --
 virtually,

Rob Mensching
http://RobMensching.com LLC

 --
 Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much
 more.
 Get web development skills now with LearnDevNow -
 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
 SALE $99.99 this month only -- learn more at:
 http://p.sf.net/sfu/learnmore_122812
 ___
 WiX-users mailing list
 

 WiX-users@.sourceforge

 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
 MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
 with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
 MVPs and experts. SALE $99.99 this month only -- learn more at:
 http://p.sf.net/sfu/learnmore_122912
 ___
 WiX-users mailing list
 

 WiX-users@.sourceforge

 https://lists.sourceforge.net/lists/listinfo/wix-users

 
 
 
 -- 
 virtually,
 
Rob Mensching
http://RobMensching.com LLC
 --
 Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
 MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
 with LearnDevNow - 3,200 step-by-step video

Re: [WiX-users] Difficulties with Burn (and introducing myself)

I don't think you want that check. You want Burn to register the package for
each bootstrapper that installs it. In other words, you want to install it
everytime, even if it's already installed. Burn should detect that the
package is already installed and just skip over it. That way, when one
bundle is uninstalled, the package ref count will be decreased by one, and
the package is only removed if ref count reaches zero (after all bundles
that reference it are uninstalled).

But if the package wasn't installed by Burn, you probably aren't getting the
benefit of the package ref counting (since that's a Burn feature).



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Difficulties-with-Burn-and-introducing-myself-tp7587950p7590340.html
Sent from the wix-users mailing list archive at Nabble.com.

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Control Property vs ComboBox Property...

The Property attribute should be the same on both elements. It ties them
together in that way.

According to the MSI documention for the ComboList property:

If the ComboList Control bit is set on a combo box, the edit field is
replaced by a static text field. This prevents a user from entering a new
value and requires the user to choose only one of the predefined values.
If this bit is not set, the combo box has an edit field.

I guess you could experiment with that one. :)



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Control-Property-vs-ComboBox-Property-tp7590269p7590341.html
Sent from the wix-users mailing list archive at Nabble.com.

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix Newbie

Are you just starting your journey with WiX? If you are, you might take a
step back from WPF user interfaces for a few days and dig into writing an
MSI file. Once you've got that, I'd read up on how to use Burn by itself,
using the UI that comes with the toolset. Here, I'm talking about just
writing a bundle file and chaining packages in it, etc. Then, once you've
got that down, move on to writing the WPF stuff, which may not even be
necessary for you once you've seen what a plain old MSI can do.



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

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Multiple Instances and Burn

2013-11-06 Thread Lynn Crumbling

I've read a lot of threads, all of which seem to burn not yet having support 
for Instance Transforms. This is a bit of a bummer, as I've already authored 
the MSI with the transforms, and just need a bootstrapper for [.net, sql ce, 
target iis website selection (install only), instance selection (removal only)].

As a starting point for this thread, am I correct about the lack of support in 
burn? If so, I'm going to go the route of using burn purely for the purposes of 
a UI for manually launching a command line composed of msiexec with a bunch of 
parameters, unless someone can suggest another approach.

- Lynn


--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bundle installing VS - returns 0x80048bc7

2013-11-06 Thread Carter Young

If the only block to be reported is ?Reboot Pending,? the returned
value is the Incomplete-Reboot Required value (0x80048bc7).

That's Pending Restart due to a Block. Incomplete means, the
installer did not finish. Upon Restart the block should be removed
and the install will need to be restarted. You need to investigate to
see which component in your requirements is creating the block.

Quoting rowbot james.row...@microfocus.com:

Hi,

Got a bundle that installs VS2012 or VS2013 Shells..

I've noticed that sometimes, we get a 0x80048bc7 (pending restart required)

It seems to be if VS updated some .NET framework components...

Our bundle doesn't catch it as 3010 etc... so what does 0x80048bc7 translate
to?

In the VS admin guide
(http://msdn.microsoft.com/en-us/library/vstudio/ee225238.aspx) it's not
translated into a 4-digit error code..

Thanks,

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-installing-VS-returns-0x80048bc7-tp7590319.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Inserting a dialog when user click on the Advanced button