Hi everyone,
I've got a real big problem here on applying minor upgrades to my
product. I really need your help here :)
During the first install, I ask the user where the product should be
installed (by using the wix standard Gui)
But on minor upgrades, I do not ask him again. I just re-install
On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet
[EMAIL PROTECTED] wrote:
Hi everyone,
I've got a real big problem here on applying minor upgrades to my
product. I really need your help here :)
During the first install, I ask the user where the product should be
installed (by using the wix
Johan Appelgren a écrit :
On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet
[EMAIL PROTECTED] wrote:
Hi everyone,
I've got a real big problem here on applying minor upgrades to my
product. I really need your help here :)
During the first install, I ask the user where the product should
Hi everyone,
Let's say that I have a registry key HKLM\Software\MyProduct with a
String value TheDir = c:\program files\My product\module
I can easily get the value by using a RegistrySearch:
Property Id=MYPROP
RegistrySearch Id=MYPROP Type=directory Root=HKLM
Key=Software\MyProduct
Hello,
I want to register 2 policies with the same publisher-file (pub) to the GAC
example - i have those files:
mypolicy.dll
policy.1.0.mypolicy.dll
policy.2.0.mypolicy.dll
mypolicy.pub
I register the file policy.1.0.mypolicy.dll like that:
Component Id=RUNT_policy.1.0.mypolicy.dll
String manipulation is not supported in WIX, you will have to write a
C++/.net/vbs custom action to get substring.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frédéric
Viollet
Sent: Tuesday, July 01, 2008 3:41 PM
To: General discussion for Windows
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
-
[ProductName] indicates that ProductName is a property. Are you sure you don't
want $(loc.ProductName)?
Rob
Andreas Hellwig wrote:
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).
Ok, thanks for your answer.
Fred
Nitin Chaudhari a écrit :
String manipulation is not supported in WIX, you will have to write a
C++/.net/vbs custom action to get substring.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frédéric
Viollet
Sent:
Well I used [ProductName] like it is used in the WiXUI localization
files. Everywhere else it works correct. Just in the shortcut it isn't
replaced correctly.
in the .wxl file i've got this:
String Id=Test_UninstallLinkTitle Overridable=yesUninstall
[ProductName]/String
String
From the windows installer SDK:
http://msdn.microsoft.com/en-us/library/aa371847(VS.85).aspx
The `Shortcut`.`Name` field is not a formatted field.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Hellwig
Sent: Tuesday, July 01, 2008 8:54 AM
On Tue, Jul 1, 2008 at 11:29 AM, Frédéric Viollet
[EMAIL PROTECTED] wrote:
Johan Appelgren a écrit :
On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet
[EMAIL PROTECTED] wrote:
Hi everyone,
I've got a real big problem here on applying minor upgrades to my
product. I really need your help
Am I going to have to resort to a custom action to read the settings and
propagate them? If so, ugh. It seems like there should be a WiX custom
action for simply reading the contents of an XML file (value or
attribute) and putting the value into a property.
Open feature request that no one
Johan Appelgren a écrit :
On Tue, Jul 1, 2008 at 11:29 AM, Frédéric Viollet
[EMAIL PROTECTED] wrote:
Johan Appelgren a écrit :
On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet
[EMAIL PROTECTED] wrote:
Hi everyone,
I've got a real big problem here on applying minor
I had similar things happen to me and solved them by using CA like:
Property Id=PROGRESS_DLG_TITLE Secure=yes /
CustomAction Id=SetProgressTitle Property=PROGRESS_DLG_TITLE
Value=!(loc.ProgressDlg_Title) Execute=immediate /
In this case above dialog title contained [ProductName] which
Ryan Markel wrote:
The problem is that if I try to run the generated msp as suggested:
msiexec /p patch/patch.msp
Windows Installer simply brings up the maintenance dialog for the currently
installed version, instead of patching it. Is there something totally obvious
that I'm missing
John Nannenga wrote:
From the windows installer SDK:
http://msdn.microsoft.com/en-us/library/aa371847(VS.85).aspx
The `Shortcut`.`Name` field is not a formatted field.
The InternetShortcut element in WixUtilExtension is primarily to support
URLs in shortcuts but it has the side-effect
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
Andreas,
Another option is to make ProductName a localization string in your wxl file.
Then use !(loc.ProductName) everywhere, including in the Product element. This
is what we do and it works like a charm.
Neil
-Original Message-
From: Andreas Hellwig [EMAIL PROTECTED]
Sent:
Thanks for your help. I found a solution that works for me.
I splited the Name into two parts, the part before the ProductName and
the part after the ProductName. Instead of [ProductName] i define. Into
the Name attribute I put
!(loc.textPart1)$(var.myProductName)!(loc.textPart2). That version
Im trying to launch the default browser:
Property Id=BROWSER
RegistrySearch Id=DefaultBrowser Type=raw Root=HKCR
Key=http\shell\open\command/
/Property
CustomAction Id=LaunchBrowser Property=BROWSER
ExeCommand=http://blahblahblah/; Return=asyncNoWait/
linking it with the finish button,
How do I execute it? You mean execute a shortcut of a url?
--
Arthur Curvello
Convergência Latina
tel: +55 21 2494-5476
email: [EMAIL PROTECTED]
Confidencialidade: A informação contida nesta mensagem de e-mail, incluindo
quaisquer anexos, é confidencial e está reservada apenas à pessoa ou
Try this;
CustomAction Id=CA_LaunchBrowser Return=asyncNoWait
Property=IEXPLORE ExeCommand=http://www.blah.com/ Execute=deferred
Impersonate=no /
Scheduled via;
/InstallExecuteSequence Custom
Action=CA_HelpInstall Before=InstallFinalizeNOT
Updating the community from Brian's and my offline conversation / investigation
...
When installing Team Build, the account used for the service is added to the
IIS_IUSRS group. I had added the build account to the administrators group,
but apparently this had little effect when running
Hello Everyone,
I have a question on how to popup a warning mesagebox if there is old
version already installed.
I will appreciate any help.
Backround:
e.g, I have installed a product with version 1.2.10.1.
Now I have a installation with a higher version 1.2.10.2
When I double the product.msi,
Rather than prompt the user to do the uninstall, have you considered having MSI
take care of it for you? How to make that work is reasonably well documented at
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx.
Note that this requires you increment
I just wanted to make sure I'm not doing thing the hard way here. I'm
creating an inatallation and I want my customers to be able to modify some
its many properties. From what I can see they have the following options:
1. Specify a property on the command line.
2. Use Orca.
3. Use a WiX
0. Modifying the MSI is not advised since that will mess with the signature.
I think MST will have the same problem, but it might not if using the
TRANSFORMS property (haven't tried). A tool to generate transforms makes sense
(Office used to ship something just like this called Office
A new How To topic (should be in the next weekly build) covers launching your
installed application after install. While not exactly what you are trying to
do it does demonstrate how to use the ShellExec cusotm action. You can modify
it slightly by changing the WixShellExecTarget element to
Similarly, what would the recommended approach be for the custom properties
values during a maintenance procedure (upgrade, repair, removal, etc...)?
A number of folks seem to simply squirrel the settings off in the registry,
then have the installation reg-search the values during maintenance
30 matches
Mail list logo