What's the opinion on leaving files/directories behind on uninstall?
Applications write files/directories the installer doesn't know about,
especially user specific ones. But the installer doesn't know about the
files/directories created.
What's the best way to go about cleaning them? Enumerating
Thank you both.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dialog-templates-tp7322083p7324579.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Keep Y
On 27-Feb-12 15:57, David L. Beckwith wrote:
> MyBA.exe WIN8=1
>
> and
>
>
>
> How do I get it into Value?
The command line is passed to the BA in the command
(BOOTSTRAPPER_COMMAND.wzCommandLine in C++).
--
sig://boB
http://joyofsetup.com/
-
On 27-Feb-12 11:29, Rob Mensching wrote:
> I am not a lawyer so my comments cannot provide you legal advice but my
> legally uneducated understanding of the license is that the output of the
> tools is not OSS.
Of course, any use of a WiX extension or Burn includes code licensed
under the CPL...
On 27-Feb-12 10:50, victorwhiskey wrote:
> So is there a way I can define the font size and color for
> title/subtitle/description...? and have all dialogs use that?
No, but you can use TextStyle to change font size and color.
--
sig://boB
http://joyofsetup.com/
On 17-Feb-12 05:07, Tobias S wrote:
> d) Is there a bug or is it not completely implemented ?
Yes, there are bugs, already filed.
--
sig://boB
http://joyofsetup.com/
--
Keep Your Developer Skills Current with LearnDevNo
I suspect a LoadUserProfile is done for the user in question. That's what
contains those kinds of paths etc.
Phil W
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent: Wednesday, February 22, 2012 11:04 AM
To: General discussion for Windows Installer XML toolset.
S
6.1.98.16 was a security update, and I don't believe new merge modules were
ever supplied.
The Windows Installer default file replacement rules mean that 6.0.88.4 should
never replace a 6.1.98.16. I suspect that something non-standard is going on.
You're not updating with a REINSTALLMODE speci
Thanks for the response, and the info in there is useful, but
unfortunately, I'm not using MSBuild for this project for various reasons.
However, that was enough for me to find the documentation for Insignia,
which seems to be what I need.
Thanks!
On Mon, Feb 27, 2012 at 3:11 PM, Roee Shenberg w
Tried that with no luck.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-command-line-parameters-tp7323306p7323422.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi David,
Have you tried changing the value into a variable instead of static value?
Cheers,
Romeo
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-command-line-parameters-tp7323306p7323393.html
Sent from the wix-users mailing list archive at
Hi Roee,
Please have a look at these thread. There's a MSBuild task that you can
override to sign the bundle and engine (assuming you're using MSBuild for
your projects).
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Signing-the-burn-bootstrapper-tp7174715p7179602.html
Regards,
R
I think I understand that standard command line parameters that MSI support
are automatically passed to each package in the bootstrap application. And
it sounds like others can be passed but I need to specifically add it to the
MsiProperty. However, I'm not clear how to do this.
Here is my example
You'd be way better off using a chainer. That being said, you're probably
going to have to conditional the second install on the install states of a
feature(s) or component(s) and create your own "Installed_Second" property to
effectively mimic the behavior of "Installed."
You're going to hate
Contrary to norm, I have implemented a concurrent installation scenario where
one second install, user will go through my custom install dialogs. One last
leg, I present them with "Install" button, which simulates what
"VerifyReadyDlg" dialog's custom install option would do.
Nothing built into the WiX toolset, no. I thougth about user controls as
well a long time ago.
I'm personally moving away from MSI UI because it is so limited and using
Burn instead.
On Mon, Feb 27, 2012 at 7:50 AM, victorwhiskey wrote:
> Hi,
>
> I've done some searching ("Googling") and searchin
I am not a lawyer so my comments cannot provide you legal advice but my
legally uneducated understanding of the license is that the output of the
tools is not OSS.
Our *intention* is that if you change the code in our repository, that
needs to be released (back to us hopefully). If you create your
I'd suggest that your boss talk to his own retained or internal counsel.
It's prima facie case to me that the license of a compiler doesn't transfer
to the built object code format of your IP. However, I'm not in the
business, nor do I imagine the WiX team is in the business, of giving legal
Hello every one and WiX Team,
my boss want's to know the following regarding the CPL WiX is lecensed under:
Are outputs of WiX tools, e.g. msi files, under CPL or another OSS license?
I for myself believe not, but my boss likes to get a statement from the WiX
team, so please answer my question.
Hi,
I've done some searching ("Googling") and searching in this forum, but
haven't found much help. I was wondering if there's a way to create dialog
templates? I'd like to have my dialogs use certain font size and color or
all dialogs that MAY come up. Many times I would have to create a dialo
20 matches
Mail list logo
