Our application 'MyApp' has two features, one coded in wxs file and other in a
merge module. Both the features are coded with
ConfigurableDirectory="TARGETDIR".
We would like to install the app one directory off of user's choice. We have a
default directory for installation "c:\ProgramFiles
Thanks Rob. We did notice this started happening after adding a new managed
custom action. The custom action does not need a rollback so we didn't
schedule one. Does this seem reasonable? Should we always schedule a
rollback?
| -Original Message-
| From: Rob Mensching [mailto:r...@robmensc
Thanks.
On Mon, Jul 26, 2010 at 9:37 AM, Jeffrey Cutting wrote:
> I've narrowed this down to being an issue with Light and the -xo (output
> wixout format) and -bf (bind files) options. I set OutputAsXml = true and
> LinkerBindFiles = true in my project file. Those get passed to the Light
> MSB
The best way to work around this problem with the WiX toolset is to use the
EnsureTable element to have the WiX toolset use its definition of the table
instead of the MSM's version of the table.
On Fri, Jul 30, 2010 at 10:24 AM, Blair wrote:
> 1st step: try to not use them.
> 2nd step: try to fi
I think there was a bug open about this that might have been fixed in this
week's build. Or it might still be open.
On Thu, Jul 29, 2010 at 11:46 AM, Tomasz Grobelny <
tom...@grobelny.oswiecenia.net> wrote:
> I have a strange issue with automating visual studio with votive: I create
> several pr
Sounds like you've run into a Windows Installer bug. I've never heard of
anything like that but if it's intermittent who knows how often it happens
in the wild.
On Thu, Jul 29, 2010 at 5:41 PM, Bassam Tabbara wrote:
> Hello,
>
>
>
> We are seeing a weird case where the rollback sequence is incorr
Wow, that's a new one. I'm not sure how an access violation would happen on
a close handle. Can you provide any more information about when this
happens?
On Thu, Jul 29, 2010 at 6:29 AM, Thomas Svare wrote:
> Hello,
>
>
>
> We're currently using WiX 3.5.1902 but for the last couple of releases
>
What does the verbose log file say?
On Sat, Jul 31, 2010 at 10:19 AM, Blair wrote:
> Hard to say with such limited information, but my best guess would be a
> problem with component rule violations. You really don't give enough of the
> right information to make concrete diagnosis and give good
a) - from http://msdn.microsoft.com/library/aa368281.aspx - UILevel property
(read from session). Note that you can always safely call MsiProcessMessage.
If the UI does not allow your message, it will be added to any log AND some
sort of default response will be returned.
b) - Not sure, but you ca
Hi,
I looked at the docs at
http://msdn.microsoft.com/en-us/library/aa368250%28VS.85%29.aspx but I
could not find any information:
Within a DLL extension for MSI, how can I found out ...
a) In which UI mode I am (full, reduced, simple, no)
b) If I am called in InstallUISequence or InstallExecu
Hard to say with such limited information, but my best guess would be a
problem with component rule violations. You really don't give enough of the
right information to make concrete diagnosis and give good advice.
-Original Message-
From: S.P [mailto:iraniangirl9...@yahoo.com]
Sent: Satu
Dear All,
I have an installer which can have different versions such as V1.7, V1.8, etc.
After installin each version, we have some problems with uninstalling it.
When we uninstall V1.8, it also uninstalls V1.7 or disables it. This is not on
all machines. The primary one we have seen the probl
12 matches
Mail list logo
