I was just starting to investigate that control type... and where the text
breaks up the string (eg. -) the control conditions to re-evaluate
when the caret reaches the 2nd section, so it very nearly does the perfect
job. Thanks again.
--
View this message in context:
Of course... I could've been looking for weeks before I noticed that. Many
thanks.
--
View this message in context:
http://www.nabble.com/PrintEULA-CA-tf4856905.html#a13914516
Sent from the wix-users mailing list archive at Nabble.com.
Has anyone created a dialog to accept a serial key from the user before
allowing the 'Next' button to function? I think it's easy enough to call a
custom action to validate the serial key and to create the field(s) for
users to type their serial key into, but the niceties I'm finding tricky.
1
Hi guys, has anyone succesfully included the PrintEULA call in the latest
wixca.dll (2.0.5805.0)?
I have my custom action:
CustomAction Id=PrintEula BinaryKey=wixca DllEntry=PrintEula
Return=ignore Execute=immediate /
And my 'Print' button:
Control Id=Print Type=PushButton X=112 Y=243 Width=56
Have you tried looking at the SystemLanguageID property?
I was hoping to find a nice simple regkey to look for rather than having to
compose a new DLL function.
--
View this message in context:
http://www.nabble.com/Operating-System-language-detection-tf4671232.html#a13359979
Sent from the
Does anyone know hoe to determin the language of the operating system?
I'm aware that the MSI Engine stores the locale, which you can configure in
the control panel. However, there must be something deeper as some of
Microsoft's KB updates (xmllite WIC, for example) seem to fail if the OS
is
I think the problem is with your SpawnDialog event... try NewDialog instead.
--
View this message in context:
http://www.nabble.com/Confusing-UI-Issue-tf4646232.html#a13344788
Sent from the wix-users mailing list archive at Nabble.com.
Okay I figured it out... you need to ommit the transform's file extension.
In my example, just call the file 1036 and embed this.
--
View this message in context:
http://www.nabble.com/Embedded-locale-transforms-tf4523004.html#a13001287
Sent from the wix-users mailing list archive at
Has nobody had any experience in this sort of behaviour? I've been sent this
link in another forum, and I'm sure I'm covering all the steps:
http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm
Is there a minute detail not covered that I could be made aware of?
Cheers,
Has anyone any experience of this kind of thing?
I've got an MSI with ProductLanguage property set to 1033, likewise the
Languages field of the Summary Information is set to 1033. I have created a
French transform (just for the dialog strings, for testing purposses) and
called it 1036.mst and
.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gareth at
Serif
Sent: Friday, August 17, 2007 3:38 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] AppSearch nesting
Thanks for your feedback Phil. you're right
Has anyone had any cause to install the Windows Imaging Component (WIC) from
Microsoft?
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e011506-6307-445b-b950-215def45ddd8DisplayLang=en
The problem I have is that there are 10 language variations and that hey
appear to only install on
You can also avoid making the directory into a global property by using
[$component_name] to evaluate the full path to where a component is
installed to in the same way that Rob suggests [#field] fo evaluate the
location of a file.
Cheers,
Gareth
Rob Hamflett wrote:
Rob's suggestion is if
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gareth at
Serif
Sent: Tuesday, August 14, 2007 4:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] AppSearch nesting
Hi,
I am trying to use AppSearch to determin if the installed
I would suggest that you add an event to the 'Next' button on one of your
early dialogs (perhaps even the Welcome dialog) and display the info on a
spawned dialog...
Publish Event=SpawnDialog
Value=VistaWarningWindowsNTgt;=600/Publish
Then define your 'Vista Warning' with the dimensions and
Yes
shambhu kumar wrote:
--
View this message in context:
http://www.nabble.com/how-to-create-language-transform-in-wix--Is-it-possible-to-do-this-in-wix--tf4277987.html#a12197382
Sent from the wix-users mailing list archive at Nabble.com.
Hi,
I am trying to use AppSearch to determin if the installed version of
FlashPlayer is sufficient (greater than 8.0.24.0) and have nested some
searches as follows:
Property Id=FILEVERSIONTEST Secure=yes
RegistrySearch Id=FileVersionTestA Root=HKCR
I think you may have to define Advertised=no (I think 'yes' is the default
if undefined) else the shortcut creation will attempt to make a shortcut to
the component's keypath, which isn't a file and so may choose not to make
one (as you've seen).
Cheers,
Gareth
--
View this message in context:
I use DXMajorVersion and DXMinorVersion to test if DirectX is up to date and
to install it if not (required for some apps I build packages for).
Best of luck,
Gareth
--
View this message in context:
http://www.nabble.com/DirectX-Support-Condition-tf4210480.html#a11981522
Sent from the
I think it's a documented bug of the progress bar behaviour on certain
versions of Windows Installer if your package is installing more than 2GB of
data.
Regards,
Gareth
Man, Shirley wrote:
Hi all,
On Windows 2000, our installer's progress bar first jumps to 100%, then
rewinds back to
I don't think your uninstall process should remove anything it didn't create.
Sure, the application itself may make some entries, but you do not need to
know what they are and remove them... these entries are usually user
customisations that I'm sure they'd want to have back when they reinstall
You need a 1 in your new dialog publish too...
Publish Event=NewDialog
Value=[WixUI_WEBConfigToReadyToInstall_Next]1/Publish
--
View this message in context:
http://www.nabble.com/Am-I-using-a-property-and-condition-correctly-tf3801422.html#a10780538
Sent from the wix-users mailing list
Hi John,
I've dnone something similar, but while the MSI technology incorporates the
LockPermissions table in order to achieve such things it actually removes
any existing permissions and as such far more intrusive than you'd really
want. I use SubinACL.exe from M$... the WiX looks something
Thanks for your comments, but with the single file, the patch is 3 times
bigger when including whole files. When you factor in the other patching
files from the real case (which all make much smaller binary differences)
the final patch is closer to 4 times bigger.
Do you not think there's a bug
So, do you think it's a bug in MsiMsp.exe that I can report to M$ or with the
Candle/Light stages prior to it?
--
View this message in context:
http://www.nabble.com/Patch-failure-when-using-non-whole-files-tf3778936.html#a10721753
Sent from the wix-users mailing list archive at Nabble.com.
Hi guys,
Here's a puzzle for you to consider. I had a big patching issue for one of
my largest packages and have narrowed the issue down to such a degree that I
have created an identicle package that merely installs one single file that
when patched to it's second version, the MSP creation goes
Providing your old package made in InstallShield is MSI based, you can
perform a major upgrade by including the old package's UpgradeCode in the
new package's Upgrade Table.
Best of luck,
Gareth
--
View this message in context:
Hi guys,
I have a problem that I'd like to install file and use it as part of a CA,
but before the registry is written. Initially this seemed easy enough by
sequencing the CA within the InstallExecute sequence somewhere between
InstallFiles and WriteRegistryValues, but in this scenario the CA
Hi Rob,
I've started to see some peculiar results due to priveledge issues on Vista
and found myself back in this thread. I find, as I think you have, that
once the app in question is installed, the elevation being passed to the
client side of the install differ greatly depending on how you
Thanks for that Tony.
I actually found it and just checked Nabble to post as such.
It works a treat as you'd expect.
--
View this message in context:
http://www.nabble.com/SubinACL-usage-abroad-tf3679498.html#a10287110
Sent from the wix-users mailing list archive at Nabble.com.
Thanks for your advice. I have done some detailed comparisons between the
log of the successful repair (with UAC prompt) and the unsuccesful repair
(without UAC prompt) and here are the unique lines for each case...
WORKING REPAIR:
MSI_LUA: Credential prompt not required, user is
I think all you want is a pair of components with the required registry
values you want in each feature... the installation will choose which
registry value to write automatically.
Regards,
Gareth
--
View this message in context:
To compy with users' prefered browsers, i find it easier to simply make the
shortcut (*.url) file and install it to the ProgramMenuFolder as a file.
For translations, you can localise the name of the file and so how it
appears in the shortcut list, but not the rollover description... so for
Quite. I wrote one a while back, something like this...
Dialog Id=ShortcutsDlg Width=376 Height=266
Title=$(loc.DIALOG_GENERIC_Title) NoMinimize=yes
Control Id=BannerBitmap Type=Bitmap X=0 Y=0 Width=376
Height=45 TabSkip=no Text=DlgBanner /
Control Id=Title Type=Text X=15 Y=6
While the dialog works, I'd much prefer some kind of list box of the
ProgramMenu rather than a browse control that enables users to dump their
shortcuts in some inappropriate locations... actually, anyone want to
suggest how to go about such an improvement to the above code?
Thanks,
Gareth
--
The InstallPrivileges attribute is indeed set to elevated. I never
actually figured out what behioural differences there were on the strength
of this attribute though...
--
View this message in context:
http://www.nabble.com/UAC-Prompt-Required-tf3637831.html#a10184850
Sent from the wix-users
Hi guys,
I have an issue with a package I've built which has a number of merge
modules, including that for MDAC2.8. This has some properties set on the
client side of the installation that need to be passed to the server side in
order for it to install when needed. It is not needed on Vista, of
I find that the msi file extension tells Vista that the process requires
elevation and you get the UAC prompt before the UI Sequene begins.
Therefore, by the time you get to your 'Install' button with the potential
to display your UAC Shield, the install doesn't require elevation (as it all
It's because the olders you're installing files to can be in per-user or
per-machine locations depending on the value of the ALLUSERS property. For
example, your start menu, or the AllUser's start menu. Since the package
doesn't know what ALLUSERS will be set to until it's executed, the
The Warnings are okay - it's errors you want to worry about. I get the same
verification reports and a big fat Vista verification logo to go with them
:-)
--
View this message in context:
http://www.nabble.com/Problems-with-MFC-and-CRT-8-Merge-Modules-tf3487580.html#a9738055
Sent from the
You can probably declare your 'RemoveFile' ines in a component that has a
component condition triggered by a property that your user can configure via
a checkbox in your UI. I believe that 'RemoveFile' lines work on install
and all files will be removed on uninstall so probably won't be the
I regularly install DirectX as part of my WiX packages, here's the code for a
file I just include for the functionality to 'appear':
?xml version='1.0' encoding=utf-8?
Include xmlns='http://schemas.microsoft.com/wix/2003/01/wi'
Feature Id=DirectX9 Title=DirectX9 Level=100
Re: FASTOEM
I read the same requirement and found details on what is required for this
functionality to work here:
http://msdn2.microsoft.com/en-us/library/aa368576.aspx
So, it could be something as simple as the package not been ran from the
same volume... when it does work, it goes lightning
I've done something similar, but while I don't have a solution to your
'double-click Next' issue, I can suggest how my validation works.
On the 'Next' control button I have a pair of Punlished Events for
true/false as you do, but only one is NewDialog. The
REGISTRATIONCODEVALID=false case
In my experience the product name is the name of the app and shouldn't change
when you localise the app. For example, when John goes to Spain he doesn't
start calling himself Juan, he's still called John.
Sorry I couldn't answer your technical queries.
--
View this message in context:
I can confirm that warnings are all okay for Vista logo... I have a number of
ICE33 warnings and have gotten that all important badge of approval for my
packages. You can also get away with errors that appear as aresult of
including MS merge modules, so long as they're well documented. The
Does running the application generate new files in your folder(s) and so the
installer has lost full ownership and so won't remove them? Try performing
a treewalk of your installation files and see if anything new shows up that
you weren't expecting.
--
View this message in context:
if this is a change from version 2, but in version 3
localization variables are called via '!(loc.VariableName)' (instead
of '$(loc.VariableName)').
Maybe just a typo in your ListItem declarations?
Henrik Opel
Gareth at Serif wrote:
Hi guys,
I have a ComboBox defined in my UI
Hi all,
To bring up to speed with my problem... I had to convert some installs to
pass Windows Logo testing, which meant (among many other things) that no
component can have more than one shortcut. So, since I require a Start menu
shortcut and a Desktop shortcut, I came up with the brilliant
Hi guys,
I have a ComboBox defined in my UI to list a selection of countries for the
end-user to choose from... these countries are localised so that when the
install is translated, these entries are correct for the country of
distribution. Something like this:
ComboBox Property=COUNTRY
You need to make sure that your bootstrapper has one of the magical Vista
strings within it like setup or install. This will instantly elevate
the priveledges within Vista unless it has a corresponding Manifest file
telling it not to.
I get the impression that you're calling the MSI file
51 matches
Mail list logo