Re: [WiX-users] Wix 3.5 - Unresolved reference to symbol 'Property:ApplicationFolderName'

2012-04-10 Thread Omar
Hi again,

For more information: the error only appears when I show the dialog 
before the WelcomeDlg.
If I show the dialog before the ProgressDlg for example, it builds 
correctly...

This doesn't work (see error messages + warnings in previous message):

InstallUISequence
?if $(var.Platform) = x64 ?
Show Dialog=SqlServerPrerequisitesDlg Before=WelcomeDlgNOT 
DTSDIR.X64/Show
?else?
Show Dialog=SqlServerPrerequisitesDlg Before=WelcomeDlgNOT DTSDIR/Show
?endif?
/InstallUISequence


While, this works without any error/warning:

InstallUISequence
?if $(var.Platform) = x64 ?
Show Dialog=SqlServerPrerequisitesDlg Before=ProgressDlgNOT 
DTSDIR.X64/Show
?else?
Show Dialog=SqlServerPrerequisitesDlg Before=ProgressDlgNOT DTSDIR/Show
?endif?
/InstallUISequence


There must be some bug which tries to load the WixUI_Advanced when 
referencing WelcomeDlg inside the InstallUiSequence?

I'll test with that to ensure that it's correctly working, but at least, 
it builds without problems.

Let me know if I'm doing something wrong...

Thank you,

Omar

Le 05/04/2012 14:25, Omar a écrit :
 Hi,

 I'm updating to Wix 3.5 (I think I used WiX 3.0 before, but I need
 support for VS 2010).
 But I now have problems with my current installer.


 I'm using a custom UI (sorry for long code...):
 -
 ?xml version=1.0 encoding=UTF-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
 xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
 Fragment
 UI Id=WixUI_Enesys
 TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 /
 TextStyle Id=WixUI_Font_Bold FaceName=Tahoma Size=8 Bold=yes /
 TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 Bold=yes /
 TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes /
 TextStyle Id=WixUI_Font_Error FaceName=Tahoma Size=8 Bold=yes
 Blue=0 Green=0 Red=255/

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

 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=EnesysExitDialog Control=Finish Event=EndDialog
 Value=Return Order=9991/Publish

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

 Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog
 Value=WelcomeDlg1/Publish
 Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog
 Value=CustomizeDlg Order=2LicenseAccepted = 1/Publish

 Publish Dialog=CustomizeDlg Control=Back Event=NewDialog
 Value=MaintenanceTypeDlg Order=1WixUI_InstallMode = Change/Publish
 Publish Dialog=CustomizeDlg Control=Back Event=NewDialog
 Value=LicenseAgreementDlg Order=2WixUI_InstallMode =
 InstallCustom/Publish
 Publish Dialog=CustomizeDlg Control=Next Event=NewDialog
 Value=ShortcutDlg Order=11/Publish

 Publish Dialog=ShortcutDlg Control=Back Event=NewDialog
 Value=CustomizeDlg Order=11/Publish
 Publish Dialog=ShortcutDlg Control=Next Event=NewDialog
 Value=VerifyReadyDlg1/Publish

 Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=ShortcutDlg Order=1WixUI_InstallMode = InstallCustom/Publish
 Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=CustomizeDlg Order=2WixUI_InstallMode = Change/Publish
 Publish Dialog=VerifyReadyDlg Control=Back Event=NewDialog
 Value=MaintenanceTypeDlg Order=3WixUI_InstallMode = Repair OR
 WixUI_InstallMode = Remove/Publish

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

 Publish Dialog=MaintenanceTypeDlg Control=ChangeButton
 Event=NewDialog Value=CustomizeDlg1/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/
 /Fragment
 /Wix
 -


 Like that it works correctly I don't have any error.

 But I also have a custom error Dialog that is displayed if some
 necessary things are not installed on the workstation.
 Here it is :

 -
 ?xml version=1.0 encoding=utf-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;

 ?include Definitions/VersionDef.wxi ?

 Fragment
 UI
 Dialog Id=SqlServerPrerequisitesDlg Width=270 Height=105
 Title=[ProductName] Setup
 Control Id=ErrorText Type=Text X=48 Y=15 Width=205
 Height=60 TabSkip=no Transparent=yes NoPrefix=yes
 TextSQL Server $(var.SqlVersion) Integration Services was not detected
 on this computer. Please install Integration Services before installing
 [ProductName]./Text
 /Control
 Control Id=ErrorIcon Type=Icon X=15 Y=15 Width=24 Height=24
 ToolTip=!(loc.ErrorDlgErrorIconTooltip) FixedSize=yes IconSize=32
 Text=!(loc.WaitForCostingDlgIcon

[WiX-users] Wix 3.5 - Unresolved reference to symbol 'Property:ApplicationFolderName'

2012-04-05 Thread Omar
 that only 
references WixUI_Common!!

Anyway, I tried to add the necessary things for WixUI_Advanced, so I 
don't have this error anymore.
It seems to work, but it throws some other errors:

...\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(125): error LGHT0170: The 
InstallUISequence table contains an action 'WelcomeDlg' that is declared in two 
different locations.  Please remove one of the actions or set the 
Overridable='yes' attribute on one of their elements.
...\src\ext\UIExtension\wixlib\WixUI_Minimal.wxs(63): error LGHT0171: The 
location of the action related to previous error.
...\src\ext\UIExtension\wixlib\ExitDialog.wxs(37): warning LGHT1050: The 
AdminUISequence table contains actions 'ExitDialog' and 'EnesysExitDialog' 
which both have the same sequence number -1.  Please change the sequence number 
for one of these actions to avoid an ICE warning.
...\EnesysExitDialog.wxs(29): warning LGHT1051: The location of the action 
related to previous warning.
...\src\ext\UIExtension\wixlib\ExitDialog.wxs(33): warning LGHT1050: The 
InstallUISequence table contains actions 'ExitDialog' and 'EnesysExitDialog' 
which both have the same sequence number -1.  Please change the sequence number 
for one of these actions to avoid an ICE warning.
...\src\EnesysISInstaller\EnesysExitDialog.wxs(25): warning LGHT1051: The 
location of the action related to previous warning.


But I don't reference any of those files with errors (Advanced, Minimal, 
ExitDialog)

