It seems that MSI cannot write REG_DWORD type values to registry..Wht is the
workaround for this?
Anidil wrote:
I'm using the following code to write an integer value to windows
registry.
Registry Id='PCPERegNotification' Root='HKLM'
Key='Software\Wow6432Node\Product\Notification'
Hello Bob,
For installing assemblies into GAC we were adding Assembly Manifest tag
in the .wxs which is authored by the tool but we were getting errors
stating Assembly tag is not supported. We need help about how existing
MSI's can be modified by the WIX 1.0?
Below contains the
I am trying to use wix for installation of my product .When
i try to use the UI wizard in my wxs file by using the
following lines:
UIRef Id=WixUI_Mondo /
UIRef Id=WixUI_ErrorProgressText /
I get the fillowing error while linking :
unresolved reference to the symbol 'WixUI:
It seems that MSI cannot write REG_DWORD type values to
registry..Wht is the workaround for this?
Anidil,
The documentation for the registry table in MSI says:
This column is the localizable registry value. The field is Formatted.
If the value is attached to one of the following prefixes
I have tried prefexing # for all the DWORD types but after
running the MSI i see that the registry is getting updated as
type REG_SZ
Looks like I misled you - the RegistryValue element has a 'Type'
attribute, which you can set to 'integer':
RegistryValue Id=Registry1 Name=IntValue
I have tried prefexing # for all the DWORD types but after running the MSI i
see that the registry is getting updated as type REG_SZ
John Hall-9 wrote:
It seems that MSI cannot write REG_DWORD type values to
registry..Wht is the workaround for this?
Anidil,
The documentation for the
Hello,
After not using WIX a while, we made a new release, and now VS2005 is
crashing when i want to create a new WIX project.
Also opening an old wix project, does not open anything.
I already removed and reinstalled votive, but this did not solve the
problem.
I recently installed also
Oki..The ReistryKey and RegistryValue tags are used only with
WiX 3.0 right?
Yes. Under WiX 2.0, you seem to just use the Registry element, which
also has a Type attribute:
Registry Id=Registry1 Root=HKLM Key=Software\Product Value=42
Type=integer /
Cheers,
John
LEMIRE, JOHN wrote:
The scenario is an automated deployment environment that attempts to
run a scheduled upgrade of minor revisions of a product.
Therefore the numbers of the currently installed and to be installed
versions only differ in the revision position.
The major/minor/build positions
What are possible issues with running an installer silently from the
commandline:
MSIEXEC /i MyInstaller.msi /Log LOGFILE.TXT /qn ADDLOCAL=AllMyVariables
This works for almost the entire installer. However, it has a problems
with an internal property that is set on a UI page (it doesn't get
What value do I specify in the Validation attribute of the TargetImage
element to have the product code, upgrade code, product version and most
importly the product language to be validated? Thx!-
This SF.net email is
From my understand of reading MSIExec's help file (and I might be totally
wrong) the /a flag (for admin install) is for a network install. If that's the
case with the CA not running, why would it then generate an error message?
Is it possible to run the util:FileShare as a local admin instead
I'm new to Wix and I'm using Wix 3. So far I've been able to figure out
everything I need to do except one thing. I need to install a few exe's
after the main program installs. Here's what I have. It doesn't run the
exe's though. One thing I did notice however, after installing the program
If you run silently from the command line, the UI sequence is not processed
at all, it goes straight to InstallExecuteSequence.
Therefore, if you have any custom actions that will dictate what gets
installed, you need to ensure that they are scheduled in
InstallExecuteSequence, instead of or
This error usually refers to a custom action that's running an exe
that's being installed with the product, but isn't installed for some
reason (perhaps because the exe is already on the system and won't be
replaced because of versioning rules). So it can't run the exe from your
package because
{BODY}-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now
Trying to get my installer to work. It works for the main files but there
are some files I don't want to install unless I click Complete (as Opposed
to typical, I'm using mondo). It copies the files correctly regardless but
when I also want it to run the ones that it copies. I think the
Hi!
I have this statement below that changes a configuration string in a xml file:
XmlFile Id=CfgConfigureConnectionString
File=[TARGETDIR]\Web.Config
Action=setValue
Name=value
Value=Data Source=[SQLSERVERNAME];Initial
That's not what I meant. When you said it was a `Visual Studio MSI` I didn't
think you meant that it was from the Visual Studio Team, I thought you meant
that it was a VDPROJ created MSI. In fact, I can see it's created using WiX 2.0.
Which brings us back to the orginal question
I've been working on building an installer using Wix. Building an msi seems
to work well and I have no major problem. But where I'm getting bogged down
is in the things surrounding it, such as the setup.exe program. I have a
couple of questions.
1. I've noticed the setupbld.exe utility and
Christopher Painter wrote:
IMHO, that's even more inexcusable.
Why is it inexcusable to redistribute a redistributable package?
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
Still
Alexei wrote:
just wondering if it is possible to have an install read values and assign
them to properties if there is the appropriate .ini file but if the file can
not be found to go ahead and display the GUI (which will then be able to get
the data from the user).
There's no support
Public properties are described:
http://msdn2.microsoft.com/en-us/library/aa370912.aspx
http://msdn2.microsoft.com/en-us/library/aa371245.aspx
A subtle correction of the definition is that a public property cannot
contain lowercase letters. It may contain other special
How do I make a property Public? Or are there only certain public
properties?
Christopher Painter wrote:
Only public properties can be passed via the command line. Also you
probably want to set the TRANSFORMS property not the TRANSFORM property.
Magus [EMAIL PROTECTED] wrote:
I have
Only public properties can be passed via the command line. Also you probably
want to set the TRANSFORMS property not the TRANSFORM property.
Magus [EMAIL PROTECTED] wrote:
I have a bootstrapper that is suppose to set 2 properties via command line,
however none of the properties that I set in
You don't need it as a custom action. Just specify a property Property
Id=TARGETDIRe:\/Property
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ravit Shapira
Sent: Tuesday, July 24, 2007 11:46 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to change
Anidil,
Does it help if you pass Value='1' instead of Value='#0x0001(1)'?
Daryn.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anidil [...]
Now that i don't get permission denied message after prefexing # for all the
DWORD types as follows :
Hey all,
just wondering if it is possible to have an install read values and assign
them to properties if there is the appropriate .ini file but if the file can
not be found to go ahead and display the GUI (which will then be able to get
the data from the user).
The thing I'd like is to have this
davemave wrote:
I did a verbose log install but do not know where to look for service
installation failure in this log.
The installer ends with succes.
Do you have any tips on looking into the log to see if the service is
installed or not?
Just look for the IDs you use for
John Hall wrote:
I wanted to add a checkbox at the end of my installer and found the
WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT property. However, when the
checkbox is displayed it is drawn with the wrong background colour -
see the attached screenshot. This is with Wix 3.0.3120.0.
Is there a way
Magus wrote:
Is there any way to convert Unicode to said code page via code? I am lucky
enough to be using an external UI. There is only 1 dialog (Disk Cost) that
is displays internally. Is there a way to get the information that a Disk
Cost dialog would display from the MSI?
I don't
I don't know if it was actually the case, or if it was an email
formatting thing, but it looked almost as if the original MSI name had
spaces in it, and the one that works didn't. Could that possibly be the
root cause of the problem?
Regards,
Richard
I did a verbose log install but do not know where to look for service
installation failure in this log.
The installer ends with succes.
Do you have any tips on looking into the log to see if the service is
installed or not?
Bob Arnson-6 wrote:
davemave wrote:
The msi installs succesfull,
I'm using WIX 2.0 and i have mentioned the type attribute in the registry
tag as given in my code..
But it doesn't seems to work as expected :(
John Hall-9 wrote:
Oki..The ReistryKey and RegistryValue tags are used only with
WiX 3.0 right?
Yes. Under WiX 2.0, you seem to just use the
I'm in the process of migrating my installer from InstallShield to WiX
3. As part of this I have reorganised and rationalised the features in
the product.
When I come to do a major upgrade from the old installation to my new
one, all of the features in my product in the customize dialog are
I'm using the following code to write an integer value to windows registry.
Registry Id='PCPERegNotification' Root='HKLM'
Key='Software\Wow6432Node\Notification' Name='Notification Sounds Enabled'
Action='write' Type='integer' Value='0x0001(1)' /
It gives me a permission denied to
Mike Dimmick wrote:
The MSI file probably shouldn't even be renamed -- aren't there issues
with using a different filename for an upgrade MSI?
Yes, only major upgrades support it. And on wix.sf.net/releases, we
don't rename it. But on the SF releases page, we have to, hence the .zip
we
Only public properties can be passed via the command line. Also you probably
want to set the TRANSFORMS property not the TRANSFORM property.
Magus [EMAIL PROTECTED] wrote:
I have a bootstrapper that is suppose to set 2 properties via command line,
however none of the properties that I set in
I'm doing a remote admin installation using an internal MSI deployment tool. My
problem is that when I go to set the folder permissions for a FileShare it's
telling me I don't have permissions to do this.
Is there an easy way to elevate the MSI installation so that it will attempt to
setup the
I have a bootstrapper that is suppose to set 2 properties via command line,
however none of the properties that I set in the Cmdline are being set. Is
there something I am doing wrong?
CMDLINE = PropertyA=18 PropertyB=C:\Temp TRANSFORM=KOREAN.mst
--
View this message in context:
We should be thanking the Wix team for providing this 'third-party' .msi
from Microsoft instead of making us hunt it down on MSDN. Geesh.
-Matt
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christopher Painter
Sent: Thursday, July 26, 2007 10:57 AM
To: Bob
Hi,
I checked in the Project-Properties-Configuration Properties-C/C++-Code
Generation - Runtime library is Multi-threaded(/MT) only. Is there anything
else I should do in order to resolve this issue? The installer is working
fine in windows xp and vista and the issue is only with windows server
Where can I find the current list of preprocessor directives? I'm using the
list from this article,
http://msdn2.microsoft.com/en-us/library/aa302186.aspx#wixsetup_topic6 But
I'm getting compilation errors in VS when using the
ProjectAggregator2-3.0.2925.0.msi. Thanks
Example error: Error 1
Quattro IV wrote:
Hello, can anyone point me to a way to get a shortcut installed under
the windows volume folder without getting the following warning?
WindowsVolume points to the root directory where Windows is installed.
Is that really what you wanted?
--
sig://boB
http://joyofsetup.com/
John Hall wrote:
I'm in the process of migrating my installer from InstallShield to WiX
3. As part of this I have reorganised and rationalised the features in
the product.
When I come to do a major upgrade from the old installation to my new
one, all of the features in my product in the
Collins, James wrote:
Yes I would agree fragments offer much more and I will keep that
in mind moving forward. For me however I need a migration path from Wise
to WIX and that's going to be merge modules for now. Once I have
convinced my team WIX is the way to go (and believe me I'm
Scott Palmer wrote:
If an upgrade isn't supported then what happened when I renamed the
file and it just worked ?
Because only a major upgrade supports renaming the MSI. It shouldn't be
renamed on the SF releases page. As I recall, we shipped old versions in
a .zip file because of this
If an upgrade isn't supported then what happened when I renamed the file and
it just worked ?
I think that the msi files provided with WiX itself should be good examples
to follow... but perhaps they aren't.
Scott
On 7/25/07, Quattro IV [EMAIL PROTECTED] wrote:
I got that same error, you
Hello,
I am using Wix 2.0.5325.0
I have a app.config that I want to modify:
configuration
applicationSettings
TestService.Properties.Settings
setting name=Property serializeAs=String
valueValue/value
/setting
setting name=MyProperty serializeAs=String
Hi,
I created a Windows Installer DLL using Visual Studio C++. The installer is
working fine in windows xp and vista. But when I run the installer which has
custom action dll in windows 2003, it is not installing in windows server
2003. Is it known issue or does any body have idea this issue?
hi
i m having msi of my product which is working on all 32 bit windows versions
now iwant to create msi which will wirk for bith 32 and 64bit os or will
work for 64 bit os. i have no idea what r the changes i m suppose to make in
my msi.
--
View this message in context:
Hi All,
My installer needs to read a value from the registry and set the install
path based on that value. However, the installer should install 2 levels
up the value that was read from the registry. For example, I read the
registry and get the following:
C:\Temp\First\Second
And I want my
You can't set the installUI level (as I've been told) via the MSI. If you have
a UI, it will be called. You can condition the UI to pop up particular screens
if an INI file is not available, but the base UI screen (welcomedlg) will still
be brought up in both cases.
-Original Message-
Alan Sinclair wrote:
If I'm moving to WiX, which version should I use. How far off is
stable v3 likely to be?
A colleague said I would wait for a stable 3.0 before considering
switching. It's vastly improved over version 2, and is not backwards
compatible.
The biggest risk with WiX v3 is
Crusty Applesniffer wrote:
If user selects Service N°2 during installation, Service N°1 feature
will be unselected.
If user selects Service N°1 during installation, Service N°2 feature
goes back to unselected
There's nothing automatic, either in the UI or with feature conditions,
that
Naresh Krishna Kumar K wrote:
I checked in the Project-Properties-Configuration Properties-C/C++-Code
Generation - Runtime library is Multi-threaded(/MT) only. Is there anything
else I should do in order to resolve this issue? The installer is working
fine in windows xp and vista and the issue
Hi All,
I am trying to use wix for installation of my product .When i try to use
the UI wizard in my wxs file by using the following lines:
UIRef Id=WixUI_Mondo /
UIRef Id=WixUI_ErrorProgressText /
I get the fillowing error while linking :
unresolved reference to the symbol 'WixUI:
You need to include the UI library file i.e. wixui.wixlib while linking your
object file
chandan Koushik wrote:
Hi All,
I am trying to use wix for installation of my product .When i try to use
the UI wizard in my wxs file by using the following lines:
UIRef Id=WixUI_Mondo /
UIRef
Can you manually register it? I mean something like YOUR_SERVICE.exe
/REGSERVER or similar? Does it show then?
For checking if at the end of the installation it was 'registered within the
system', you might check you registry under
HKLM\SYSTEM\CurrentControlSet\Services even though I'm not
I created a Windows Installer DLL using Visual Studio C++.
The installer is working fine in windows xp and vista. But
when I run the installer which has custom action dll in
windows 2003, it is not installing in windows server 2003. Is
it known issue or does any body have idea this issue?
i m having msi of my product which is working on all 32 bit windows
versions
now iwant to create msi which will wirk for bith 32 and 64bit os or
will
work for 64 bit os. i have no idea what r the changes i m suppose to
make in
my msi.
You need to make a copy of your 32bit WiX source (you
Gaurav Tiwari, HCL-Industry Solutions wrote:
We need help about how existing MSI's can be modified by the WIX 1.0?
Sorry, WiX v1 hasn't been supported for almost three years now. I've
never used it personally as it wasn't publicly released.
--
sig://boB
http://joyofsetup.com/
Public properties in WiX are specified by the fact that the Property Id (the
name) is all in Caps
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Magus
Sent: Thursday, July 26, 2007 12:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
63 matches
Mail list logo