I am populating UserName property in UI textbox and then storing it in
registry. For this I am using custom action to set this variable at
UISqeuence and ExecuteSequence. Everything works great.
I found that if I change this value to something else, my registry is never
changes to new value. i saw
In the project vacuum-im ~ 1200 files,%)
To fill the Features have to specify 1200 components (if we consider a
1 component is a 1 file)
2012/6/21 Hoover, Jacob :
> Since heat allows for a XSLT to be applied to the output "anything" is
> possible but I would highly advise against it. A component
Since heat allows for a XSLT to be applied to the output "anything" is possible
but I would highly advise against it. A component is the most granular part of
an installation, so if the first file in a component exists and is of the
correct version (assuming no other file is marked as the keypat
like this https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: >heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
Components for
I have checked the verbose log and found that property assigned correctly
in InstallUISequence but it gets modified in InstallExecuteSequence.
I had to use custom actions at both places. How can I correct it?
On Wed, Jun 20, 2012 at 9:38 PM, Rob Mensching wrote:
> I would use a verbose log fil
I'm using WixUI_FeatureTree with a few custom dialogs. I want to get a
string entered by the user on one dialog and use it in a call to a managed
custom action implemented in a C# DLL assembly. What is the best, and
hopefully easiest, way to do this?
Thanks,
Bob
--
I am displaying my custom messages as progress text based on my custom
action but everytime I am seeing the same message of Install CA on install,
uninstall, repair.
I am not able to figure it out. Here is my code:
Importing ... (this may take a few
minutes)Importing Virtualization ... (this may
t
I like the button progress bar on installation. Shouldn't it also be used
during repair and uninstall?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/taskbar-button-progress-bar-to-WixStdBA-on-repair-uninstall-tp7578993.html
Sent from the wix-users
That's total side-effect. May not always be true.
On Wed, Jun 20, 2012 at 12:32 PM, Dan Muller wrote:
> Found that the order that the fueatures are listed is the order in which
> they
> are installed. By making the merge module first, it guarantees that they
> files in the merge module are insta
Thanks Rob, appreciate the insight.
On Fri, Jun 15, 2012 at 12:54 PM, Rob Mensching wrote:
> I need to write the blog entry about this. Bundles are registered on the
> machine. Bundles can be uninstalled, manage the package cache and they
> reference count their packages. Basically, they do every
So my understanding is even using AFTERREBOOT or RESUME, I would still have
to condition all the dialogs and actions so that they don't run after the
REBOOT correct?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Continue-logging-after-a-force-reboo
Found that the order that the fueatures are listed is the order in which they
are installed. By making the merge module first, it guarantees that they
files in the merge module are installed first.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chai
Thanks Rob! That's very handy to know.
It turns out that the missing component was something that one of the 3rd
party merge modules was supposed to install. I don't really know why it
didn't install, but at least now I know where to focus to debug this.
___
Frank Jenner
On Wed, Jun 20,
That solved the issue.
Thanks!
Carl
>>> Rob Mensching 6/19/2012 2:15 PM >>>
Random guess, mark the Merge/FileCompression="yes". It is very possible the
VS2005 merge module incorrectly marked all of it's Files as explicitly
compressed or uncompressed and you need to force it. I'm assuming you
Look in the machine's event log. You should see messages from the Windows
Installer telling you what it repaired. Basically, the Windows Installer
thinks your Component with an Advertised entry is broken and needs to be
fixed, perpetually.
On Wed, Jun 20, 2012 at 10:27 AM, Frank Jenner wrote:
>
In my installer, I have created a few shortcuts on the start menu and the
desktop. However, the first time that I launch an application through its
shortcut, the default Windows Installer dialog pops up with a progress bar
and tells me to "Please wait while Windows configures" my application. I am
I've been following this discussion for the last day or so because I'm
attempting something very similar. I have multiple MSIs that I would like to
be installed as a single user experience ... just as the documentation says.
However, I haven't been able to even get a bundle project to run. I get an
The WixExtensions extend the compiler/linker and provide embedded .wixlibs
to do provide functionality that is not built-in. For example, the
WixUtilExtension adds custom elements so you can do things like manipulate
XML files (aka: XmlFile and XmlConfig). When you use one of those custom
elements
Bob Arnson-6 wrote
>
> Not sure what the writer was smoking that day but there's nothing like
> that in the WiX code and it's not supported by MSI. Could you file a
> bug? Doc needs fixing.
>
Thanks, Bob. I figured it was probably something like that. Probably just
hasn't been implemented y
RESUME appears to be the special case that the system rebooted during the
installation.
http://blogs.msdn.com/b/windows_installer_team/archive/2005/09/19/470980.aspx
Phil W
-Original Message-
From: victorwhiskey [mailto:victorhwhis...@yahoo.com]
Sent: Wednesday, June 20, 2012 8:49 AM
It's just a property - use it as a condition on anything you don't want to
repeat, such as NOT AFTERREBOOT.
-Original Message-
From: victorwhiskey [mailto:victorhwhis...@yahoo.com]
Sent: Tuesday, June 19, 2012 9:38 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Continue
Hi,
Is there an API to remove registry value on uninstall? As per the Wix API
doc, RemoveRegistryValue allows deleting the value during installation only.
I want to delete an environment variable on uninstall. It looks like this
can be done by deleting the value from registry under
HKEY_LOCAL_M
Hi,
Past two days am working for this, am unable to find the solution. Could you
please update the response for last my updates queries?
Its very urgent.
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Planning-package-customiz
I would use a verbose log file and watch the changes to the Property value
to ensure it changed the way I expected.
On Tue, Jun 19, 2012 at 8:52 PM, Ravi Raj wrote:
> I want to store a textbox value in registry but my situation is little
> different.
> I am doing a registry search for a particula
I was pretty sure there was documentation in the WiX.chm that details how
to do this. You have to be very careful to unreference the old dialog that
you are replacing. Otherwise, you'lll end up with two dialogs that end up
duplicating a bunch of symbols.
Unfortunately, the error messages are not t
It appears the "config.xml" file is being embedded in your MSI. If that is
the case, why not just make it easy to author the RemoveFile entries when
the MSI is built. The result will be the same but you don't have a separate
declarative file in your MSI.
Note: It doesn't appear your custom action
1. Your BA should *never* modify the machine state.
2. Put all modifications to machine state in packages. We wanted to create
a "WindowsComponentPackage" or "WindowsRolePackage" (or something) that you
could put in a Burn Chain to turn on Windows components but didn't have
time to get it done in W
WiX v2 did not run the static analysis tools (ICE). WiX v3 we started
running the tools automatically to help everyone find bugs before they
shipped.
On Wed, Jun 20, 2012 at 2:13 AM, Gareth wrote:
> Hi Rob,
>
> Thanks for your attention, I did as requested, but was not getting the same
> result -
An MSI cannot install another MSI.
On Wed, Jun 20, 2012 at 7:33 AM, Dan Muller wrote:
> Yeah, I had found that link and it was not the most useful, I eventually
> found some references and learned from them.
>
> I got a bundled exe, but I was wondering if there was a way to create a
> bundled ms
Also, how is the RESUME property used/related to AFTERREBOOT proptery?
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Continue-logging-after-a-force-reboot-during-the-install-tp7578946p7578971.html
Sent from the wix-users mailing list archiv
Hi,
We have been successfully using admin installs and explicit patch.wxs files
(specifying what components to patch under the ) to create msp
files for a few years now and I have just started to look into making patches
automatically from our release builds. I intended to leave the
empty and let
Yeah, I had found that link and it was not the most useful, I eventually
found some references and learned from them.
I got a bundled exe, but I was wondering if there was a way to create a
bundled msi instead?
Also, can someone point me to a tutorial on changing the burn UI?
http://schemas.mi
Thank you, Peter
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detecting-upgrades-UPGRADINGPRODUCTCODE-tp7578945p7578968.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Hi,
I would like to know the utility/need of the - ext WixUtilExtension and
-ext WixUIExtension while using the candle.exe and light.exe , i am higly
confused with it .
as earlier i was trying to build the msi as follows:
candle.exe main.wxs -dPlatform=x86 -ext WixUtilExtension
candle.exe MyInst
While uninstalling I see small window for uninstall (with no UI
interaction). I want to launch Maintenance UI whenever user choose to
uninstall via Add/Remove program.
How can I do this?
--
Thanks and Regards,
Ravi Raj
--
Hi,
I want to use the '
i need to know if i want to use that for the radio button , how would i
accomplish that say i write:
-what should i specify in the Value?
Also I have the following scenario:
i added a new dialog(Renamed the InstallScopeDlg to AssistanceDlg.wxs) and
wants to build a msi i
Windows 7 64 bit SP1 and VS 2005 Team Edition For Software Developers SP1.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com
From: Naim Kingston [naim.kings...@ancamotion.com]
Sent: 20 June 2012 01:06
To: General discussion for Windows Installer
Thanks John, for the hint. Unfortunately it did not resolve my issue.
To make my question and related fragment (see below) more clear:
1) I have no issue with setting correct credentials to app pool itself, this
works absolutely fine. My problem is, that virtual directory created by the
installer
Somehow I am not satisfied with that I have done in the implementation given
http://www.csharpque.com/2012/06/wix-custom-action-delete-files-before.html
here
Is there anyone who can suggest a better implementation... all the
requirement and implementation is written in the page.
I am not in fav
Hi Rob,
Thanks for your attention, I did as requested, but was not getting the same
result - I am now getting a more useful and expected error message of
"LGHT0345 : '...\Microsoft_VC100_CRT_x64.msm' is a 64-bit merge module but
the product consuming it is 32-bit. 32-bit products can consume only
If you take a look in an MSI built using MajorUpgrade, you'll see 2
properties are set in the Upgrade table called WIX_UPGRADE_DETECTED and
WIX_DOWNGRADE_DETECTED. They'll be set after FindRelatedProducts has run.
-Original Message-
From: victorwhiskey [mailto:victorhwhis...@yahoo.com]
Se
Hi,
I've created a managed bootstrapper application with burn which installs a web
application packaged as an MSI. This works great so far.
Now I need to ensure that certain server roles and features are installed.
Since we target only Windows 2008 R2, I can use the ServerManager Cmdlets for
t
42 matches
Mail list logo