Is there some bug or did I miss something?

Thank you

Omar


--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Editing a file on installmode = Change

2008-12-08 Thread Omar Sharif

Hi,

I have an installer which asks for a license key.
The license key is stored in an xml file, but it's not very obvious for
users, and it may be difficult to change it manually, so I would like to
allow users to change the license key directly through the installation (in
Change mode).

I created a custom page where I ask a license key, which is set in one of my
features. But, when I click on Change for changing installation property,
the feature is already installed, so the key would not be changed, as the
feature would not be re-installed. Is there a way to allow users to change
the license key, by relaunching the feature ? Or by creating a fake feature,
I don't know ?!

Thanks
-- 
View this message in context: 
http://n2.nabble.com/Editing-a-file-on-installmode-%3D-Change-tp1630948p1630948.html
Sent from the wix-users mailing list archive at Nabble.com.


--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Registry problems

2007-09-20 Thread Omar Ferrer
I'm currently using WiX 3, and I'm trying to register an OCX, but I'm having
problems with it.
First of all, I'm trying to register and .OCX that is already in the
computer, and not included on the package itself.
Is that possible?
Second of all, I'm trying to register an .OCX, in the HKCR, but it keeps
making it on the HKCU or the HKCM.  The account has administrator privileges
by the way.

This is what I'm using for the Register:

RegistryValue Id=registry0 Action='write' Root=HKCR
Key=CLSID\{1123-E14C-319B-9A9C-1A58AE70D7A2}\InprocServer32
Type=string
 Value=C:\Documents and
Settings\Chamakits\Desktop\myOcx.OCX 

 /RegistryValue

Any help would be greatly appreciated.

Thanks in advance,
Omar Ferrer
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users