Have a look in the "DOC" folder where WiX has been installed. The help
files are some of the most complete references that you'll find
anywhere. Specifically WiX.chm and msi.chm
Also get yourself a copy of "The Definitive Guide to Windows
Installer" for a great paperback reference book. WiX is sim
Hi,
Have you thought about writing the original properties to a registry
entry or a file somewhere during install, then restore those same
entries during uninstall? Adobe do this with a number of their
products, creating a registry tree with all values that were changed
during install so they can
That "something" is the Property table in those merge modules has a setting for
ALLUSERS=1.
Perhaps you could add a hidden feature and put all those merge modules into it.
Then use the Condition/Feature (the Condition table) to set the level to not
install them if ALLUSERS<>1.
Phil Wilson
I don't know of this is it, but it looks like it might be (there is a page
on MSDN about relative and absolute URLs, and the XmlDocument.Load(string)
method expects a URL.
Try:
string path = p_Session["MANAGED_SEARCHWEB_CONFIG_PATH"];
p_Session.Log("cadata : " + path);
Hi,
I would like to import .reg files during compile time of my merge module. I
have many.reg files that change very often. So I would like to import it to my
components at compile time so that when I generate the merge module every day,
it has the latest Registry keys (obtained from the .reg fi
I've been working part time with WIX for a short time and I just began using
DTF to include a custom action in our install kit. I'm using an immediate
custom action and I just want to be able to read a file that has been installed
by a previous installation in the case of a major upgrade to extr
I have an issue with the UAC and IIS clashing. The guy that had the
responsibility of the install kit before me was (the install kit is still using
that CA) an unmanaged C++ custom action to get the list of created websites in
IIS at the start of the installUISequence. The installkit needs to ru
First, since you really have to consider at this point you have two differing
products due to the change in the product, upgrade, and package codes, you
will need multiple entries for the upgrade table to address your situation,
each with a differing version range and each with its own independent
Hello,
I think the information you are seeking would be found in the MSI Help
Library which can be freely obtained through the Platform SDK from MS.
Here, try this:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en
SDK
Choose the Windo
Hi all,
Sometimes, I'm just wondering where do you get the WiX knowledge?
For me, I use these resources:
1. WiX tutorial: http://www.tramontana.co.hu/wix/
2. Online help: http://wix.sourceforge.net/manual-wix3/main.htm
3. Alex Shevchuk Wix series:
http://blogs.technet.com/alexshev/pages/from-msi-
Thanks Bob.
I tried "WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT AND NOT Installed", but it still
doesn't work. I mean, I install it, then run msi again and choose 'Remove', in
the final page of the uninstallation, the "Launch Application" option is still
showing up.
Here is the code:
WIXUI_E
Thanks Blair!
"you can create an uninstallation shortcut, but that
is incompatible with the Vista Logo program." - wow, good to know. I'll
remember this. The reason we create the uninstall shortcut becuase our customer
ask for it.
"but you can use the
ARPNOREMOVE trick I mention to use UI from
I'm assuming that the @BinaryKey attributes are pulling the scripts from the
Binary table (populated with the elements). Thus, you probably don't
"need" the elements with those same files for the
elements at all. That should get rid of the need to delete them towards the end
of install.
---
The custom action(s) used by the MSM appear to be checking ALLUSERS before
it checks to see if it is selected for installation. Any "fix" would be
quite a hack that you would have to maintain (it would also involve using
the MSI SDK in your build).
Yet another reason that packages that switch betw
Disable uninstall from Add/Remove Programs, enable maintenance mode,
which will show a GUI during uninstall. Then allow user to uninstall
from maintenance, typically through a radio button selection that sets
REMOVE=ALL. The you can prompt the user for what you need (e.g. a SQL
password to drop a
Thank you so much, Blair.
"Because of the inability to prevent older versions from being reinstalled,
it is a Best Practice to not change UpgradeCodes when you change versions.
" - yes, I agree. And we're going to make 2.x and 3.x use the same upgrade ID.
"Unless 2.x and 3.x should be installed
si
On Thu, Aug 27, 2009 at 5:19 PM, Prabhakaran Paulraj <
prabhakaran_paul...@dynamicbi.com> wrote:
> Hi there,
>
> I tried appending the parameter to the ApplicationFile but it doesnt work
> since it assumes that to be as the File Name.
>
> Is it possible to pass any arguements from Bootstrapper to
Hi.
1) Check out the User and Password attributes of SqlDatabase.
Need to ask the user for user/password? Create controls in a dialog and
associate with properties.
Remember to hid the password, i.e.
2) Hmm...I'm not sure, but I think that this binaries are deleted.
3) Could you write a
Hi there,
I tried appending the parameter to the ApplicationFile but it doesnt work since
it assumes that to be as the File Name.
Is it possible to pass any arguements from Bootstrapper to the EXE called?
I am tried many but couldn make it.
Content-Type: text/plain; charset="iso-8859-1"
Tr
I was building WiX and noticed that AnyCPU assemblies are outputted to the
x86 folder. I was just curious as to why this was the case. Its not a big
deal, just curiosity.
--
View this message in context:
http://n2.nabble.com/Curious-Why-WiX-Build-Outputs-AnyCPU-assemblies-to-the-X86-Directory-tp
Hi,
to make the uninstall as perfect as possible I would like to save some
information for the uninstaller custom action.
Say if my installer custom action changes a setting then I would like the
uninstaller to undo that. The problem I face at the moment is that I can
only revert the setting t
Thanks for the response.
I'll just disable Cancel when the message is received from Windows
Installer.
Blair-2 wrote:
>
> We observed that ourselves. Basically if Windows Installer thinks that it
> has gone "too far" and it isn't reasonable/possible to cancel it ignores
> that request. Interna
I am currently creating an installer which have to create a database. This
works fine as goes, however I have a question:
Right now my code looks like this:
Thanks for your repley.
This still doesn't solve the problem. Doesn't that have the same effect as
using a custom property.
Either way, it appears that a condition doesn't solve my problem here. There
seems to be something embedded in the MSI file that is telling the installer
it cannot install
Hi,
Instead of using SKIP_MERGE_MODULES I'd just check for ALLUSERS=1 in die
Condition.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: asanami [mailto:alexsan...@gmail.com]
Sent: Thursda
Hi,
I need to be able to skip installation of the VC merge modules if is a
per-user install. (ie. ALLUSERS=2) and the user doesn't have admin rights on
the machine.
Ideally, this would be done by setting a property on the command line. e.g
MSIExec /i image.msi SKIP_MERGE_MODULES=1
I can make
Blair,
Thank you very much at last it worked.
I need to pass a parameter from the bootstrapper. Is it possible? I am using
the generic bootstrapper available with Visual Studio .Net 2005.
Any suggestions?
--
Let Crystal
Thanks for your help.
It seems I was being rather stupid, I was just doing Because that's all I was doing with the other directory
not realising that the other one worked because it was inside a
already. I needed to specify the Directory attribute explicitly.
Was staring at that for hours, I
Dear Yan Sklyarenko,
Thank you for your help!
> See , and element references
> in wix.chm for details.
I checked the portion, but I couldn't figure out any solution.
I think that using install level doesn't solve my problem.
What I want to do is as follows:
I have to implement 100 features.
Hi Blair,
I just want the installer WIx file to be more manageable as there are very
large number of folders. So I just want to keep the same structre as the root
folder has.
The folders may contain XML, ASPX, CS and images.
And my next step would be creating Virtual Directories.
Thanks
Jasp
30 matches
Mail list logo