Hi Blair!
I have latest stable version of WiX 3.0.
I was playing around with this issue and found a workaround.
If I add a reference to "MyProject", Visual studio Solution Explorer
displays a reference to it as "MyProject (MyProject\MyProject)".
So I edited WiX project file (Setup.wixproj) manua
MSMs generally don't place anything in the Add or Remove Programs list.
Where did the msxml.msm file you are using come from?
-Original Message-
From: Eschenbacher, Frank [mailto:frank.eschenbac...@voltdelta.net]
Sent: Thursday, November 05, 2009 6:41 AM
To: wix-us...@lists.sourceforge.n
There is a way to build an MSI such that it doesn't cab the files at all, which
produces a layout that is identical to an admin install. I haven't tried it
myself, but it probably involves some manipulations of the Media element and
the SourceName attribute of the Directory element(s), as well
For the test scenario, go to Add/Remove Programs and select "Repair", and
make sure that the registry value doesn't change (test from each of the two
initial states).
Not sure why it doesn't delete, but you could try adding a RemoveRegistryKey
element to the same component.
-Original Message-
Yes. 1033 = en-US = English (United States). The attribute's value needs to
be the decimal LCID value.
A list of LCIDs are here:
http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Thursday, November 05, 200
Thanks Blair.
I tried it by using your code example. It works!
But I found a problem, after uninstallation, this registry entry is still in
the registry. Even if I use "createAndRemoveOnUninstall", it's still there. I
checked the uninstall log, it doesn't say if the delete key operation is oka
Thanks Blair. You're a truly expert on Wix.
I added "" in my code. It works!
By the way, how does LCID work? Currently, in my code, I have "Language='1033'"
in my code, is this okay?
Thanks.
From: Blair
To: General discussion for Windows Installer XML tools
Blair, all files we patch are part of merge modules. There are no files
outside of a merge module at all. I guess that rules out the WIXPDB approach.
Anyway, wixpdb files are introduced in WIX3, isn't it? In that case, we do not
have any original wixpdb files since we used WIX 2 to generate the
.wproj files are reported to be Wwise project files (from
http://www.audiokinetic.com/).
WiX msbuild (votive) project files have always been .wixproj as far as I
know. I have never seen .wproj used with WiX.
-Original Message-
From: Colin Yu [mailto:coli...@microsoft.com]
Sent: Thursday,
Not quite. There are two things at play here: the ALLUSERS property and the
"don't elevate" flag.
If you set InstallPrivileges to "elevated" the flag is not set (the
default). If you set InstallPrivileges to "limited" the flag is set. Nothing
is done wrt the property with this attribute.
If inste
If you set InstallScope="perUser" then your MSI will be marked to not prompt
for elevation. As a consequence you cannot set ALLUSERS and all resources
must go into locations that don't require elevation, unless you want to see
the error you are reporting. ProgramFilesFolder always requires elevatio
Attachments usually don't survive the list server.
What version/build of WiX do you have installed?
-Original Message-
From: Sandi Remar [mailto:sandi_re...@yahoo.com]
Sent: Thursday, November 05, 2009 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-u
It sounds to me like a bug. Please file one - don't forget to copy all the
helpful information (version information, sample authoring + log failure
messages) from your mail into the bug.
Thanks,
Mike Carlson
-Original Message-
From: Duncan Kelbie [mailto:duncan.kel...@neuralt.com]
Sent
Regarding "I've tried scripting the installer to remove the file in question
first before writing the new one in, but only the file remove is running the
first time the installer is run. If the installer is run a second time, the
file remove does not run (because the file isn't there and the fil
This might get the job done for you...
?Foo.exe=3 AND NOT PATCH
This would work if your upgrade process will install missing files.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, November 05, 2009 10:40 AM
To: 'General discussion for Windows Inst
Sascha's point is that you can save this yourself if you really want to get it
from the registry. ProductID might be the better property to change because
it's been through any verification that might be done by ValidateProductID.
However if you've already shipped the original it's too late, whi
InstallPrivileges is to do with whether Windows can show the UAC prompt or not.
InstallScope sets the ALLUSERS per machine/per user value. I'm not sure what
you mean by one overriding the other. If you can author a true per-user install
that you know doesn't require elevation then you do a per-
Hi Pally,
Perfect! I'm off and running. Thank you!
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, November 05, 2009 9:19 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch information
Unless you're speci
So, is there any way to work around this issue? Is there something I can do in
the handler of my button to cause a focus change before I invoke my CA?
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, November 04, 2009 4:45 PM
To: General discussion for
Yes, I am using the 64 bits version.
However, I do see the WiX project templates and I can add a new WiX project.
But it is interesting to notice that if I create a new WiX project, the
extension is .wixproj. The existing .wproj projects fail to load because the
project types are not understood
But as I just tried out, it is impossible to author a elevated perUSer
installation: InstallScope="perUser" actually does override a manually coded
InstallPrivileges="elevated" attribute! So is that a bug in WiX?
> -Original Message-
> From: Wilson, Phil [mailto:phil.wil...@wonderware.com]
When running my .msi on Vista, I do not see any difference between
InstallScope="perMachine" and not using this attribute at all. Is
"perMachine" the default?
--
Let Crystal Reports handle the reporting - Free Crystal Repo
This perMachine / perUser discussion really confuses me. ;-)
I tried what happens if I set InstallScope="perUser".
The result is, that I cannot install the software on Vista, because it says
I do not have sufficient access rights to enter C:\Program
Files\[Manufacturer] (no, it does not ask
Do you see the Wix Project types in the Add New Project?
If not, Votive did not install. There was a post a while ago on the list about
manually installing the templates that would take care of it. We had a
similar problem where the 64bit version would not install (3.5.1030) fully on
some of
A couple of comments:
1. It's only since UAC that the per-machine/per-user difficulty has been
around. It's not been there forever. MSIINSTALLPERUSER is the solution in MSI
5.0.
http://blogs.msdn.com/windows_installer_team/archive/2009/09/02/authoring-a-single-package-for-per-user-or-per-machi
Hello Blair!
Thank you for your answer.
But I wanted to ask something else.
I will try to explain a little better:
I have a solution named "MySolution" with two
solution folders - "MyProject" and "MySetup".
Solution folder "MyProject" has one library project named "MyProject".
Solution folder "My
Blair,
thank you very much for your detailed answer. :-)
So if I understand correctly, all I have to do is to set ALLUSERS to 1? Ok,
nice. :-)
But actually, after decades of seeing lots of installers asking the
administrator where the *he* wants the files get copied to, I do not
understand why i
I have installed the WiX Toolset but VS 2k8 still fails to load .wproj
projects. Can you give me a help on this?
Thanks
Colin
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simpli
It appears to be a property set by MSI in a location with a strange GUID. In
brief: I cannot find logic between the application and the place MSI puts
this parameter.
I need to make a customaction call to the "MsiGetProductInfo" method in
"msi.dll", passing some params. However, I've still not fou
Thx so far. I tried to do this from within C# code, and this works very
well.
Can someone tell me how I can call a method in "msi.dll" from WIX, passing a
number of parameters to the method?
TIA,
Tim
-Oorspronkelijk bericht-
Van: Wilson, Phil [mailto:phil.wil...@wonderware.com]
Verzonde
30 matches
Mail list logo
