Hi,
During installation/uninstallation we need a special registration of our dll:s.
This lead to four CA:s being scheduled for each dll:
$Meldis.Search.dll>2
$Meldis.Search.dll>2
$Meldis.Search.dll=2
$Meldis.Search.dll=2
But as I have close to a hundred dll:s, this results in th
Hi:
I'm working with a client who needs to do the following.
Firstly password protect there installations before the msi is run and ideally
at the earliest possible stage, i.e before anything is extracted).
And secondly, have the installation expire after a date they define-unique to
each install
History.txt has the complete list of changes.
On Tue, Apr 5, 2011 at 11:50 AM, Inulitka wrote:
> Is there any reference with a complete summary of WiX 3.5 release? Ideally
> I'm looking for a complete reference of the changes before I begin
> migration.
>
> thanks
>
> --
> View this message in c
I have the following scenario that I'd like to know if Wix is able to
handle. I have an assembly called bizobjects.dll with a version of 1.1.0.0
installed into the GAC, somewhere in configuring my setup I have an issue of
each upgrade to say 1.1.0.1 and so forth is getting installed and 1.1.0.0 is
Is there any reference with a complete summary of WiX 3.5 release? Ideally
I'm looking for a complete reference of the changes before I begin
migration.
thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/What-s-new-in-WiX-3-5-tp6243407p6243407.
Hi Swapna,
MSI throws a stand error code if it fails, which is 1603.
In order to track your failure, you need search your log with "return value 3",
which should give you the correct reason for failure.
PS:- feel free to contact me anytime, I can help you with windows installer.
Thanks,
Sujith
If you ever need to read a section of the registry that differs from the
bitness of the process you are executing in you can use this Windows API,
RegQueryValueEx
(http://msdn.microsoft.com/en-us/library/ms724897(v=vs.85).aspx). You can
change the section of the registry being read with the samDes
Phil, To Others,
Thanks for the reply. So the return value is what is shown below. I
don't see the words "PROPERTY CHANGE" setting the property value
anywhere. Furthermore, I don't see the property I'm trying to use
anywhere either. My goal is rather simple, I am just stumbling
everywh
This is a generic failure error. You need to hunt through the log an find the
exact place the install failed. Usually it is a result of custom action
failure.
Mat Skildum
-Original Message-
From: swapna.rachako...@thomsonreuters.com
[mailto:swapna.rachako...@thomsonreuters.com]
Sent
When I run verbose for .msi . I am getting following error in log,
Installation success or error status: 1603
I don't know what it means.
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
sma
Is your ProductCode different between packages? I suspect not as you've got it
explicitly defined it in your code below & the error you are seeing is commonly
caused by this. Try using Product@Id="*" to auto generate your ProductCode
every time you build.
Also try updating Package@InstallerVers
Swapna is using WiXEdit which is a GUI for creating .wxs files. See
http://wixedit.sourceforge.net/
WiXEdit (and WiX) have nothing to do with getting a verbose log of your
installation. Your package is installed by Windows Installer, WiX simply makes
it easier for you to create the package in
Hi Guys,
I'm trying to use Upgrade and RemoveExisitingProducts to completely remove a
existing versions (both newer and older) of a product, but it always complains
that a previous version is installed and I must remove it via add/remove
programs. I don't need to worry about patching/partial up
I think your tachyon relay got set to 2011 accidentally, you may want to aim
it at a time range to get answers appropriate to Wix 7.5.
Before you do though some 2011 lottery numbers would be good.
But seriously I'm not sure what you are asking, if you choose Install from
the build menu the msi wil
If you want to block installation of x86 MSI's on x64 platforms simply use a
LaunchCondition with "NOT VersionNT64" in the x86 package. Anything else is
pointlessly overcomplicating things.
That bug you refer to is in Burn, not candle /light. Seeing as Burn doesn't
exist in WiX 3.0 I'm not surp
I am new to WiX Edit 0.7.5 , Can anybody tell me
How to set verbose log using WiX 7.5
Thanks in advance !
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable
16 matches
Mail list logo