Hi ,
i am getting a problem while deleting registry value,
I have a MULTI_SZ value in a key and i want to delete single element/string
within this value.
How can i do that?
Thank you.
--
Hi all,
We have a customaction:
(Not
Installed) AND (&Feature_XYZ = 3)
This works in initial install, but not in 'Change' mode.
>From
here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMode-Conditions-DON-T-work-td707286.html
), I learnt that "there is no suc
Environment vars?
-Original Message-
From: Will Sullivan [mailto:wsulli...@softdocs.com]
Sent: Thursday, December 09, 2010 2:47 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Uninstalling VSIX fails as CustomAction, but succeeds
when run from cmd
Wondering if anyone has trie
Maybe it's just my lack of understanding, but you don't seem to be giving us
many clues here. You say the problem Id is in "a generated file" - what file,
generated by what?
> -Original Message-
> From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
> Sent: Thursday, Decem
Hi,
As some of you have probably noticed, there has been some discussion
recently regarding problems with DIFxApp causing rollbacks. I did some more
investigation and was able to reliably reproduce the issue and come up with
a very good idea on what is causing the problem. All investigation was
Wondering if anyone has tried reversing a vsix install.
I have a custom action that runs on install, and the uninstall version which
runs on uninstall. The install works perfectly, but the uninstall fails for
apparently no reason.
This is the full contents of the WiX file, I don't see how I can shorten it
based on what you replied.
http://schemas.microsoft.com/wix/2006/wi";
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
Hi everyone,
I just notice this problem and I'm wondering if my maintenance dialog WiX
script was not written correctly.
I notice that if I use MsiExec /X command to uninstall my app (or through
Control Panel's Program and Features dialog box), the "REMOVE" property will be
set to "ALL". Howe
Aha! From http://upx.sourceforge.net/
" UPX achieves an excellent compression ratio and offers very fast
decompression. Your executables suffer no memory overhead or other drawbacks
for most of the formats supported, because of in-place decompression."
There we go, it has in-place decompression
Interesting. I did a little more digging and found this:
http://dennisbareis.com/makemsi-manual/dllca_c.htm
It suggests that upx.exe is used only to compress dll custom actions residing
in the Binary table.
I still don't see anything specifically that knows how to decompress the dll
prior to c
You'll need to properly specify and use namespaces.
XmlDocument doc = new XmlDocument();
doc.Load(@"c:\temp\MySource.wxs");
XmlNamespaceManager xmlnsManager = new XmlNamespaceManager(doc.NameTable);
xmlnsManager.AddNamespace("wix", " http://schemas.microsoft.com/wix/2006/wi";);
XmlElement root
If I'm reading this right, upx.exe is getting used at build time to compress
the file but the compressed file will then get stuffed into a cab anyway
(because that's what Windows Installer requires). Perhaps MakeMSI is not
compressing the cab and using it strictly as a container.
You could simu
Here are your options:
1.) Use a XLST transform to change the generated wxs
2.) Use -var to specify a preprocessor variable (such as var.MySource) and
specify the value for MySource on the command line to candle.exe (see the -d
switch)
3.) Specify a base path when calling light.exe (see the -b s
Hi:
I have the following component:
I get an ice 18 when building this, the component is under a directory element
as follows:
Can I ignore this error, ideally I don't want to!
I thought as I was using CopyFile, this would
I am trying to get a node value from SelectSingleNode() by passing a xpath
query but keep getting null.
XmlDocument doc = new XmlDocument();
doc.Load(@"c:\temp\MySource.wxs");
XmlElement root = doc.DocumentElement;
root.SelectSingleNode("produ...@manufacturer]"); returns null
Can som
There's a lot that could go wrong here.
Start with this:
http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101
What's your exact command complete command line? Are you using
REINSTALL=
It's likely that it's not being removed because the sharing rules are broken
(component guids)
-=-=-=-
error:
The DirectoryRef/@Id of attributes value,
'Application.managementserver.plugins.authentication.native.client.symbo
ls' is too long for an identifier, standard identifiers are 72
characters or less.
-=-=-=-
The in the above text-cut is 73 characters long, this is
what needs to b
Bump.
Does Silence imply that I am stuck with these warnings during my build? Is
there more info that I can provide? Should I open a bug?
John
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Monday, December 06, 2010 4:48 PM
To: General disc
Hi,
The IIS schema allows me to install a new website and reference an existing
application pool the user specifies. But I want the setup to fail with a
meaningful error message if that app pool does not exist. Similarly I
require a specific user to be present. I'm not sure what condition to us
Hi
I've just come across a few bugs in the wix-ui localization files that
were preventing me building various cultures. The bugs are all simple to
fix, mostly just typos. I've added them to the bug tracker on sf, with
instructions on how to fix. I would submit patches but don't know how...
(any
Thanks Tobias, works a treat!
Sean.
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 09 December 2010 12:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] installing a feature but not showing in feature tree
Display="hidden":
Pl
Display="hidden":
Please also check http://wix.sourceforge.net/manual-wix3/wix_xsd_feature.htm
2010/12/9 Sean Farrow :
> Hi:
> I need to install a feature but I don't want the user to be able to disable
> the feature from being installed. Is this possible?
> Any help appreciated.
> Cheers
> Se
Think you mean the title in the summary information stream (Context
menu on MSI -> Properties -> Details -> Title). This cannot be set
within Wix as there is no corresponding Package Element attribute.
Also check
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Summary-Information-Stre
Hi:
I need to install a feature but I don't want the user to be able to disable the
feature from being installed. Is this possible?
Any help appreciated.
Cheers
Sean.
--
This SF Dev2Dev email is sponsored by:
WikiLeaks T
Am a little impressed about that and that even registry writing from
one package to native HKLM is possible on x86 and x64.:
In that case I get 2 ICE80 errors.
... error LGHT0204 : ICE80: This package contains 64 bit component
'Reg1' but the Template Summary P
25 matches
Mail list logo
