Hi,
I'm trying to modify the Browse_Dialog to check whether the selected
directory allready exists on the users computer and display a warning if
it exists. I'm not an WiX expert and so I would be happy if anyone could
give me some hints how that could be done.
Thanks
Andreas Hellwig
Hi,
I'm trying to create a shortcut with a localized name, but sadly
'[ProductName]' isn't replaced in the localization-string (same for the
description). Is there a method to get it working correctly?
Andreas Hellwig
=Test_startmenu_subfolder
Description=!(loc.Test_UninstallLinkDescription) /
any idea why the [ProductName] isn't replaced for the shortcut?
Andreas Hellwig
Rob Hamflett schrieb:
[ProductName] indicates that ProductName is a property. Are you sure you
don't want $(loc.ProductName)?
Rob
Andreas
Thanks for your answers.
I tried a property too. It didn't work. It wasn't replaced. Maybe that's
because the name field of a shortcut of the type Filename and not
Formatted. Well i guess i'll have to use text without the ProductName.
Andreas Hellwig
Tony Juricic schrieb:
I had similar things
works
best for me because we have a multi-language installer that is
configured by a script for different programm versions. I just didn't
want to script some manipulation for the wxl files to change the
ProductName in there.
So thanks for your input.
Andreas Hellwig
Neil Enns schrieb
Hi,
a big thanks for your help Neil. I've got an idea now how to manage the
language files.
Andreas Hellwig
Neil Enns schrieb:
Andreas,
You'll need to manually build each localized version of your MSI. Votive
doesn't currently support building multiple installers per language, nor
localization files into the project, some for german string some others
for the english versions. But I allways get a german version even if I
set the language attributes to english (1033). Does anyone have an idea
how to fix that?
Andreas Hellwig
Thanks for your answer. Yes I am getting the browse dialog, asking for
the msi file that was used to install the software. So that's the
exepected behavior.
Andreas Hellwig
Wilson, Phil schrieb:
MSI doesn't cache the entire MSI file - it discards the embedded CAB file -
so to check
thought the Windows Installer is caching the original
msi file. If it doesn't, is there a possibility to fix the repair option?
Andreas Hellwig
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy
Hi,
thanks for your answers. I'm new to installer development. Could you
explain the bootstrapper idea a little further?
Andreas Hellwig
Christopher Painter schrieb:
But you could write a bootstrapper that caches and tweaks the package based
on user input before calling
the UAC prompt.
Is there a way to avoid the UAC for the Per-User installation, and only
get it for the Per-Machine installation?
Andreas Hellwig
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell
11 matches
Mail list logo