Hello,
Could you let me know as to what issue are you facing?
Or do you just want a confirmation as to whether what you are doing is
right?
To preserve the file that you have mentioned here, there are two ways:
-Schedule RemoveExistingProducts after Install Finalize. This is more
efficient. Ho
When will weekly releases be back?
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fro
Sigh 4 warnings x 6 merge modules :(
Okay thanks all :)
Steve
-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com]
Sent: September-24-13 10:41 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module question...
On Tuesda
On Tuesday, September 24, 2013, StevenOgilvie wrote:
> I have added it back to 1 WIXLIB
>
> when I compile it works but I get this error twice for each merge module:
> Warning 22 ICE30: The target file 'kd1er3dy.dll|SQLite.Interop.dll'
> might be
> installed in '[TARGETDIR]\EnterpriseAuditLog
Its annoying because the files will NEVER be installed on top of each other...
So you install the files to subfolders, then use DuplicateFile table to put the
"right" files into the proper folder?
I looked at the DuplicateFile element but it didn't make any sense to me?
Do you have an example?
Phill Hogland wrote
> I am relatively new also, but others have advised that implementing a
> MajorUpgrade is the simplest and generally recommended deployment plan.
> So to do this you either need to remember to change both the ProductCode
> (and ProductId = "*" lets Wix do this for you) AND you
It's a warning not an error. The way I get around this is to set the
Directory to subfolders like x86 and x64 and then use the DuplicateFile
table to get the right file installed to the right directory.
From: "StevenOgilvie"
Sent: Tuesday, September 24
If you change the version (manually or via a auto increment), AND you change
the Product Code (which is what Product Id="*" does) then you will be able
to do the Major Upgrade. In my prior post I was responding to this comment:
"That is ok, but then when I rebuild the installer (without any chang
That's a tough question - you're asking why the code might be broken after
a repair install, and there are no details. My guess is that you are doing
some registration by running code (instead of having Windows Installer do
it) and something is missing during a repair, such as property values that
I have added it back to 1 WIXLIB
when I compile it works but I get this error twice for each merge module:
Warning 22 ICE30: The target file 'kd1er3dy.dll|SQLite.Interop.dll' might
be
installed in '[TARGETDIR]\EnterpriseAuditLogService\' by two different
conditionalized components on an LFN
We have an app that when runs produces a quick Dos Window and then goes away.
So we are using the WiXCA - CAQuietExec custom action to call the app in
quite mode. This work great, but my question is if the App fails and I have
the WiXCA custom action set to Return the error code will it return the
Hi all,
I have 6 services merge modules, I have them building for both x86 and x64
(different output paths) all is fine…
I have to add 2 SQL Lite files, x86 and x64 to the 6 merge modules (the
binaries are built AnyCPU)
I decided to use 1 wixlib and condition the 2 files Not Installed and Not
Hi,
I am able to build and install major build on a machine
successfully.
I am able to login into deployed application after major upgrade. For
some reason, if I repair install and try to log into deployed
application, I get type mismatch error.
Is there any reason that could caus
1) http://wixtoolset.org/documentation/manual/v3/xsd/wix/majorupgrade.html
My MajorUpgrade element looks like this:
So presumably your Product element has a Version attribute that would be
something like "1.0.0". Say this is installed on client machines, and you need
to upgrade them. You wou
can you provide any details? I'm a wix newbie. I'm using wix 3.7. What do I
need to
1) Make sure my msi can support future upgrades
2) When the next msi installs, one of the files must not be changed (its a
data file, I need to keep it as it is.. )
please help !
--
View this message in conte
The MajorUpgrade tag is probably the easiest way to support upgrades.
-Original Message-
From: nkshirsagar [mailto:nkshirsa...@gmail.com]
Sent: September 24, 2013 08:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Need some help with upgrade support in first version of MSI
I'
I'm releasing a version 1.0 MSI this week and need to support upgrades since
the next version should recognise the earlier installation, and retain one
of the files installed in this msi without overwriting it.
What changes would I need at the minimum in this version so that the future
upgrades ar
Hello,
I urgently need to make changes to my wxs file to support upgrades in the
future and I need to release in a few days ! I need the next msi to
recognise the earlier installation, and retain one file while copying over
the new dll's.
Can someone please help me ? I'm pasting my wxs file below
18 matches
Mail list logo
