what message type You used for session.message?
С уважением,
Бетке Сергей Сергеевич.
От: Phil Wilson
Отправлено: пятница, 21 марта 2014 г. 20:54
Кому: General discussion about the WiX toolset.
I'm not sure - I was under the impression that calls that that
ultimately ende
Hi David,
I have modified the WIX source file as below:
Hi,
I have a Main installer(*.msi) which is around 200 mb(6000+ files)
Am using Wix Patch creation method for creating minor patches(using
msimsp.exe and patchwiz.dll method)
Should i include all the 6000+ files in my upgrade image or just only
files which are changed and which should be patched
Hi,
I'm experiencing something strange with my custom bootstrapper.
When I click the "Install" button on a Windows 8 machine with enabled windows
updates, the installation hangs for some time before really starting to apply
my packages. In the log file I think I managed to track it down to the
In my particular situation the test pc and the dev pc are on different locked
down networks so I could not get the remote connection to work. But I hope
to solve that issue in the future.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Debugging-M
I have not been following this thread, but is it not possible to use the Visual
Studio Remote Debugging facilities so that you only have to install a bare
minimum on the test machine rather than the full VS suite? (see
http://msdn.microsoft.com/en-us/library/y7f5zaaa.aspx)
Daniel Madill
Quanser
That is exactly how I do it. I put a sleep at the beginning to give me a chance
to attach it to the process and then I can proceed with debugging.
Chris Adkins
DocuWare GmbH
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: Dienstag, 25. März 2014 14:20
To: Ge
Hi Bevan,
I have modified my source file as below. In the custom dialogs that i am
using i have disabled the edit control that shows C:\Energy Solution
International path(that part is not attached here). That's the way i
thought of restricting the user and in the next dialog i am allowing the
Yes. Not that I know of. I only seen it once I think where the computer was
out of date. Once I patched it, I didn't see it again.
-Original Message-
From: Ogrodowski, Sabine [mailto:sabine.ogrodow...@haufe-lexware.com]
Sent: March-25-14 10:37 AM
To: wix-users@lists.sourceforge.net
S
I suspect the issue is that you need to remember the values of your
properties and retrieve them prior to doing the uninstall.
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern
http://www.nichesoftware.co.nz/node/633
--
View this message in context:
http://
I think Woody used a warning message. Here is the block of code he had sent:
[CustomAction]
public static ActionResult UninstallMessage(Session session)
{
if (session == null)
{
logEventsApp.WriteLoggingEvent(string.Format(CultureInfo.Invari
I do not see anything suspect in the install log.
Components that get removed say 'Action: Absent' in the uninstall log.
Components not getting removed have 'Action: Null' in the uninstall log.
Also Registry entries are not being removed ('Action: Null'), even when using
SharedDllRefCoun
If the issue is that "disallowing uninstallation" message, then look
up the component guid in your MSI to see what it is, a file name or
registry item. Without that detail it's impossible to say if it's
working correctly. It may be shared because it's from a merge module
used by other products (Mic
You're not both simultaneously trying to create a restore point? The
other possibility is that the restore point mechanism is transactional
in the sense that if a particular update fails the system will be
restored to the restore point, so during that update you can't create
another restore point
Source code for the method :
[CustomAction]
public static ActionResult UninstallMessage(Session session)
{
if (session == null)
{
logEventsApp.WriteLoggingEvent(string.Format(CultureInfo.InvariantCulture, "{0}
; {1}", Resources.ArgumentNull
I found some "Disallowing uninstallation of component: {} since another
client exists" messages in the uninstall log, which look to be referencing the
exe files, but can't find any references to the those guids in my MSI or in the
Registry. They are not from a merge module, and I have never used
I believe the ID's are encoded in the registry to prevent manual scrubbing, but
the MsiZap may be able to help you if you can find a copy. You might want to
scan ARP on your dev machine after the application is uninstalled to see if
there is an old MSI lying around (or even look for old MSI's
Thank you Jacob. I renamed to target path (as a test) and all files/keys
installed and uninstalled fine. I've tried all my old MSIs to no avail, not
sure how long ago it broke. I'll ask around and look into msizap, now that I
know what's going on. You've been a big help diagnosing this.
Thanks,
We seem to have crossed threads here, Suvra's "disallowing
uninstallation" and Scott's similar sounding problem,.
Suvra is off looking at the actual file, as far as I know. I've no
idea why Scott would see "disallowing uninstallation" messages
referring to component ids that re not in the MSI fi
I would suggest the following:
Replace all manually generated GUIDs with '*' wherever possible. WiX can
autogenerate GUIDs for you in most situations (where you have a source file
I believe, it possibly works with RegistryKeys as well.. I can't remember).
You've also got duplicated RegistryKey en
I found a tool, called MicrosoftFixit*, that you can use to fix orphaned
installs that did not show up in ARP but were causing sharing issues with some
of my files. I now know what to do if this happens again. Thanks.
See http://support.microsoft.com/mats/Program_Install_and_Uninstall
Scott Moy
That just runs MsiZap in the end and leaves your machine in a dirty state. I
always told my testers that if they came to me with a installation bug after
running MsiZap to format the machine and try again. I didn't like hunting the
voodoo bugs that came from dealing with a machine that had MsiZa
Hi,
I am using the XMLConfig element in Wix 3.8 to add to an existing XML file.
The xml file looks like this before running setup:
SnippetCollection>
On
true
1033
%InstallRoot%\VC#\Snippets\%LCID%\Visual C#\
Visual C#
23 matches
Mail list logo
