. The process is much clearer for me
know.
-- Yan
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, December 03, 2009 16:42
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] NeverOverwrite attribute behavior
The text yo
l Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Thursday, December 03, 2009 5:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] NeverOverwrite attribute behavior
Thanks for the answer, Blair.
However, I'm not sure I fully understand the w
ow.
-- Yan
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, December 03, 2009 16:42
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] NeverOverwrite attribute behavior
The text you are referring to relates to the
element
(unless y
Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Thursday, December 03, 2009 3:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] NeverOverwrite attribute behavior
Thanks for the answer, Blair.
However, I'm not sure I fully understand the way it works.
The MSDN
oolset.'
Subject: Re: [WiX-users] NeverOverwrite attribute behavior
MSDN explicitly says that the keypaths required for this flag are files
and
registry entries. When they are explicit they only guarantee the
behavior
within the scope they describe. Since you are using a directory as the
k
MSDN explicitly says that the keypaths required for this flag are files and
registry entries. When they are explicit they only guarantee the behavior
within the scope they describe. Since you are using a directory as the
keypath (and not a file) I assume the flag is being ignored, but you would
hav
6 matches
Mail list logo
