Hello again.
I had the opportunity to test this on a virtual machine, and including
the SelfRegModules action solved the problem. Now it seems that
everything is being registered.
About the 2008 runtime msi. It doesn't work for me because we're using
the activex viewer from crystal XI and its
I will be out of the office starting 02/11/2007 and will not return until
06/11/2007.
I will respond to your message when I return
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find
Folks,
I'm trying to do this:
* Install MyApp v1.0 into a custom directory (e.g. X:\wacky\weirdo\MyApp)
* Later, install an update (to v1.01 or v1.1) that picks up where my v1.0 is
installed and goes to the same directory by default
I figured since not a whole lot has changed between 1.0 and
I actually rewrote the code for the last test. If you look at the original
example the names match.
However, after trying a few more things, it looks like the FaceName attribute
takes the localized string just fine. It's the Size and Bold attributes that
are not preprocessing the localized
Actually, paul, I suspect that Facename isn't working either, you just
don't get an XSD validation error because there's no rules for the format
of the face name.
I bet if you hardcoded the size and bold attributes and compiled your MSI
you'd have the !(...) stuff in your facename in the
All I'm saying is that if you remove the location that the software is
installed to, it is unreasonable to uninstall, repair, reinstall, or perform
any other operation since the location the software has been installed to no
longer exists. What do you want Windows Installer to do differently?
To get the second option to work, save the installation directory in the
registry when you install v1.0. Then when performing a major upgrade,
have v1.1 search the registry for the installation directory and use it.
-Brian Simoneau
From: [EMAIL
Marc, I concur with Brian, but make sure you have your AppSearch sequenced
somewhere before your RemoveExistingProducts in this case, or else MSI
will remove the existing version before you get a chance to search the
registry for the item. BTW, if you have already released 1.0 and you
can't
The issue is that those columns in the TextStyle table are not marked as
localizable so the !(loc variable replacement never happens.
Please file a sourceforge bug on this.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy
Sent: Friday, November 02, 2007 8:51 AM
To:
Hey Guys,
As part of our install my installer needs to enable ASP.Net 2.0 Web Service
Extentions in IIS 6.0 and above and windows 2003. I tried using
iis:WebServiceExtension but I am unable to get it to enable the said
extentions..Here are some of my code snippets...
Component
Thank you for the clarification!
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: [EMAIL
PROTECTED]: Fri, 2 Nov 2007 07:26:39 -0700Subject: RE: [WiX-users] MSI returns
1606 Could not access location
All I'm saying is that if you remove the location that the software is
In WiX 3.0, how do I pass the command line and timeout (QtExecCmdLine and
QtExecTimeout respectively) properties to the CAQuietExec custom action when I
need it to Execute=deferred?
When I attempt this, CAQuietExec complains that it can't get the properties.
Regards,
Adam
Pedro,
I'm not sure where (or if) there is a runtime MSI for the original XI
release. There is for XI R2 (typically in C:\Program Files\Business
Objects\Crystal Reports 11.5\Samples\en\CR .NET\.NET 2 Runtime
Setup\CrystalReports11_5_NET_2005.msi for the .NET 2.0 version. There
may be something in
Hi,
I get an error message and my guess is that it is because I do what is
said in the subject: Installing the same as admin and user.
My installer is installed centrally by our administrators and users do
not have write access to it. Now some users need to have the
installation on their own
Are you saying that TARGETDIR should not be set to
\\wmiscratch\scratch\davut\DaRT? But that's where software was installed
right?. Installer should be setting it internally. My problem is; if the share
become unavailable then there seems to be no way out. Can't uninstall or
repair, or install
On Oct 24, 2007 7:59 AM, Bob Arnson [EMAIL PROTECTED] wrote:
Geoff Finger wrote:
Instead what I found was a post claiming I don't think you want to
reference ProgramFiles64Folder either. Use ProgramFilesFolder and
Windows Installer will put things in the correct directory based upon
the
I was looking at using the XmlFile custom action.
I wanted to store the values in the Property table; and issue various
installs with setting customized (by me) using Orca. However, it
appears as if you have to hard code the value attribute of the xml tag;
and that it therefore cannot
Sorry if I'm missing something, but I'm trying to use a dialog control of
Type=Edit that worked fine in V2 but crashes the msi in V3 with an error of
2885. I'm not readily finding and mention of what the values can be here,
besides Text/Combox/but what about PathEdit, Edit?
I'm sure I'm
Sorry never mind I have this working.
On Fri, 2 Nov 2007 20:36:34 -0800, Serge Gart wrote
Sorry if I'm missing something, but I'm trying to use a dialog
control of Type=Edit that worked fine in V2 but crashes the msi in
V3 with an error of 2885. I'm not readily finding and mention of
Hi
I want to launch the default browser after my installation is finished.
I tried this
Property Id=BROWSER
RegistrySearch Id='DefaultBrowser' Type='raw'
Root='HKCR' Key='http\shell\open\command' /
/Property
CustomAction Id='LaunchBrowser' Property='BROWSER'
Well FYI I am using WIX 2
From: Srinivas Tirupati
Sent: Saturday, November 03, 2007 11:36 AM
To: wix-users@lists.sourceforge.net
Subject: Launching Default Browser
Hi
I want to launch the default browser after my installation is finished.
I tried this
Property Id=BROWSER
RegistrySearch
21 matches
Mail list logo
