Phil, yeah looks like we are on the same page in understanding. (nice book
by the way it has helped me alot)
In this case however the OP mentioned he did not want the overwrite effect
of REP being early.
On another note you could also look at marking the component not to be
uninstalled. (thi
MSI caches a stripped package under windows\installer\{guid}. In some
situations thats enough and in some situations, the original package ( as
specified in the Sourcelist HKCR\Installer\Products\PackgedGUID\Sourcelist ) is
needed. Sometimes it's not really needed but if ResolveSource is sche
the copy of the msi at c:\windows\installer is only a partial cache..
there are no files in this copy. As such any file replacements will use the
original install source as its healing point.
Rob Mensching-2 wrote:
>
> Something is causing "source resolution". Look in a verbose log file to
Something is causing "source resolution". Look in a verbose log file to see
what caused it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Langley
Sent: Wednesday, July 09, 2008 20:36
To: General discussion for Windows Installer XML toolset.
Subjec
Hi guys,
I have a question that will probably have a simple and obvious answer...
I have built a WiX MSI, where registry keys are installed under HKCU,
and the application is installed with the administrator account - it is
required to run under minimal user privileges.
When the 'underprivileged u
hmmm your wording is a little confusing.
the idea of using MM's is so that you gain referencing counting by proxy of
the components within the MM's being static.
this post explains exactly how component reference counting works.
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!1
Bummer. Is this something I should log a feature request for (to add
functionality to the PermissionEx CA)?
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Rob Mensching [EMAIL
PROTECTED]
Sent: Wednesday, July 09, 2008 8:21 PM
To: General discus
Hi all,
I was wondering how to correctly hand reference counting for components
in shared COM (say using an MSM). It seems to me that if two different
products are trying to use a same COM components and one upgrades it the
reference counting on any new components that are included will be
broken.
Thanks for your reply...
I tried with below code but no luck :(
As you suggested I spited into two actions.
But I couldn't understand what does the property attribute refers to in
below sample (Property="StartWebServer").
Actually I want to run .bat files from WIX.
Thanks one more time fo
Not sure the PermissionEx supports the deny as you want it right now. I am
certain that the Permission (which translates to LockPermission table) does
*not*. Of course, PermissionEx is our own extension/custom action so it can be
extended...
-Original Message-
From: [EMAIL PROTECTED]
What's happening when REP is just after InstallValidate ("early in the
install") is that the older product is uninstalled and then the new one is
installed. In this situation Tom's data file just gets removed and then
installed by the new product.
When REP is "late" in the install the new produ
Phil are you sure about this.. (not trying to be difficult I would be
interested to understand what your getting at here.)
My understanding of the sequencing relating to upgrades is the opposite of
what you suggest.
by moving the RemoveExistingProducts action earlier in the sequences you are
ef
I'm trying to 'ADD' [to existing permissions] an explicit deny permission on
BUILTIN\Users for "Traverse Folder / Execute File", for "Subfolders and files
only".
I'll spare you all the gory details of what I've all tried [Permission and the
util:PermissionEx elements (from within a "CreateFolde
I think the problem is that you can't evaluate properties in the
ExeCommand attribute so you need to do it in two steps. Here is an
example that works for me:
NOT
Installed
NOT
Installed
I hope this helps,
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROT
Hi All,
I am very much new to WIX. I am trying to implementing executing
commands on Command prompt.
I am using below code to do but its failing while installation.
Where .bat is placed on c:\ path.
I have tried with different methods like using properties. Please help
me on this.
Reg
I'm still working on my merge module solution here, and my last e-mail riled
up some interesting convo, but never really answered my questions. I'm
trying to use the Configuration element in my modules, does this just make
the elements available as properties? Do I need to access them some othe
Read:
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx
Do be advised that if you aren't following good versioning patterns upstream
and you move the the action in the sequence, you might see other adverse side
effects.
Christopher Painter, Author of Deployment Engineering Blog
Hav
The relevant source code is:
Where should I schedule it instead?
--
Tom
Wilson, Phil wrote:
> Where is your RemoveExistingProducts sequenced? A major upgrade will not use
> file update rules if it's sequenced early in the install, such as just after
> InstallInitialize.
>
> Phi
Blogged with more detail at
http://blogs.msdn.com/jasongin/archive/2008/07/09/votive-project-platform-configurations.aspx
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau
Sent: Wednesday, July 09, 2008 10:39 AM
To: General discussion for W
Where is your RemoveExistingProducts sequenced? A major upgrade will not use
file update rules if it's sequenced early in the install, such as just after
InstallInitialize.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Singer
Sent:
Is there a way to suppress a specific instance of a light.exe warning?
For example, I'm consuming some VBA 6.4 merge modules where they incorrectly
authored a DefaultDir of "SOURCEDIR" for the Directory of "TARGETDIR". When
including this module into my WiX v3.0 installation that has a DefaultD
If your original project was created with a build of WiX more than a couple
months old, you might need to edit the project file in notepad or the VS text
editor to add an x86 Platform to the Debug and Release PropertyGroup
conditions, like this:
bin\$(Configuration)\
...
bi
When I right click on the project properties and select 'Build' or 'Tool
Settings' see an error on the right pane with the message
"An error occurred trying to load the page.
Value does not fall within the expected range.".
Thanks
Vidya
-Original Message-
From: [EMAIL PROTECTED] [mailto
What errors are you getting?
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vidya Kukke
Sent: Wednesday, July 09, 2008 10:25 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Stable Wixv3 build for VS 2008
Hi,
Need help with the Wixv3 ve
Hi,
Need help with the Wixv3 version to use for VS 2008.
I have downloaded 3.0.4227.0 and get errors when I open the properties window
of any wix project. Is this expected? What am I missing?
FYI - The original wix project was created on VS 2005 using Wix v3 Beta and
then we moved to 3.0.4227.0
Thanks.
The trouble is I already use wixui_en-us.wxl and wixui_fr-fr.wxl. But few
strings (not all) of wixui_en-us.wxl are not overriding and few messages are
still in English despite a French version, with of course the same id.
I use the following switch : -ext WixUIExtension -cultures:fr-fr
I want to add: I've read in the mailing list archive, that the installer by
default should *keep* the file, but for our tests it definitely
overwrites/uninstalls the file.
--
Tom
Thomas Singer wrote:
> Our installers install also a configuration (text) file where - if necessary
> - the user c
27 matches
Mail list logo
