After change/repair options setups asks for rebooting. In setup log I
found records that msi can't delete some *.rbf files in directory
"setup.msi". What problem is?
--
Free Software Download: Index, Search & Analyze Log
Hi
I'm struggling to get bind.AssemblyVersion working with my WIX 3.5 installer
for an ASP .NET 4 Web Application.
The documentation states I should be able to specify:
!(bind.assemblyVersion.MyAssembly)
Based on:
bind.assemblyVersion.FileID
So given my actual main web assembly is found via
I also added the following line the the AssemblyInfo.cs in the bootstrapper
Application library but it still will not run.
[assembly: BootstrapperApplication(typeof(TestBA))]
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Trouble-implementing-a-Bo
Sure. In the previous dialog you can usually put Conditions on the Next
pushbutton to display any other dialog based upon the Condition set by
the Property
Something like that is one approach, at least.
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wedne
Since I have set default properties I just need to test BEFORE I set the
default to make sure some key "required" properties are set and if any of these
are set then I could safely avoid the dialog UI and take the defaults for the
rest. How do I test for the existence of a property and disable t
Thanks for the tip.
-qn will probably solve the problem. What would be the syntax of ?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Wednesday, February 23,
I've written a MSI project using WIX 3.6 and now I want to create my own
bootstrapper. I want to write my own UI using WPF like WixUX so I create a
new C# library project and referenced the BootstrapperCore.dll and created a
class that inherits from BootstrapperApplication. For my test BA all I wa
If you get a verbose log, that will tell you the name of the custom action.
Phil Wilson
-Original Message-
From: Colin LeMahieu [mailto:clemah...@gmail.com]
Sent: Wednesday, February 23, 2011 9:26 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error 1723
I'm getting this
Hi,
To set a property from the command line you simply just set the property to
be equal to the required value.
e.g.
Msiexec /i installer.msi FULLYQUALIFIEDCOMPUTERNAME=Kevinspc.buyseasons.com
SERVICEUSER=bob etc.
Remember to make all your properties public my making them all CAPS to and
you may
I'm getting this error on startup for an MSI that previously worked.
Are there any tips for debugging this error? Is it unreasonable to
expect the name of the offending DLL or some way to attach a debugger
to an MSI while installing?
---
I can offer some help. For the command line you append your PROPERTYNAME
followed by an equal sign and then the value you want to assign to that
property. Like this.
msiexec /L*v c:\log.txt /i my.msi PROPERTYNAME1=value1
PROPERTYNAME2=value2
In my experience it seemed like if you gave it all "req
I would like to know what strategies are best to use if I optionally don't want
a UI. Right now I have a custom dialog that appears and it sets a number of
properties. If any of these properties are set on the command line I would like
to skip the dialog. That is one question. The second questio
For this to function you will need to make sure your install supports UAC and
elevated privileges as the target OS would be Vista or higher to see this type
of behavior.
You need to make sure the all deferred custom actions have the value
Impersonate="no" set. This will force them to run at th
Thanks for the help but I still can't seem to find out why the components added
in the 1st patch (and should still be in the second) are not there in the patch.
Details:
The original installer has 454 files. Version 1.0.0.1372
1st Patch: Small Update (QFE) -
Added 1 new director
I faced an identical situation.
New version application has a bootstrapper to upgrade to a higher DotNet
version. Older app crashed as it could not handle the upgrade of dotnet.
I wrote an unmanaged program which stopped older application process and
then launched the installer (with its boot
HOW to run the uninstallation/change as administrator from ARP panel?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HOW-to-run-the-uninstallation-change-as-administrator-from-ARP-panel-tp6055847p6055847.html
Sent from the wix-users mailing list ar
I'm no patch expert so I'm just guessing now. I'd focus on the component rule
violation - that might be the reason the files aren't included in patch2
(although I'd also verify the sequence start number in patch2 higher than any
file table sequence number in the RTM and patch1). Check if any compon
I figured out this,
I should use IntPtr ptr = new IntPtr(Convert.ToInt32(args[0] , 16));
To get the handle.
It is working now.
Thanks,
Lambert
--
Free Software Download: Index, Search & Analyze Logs and other IT data
18 matches
Mail list logo