Hi
I'm trying to create hyperlinks on a dialog. From what I can see there is no
native support for a Hyperlink. I have two questions:
1. How would I declare a button or any other element to emulate a
Hyperlink?
2. How do I make the OnClick or equivalent launch the hyperlink?
Hi,
I want my wix based installer to run on windows 2000, XP, and Vista. It
should offer a per-user and per-machine installation. Now I read in a
previous task an answer from Bob Arnson that it's not possible under
Windows Vista to request elevation at run time. But my first tests on a
vista
Ok, I just read further and it seems that the behaviour is related to
the setting of the ALLUSERS property. I is explained in detail in
http://msdn.microsoft.com/en-us/library/aa371865(VS.85).aspx
Cheers Volker
Volker Enderlein wrote:
Hi,
I want my wix based installer to run on windows
Hi, I'm fairly new so forgive me if this is an easy one.
I want to use ScheduleReboot but only on uninstallation.
I've tried ScheduleReboot After=MsiUnpublishAssemblies / but this occurs
on install also.
Thanks
--
View this message in context:
Hi
I'm trying to create hyperlinks on a dialog. From what I can see there is no
native support for a Hyperlink. I have two questions:
1. How do I declare a button (or any other element) to emulate a hyperlink?
2. How do I make the OnClick of the button (or equivalent) to launch the
link?
I'm
Hi,
thanks for your answers. I'm new to installer development. Could you
explain the bootstrapper idea a little further?
Andreas Hellwig
Christopher Painter schrieb:
But you could write a bootstrapper that caches and tweaks the package based
on user input before calling into the
Well I can not find any example for this
assume two properties (containing pathes)
So let's ahve PROP1 = c:\foo
if it is set then
ANOTHER_PROP = PROP one can do that with
Property ... value=[PROP1]
But when this is not set then it should look for PROP2
if PROP2 is set then this value should
As per Rob's suggestion, here's a letter to the SQL team RE: the SQL
Express installer.
-
Dear SQL Server Team:
SQL Server 2005 Express Edition has become a platform that many
developers have come to count on in building applications. It provides a
flexible, redistributable database
YAHOO.Shortcuts.hasSensitiveText = true;
YAHOO.Shortcuts.sensitivityType = [adult];
YAHOO.Shortcuts.doUlt = false;
YAHOO.Shortcuts.location = us;
YAHOO.Shortcuts.document_id = 0;
YAHOO.Shortcuts.document_type = ;
YAHOO.Shortcuts.document_title = Re: [WiX-users] Proposed adjustments the WiX
v2
On Wed, Jun 11, 2008 at 5:49 PM, Rob Mensching
[EMAIL PROTECTED] wrote:
Interesting, didn't know the SiteId was used in farm settings. Leave to the
IIS team to take something that had no meaning and assign meaning to it
later. sigh/
I did some poking around and found the following
Please reply to wix-users. As you saw, you can't embed a RegistrySearch
element in a CustomAction element. What I meant was to write a custom
action to do the registry search, rather than using the built-in
support. The easiest way to do this is some procedural C++ code. Using
the After
Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
PROP1 exists. Something like
CustomAction Id=SetANOTHER_PROP Property=ANOTHER_PROP
Value=[PROP1]/
Custom Action=SetANOTHER_PROPPROP1/Custom
You can do the same thing for PROP2 or set PROP2 as the default value of
ANOTHER_PROP
And BTW thanks for mentioning the deployment engineering blog. I never came
across that, but just subscribed to it.
On Tue, Jun 10, 2008 at 7:02 PM, Christopher Painter [EMAIL PROTECTED]
wrote:
But you could write a bootstrapper that caches and tweaks the package based
on user input before
andywhitt wrote:
I want to use ScheduleReboot but only on uninstallation.
I've tried ScheduleReboot After=MsiUnpublishAssemblies / but this occurs
on install also.
Put a condition in the ScheduleReboot text node; see Examples of
Conditional Statement Syntax in the MSI SDK for how to
aprameya rao wrote:
1. How do I declare a button (or any other element) to emulate a hyperlink?
Use a plain button. There's no visual approximation for a link.
2. How do I make the OnClick of the button (or equivalent) to launch the
link?
Use a DoAction control event using the
Volker Enderlein wrote:
this way). The installer is started without elevation and defaults to an
per-user installation. Later the user/admin can change the preselection
in the GUI to an per-machine installation. And if he presses the install
button Vista UAC prompts for elevation.
All I do
You could havenbsp;bootstrapper that's manifested to require Administrator.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Thu, 6/12/08, Bob Arnson lt;[EMAIL PROTECTED]gt; wrote:
I appreciate the feedback and I hope you find the content useful.
nbsp;
Regards,
Chris
--- On Thu, 6/12/08, Chris Mumford lt;[EMAIL PROTECTED]gt; wrote:
From: Chris Mumford lt;[EMAIL PROTECTED]gt;
Subject: Re: [WiX-users] Vista: per-user installation without administrator
privileges
To: General
Christopher Painter wrote:
You could havenbsp;bootstrapper that's manifested to require Administrator.
Bootstrappers shouldn't be admin-manifested. They should be
asInvoker-manifested and elevate when the user commits to the
installation. Otherwise the user has no details about what will
If I try to compile that, it tells me the CustomAction element
contains illegal inner text. :(
Tim
On Thu, Jun 12, 2008 at 11:08 AM, Brian Simoneau
[EMAIL PROTECTED] wrote:
Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
PROP1 exists. Something like
CustomAction
Wix 3.0.4123 + VS2005
Hello,
I am working on an installer which writes values to a key within HKLM.
It works fine if there is no existing registry key, but fails when it
tries to overwrite existing values. I get the error message:
Could not write value Enabled to key
Oops, nevermind. The condition goes inside the Custom element in the
install sequence, not in the CustomAction element.
Tim
On Thu, Jun 12, 2008 at 11:50 AM, Tim Fisher [EMAIL PROTECTED] wrote:
If I try to compile that, it tells me the CustomAction element
contains illegal inner text. :(
Tim
I have raised a bug:
http://sourceforge.net/tracker/index.php?func=detailaid=1992202group_i
d=105970atid=642714 and included the information from this thread in
it.
Personally I think this is something that would need to be fix for v3
release but I do write a lot of website installs!
Neil
I'm very new to working with Installs but have some managed code that I'd
like to use as Custom Actions. I'd like to try out using DTF with C# but
not finding much in documentation with examples..so I'm just having to trial
and error it. Hoping that someone may know of a good site.
Currently
Does anyone know why mixed-case guids generate and error from candle if
you turn on the -pendantic flag? Is it just a coding style or is there a
problem with them? (It looks like candle forces them uppercase in the
wixobj file.)
Setup.wxs(31) : error CNDL0087 : The Upgrade/@Id attribute's
I'm very new to working with Installs but have some managed code that I'd
like to use as Custom Actions.
First, I should warn you that writing custom actions is not something that
should be done by someone unfamiliar with Windows Installer technology. Even
though DTF makes the task more
This is a quote from Heath Stewart when I asked the same question...
Upper case is required because of the compression translation matrix MSI
uses internally in some places. Characters have different ordinals which
yield different results under said matrix.
Hope that helps,
--
Brian
Does Votive do the actual conversion or is it candle.exe?
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Shevchuk
Sent: Thursday, June 12, 2008 12:07 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Candle upper-cases the guids for you. But many other MSI tools and APIs don't,
so one could make a pedantic argument that it's better to have them upper-case
in the source code for better copy-pasting.
-Jason-
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Well, it is Windows Installer. :-)
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Thu, 6/12/08, Neil Enns [EMAIL PROTECTED] wrote:
From: Neil Enns [EMAIL PROTECTED]
Subject: Re:
Hi,
Some background: I'm trying to replace a legacy builder tool. The old
builder tool compiled hundreds of vbp project files. Some ActiveX, some
Exes, some Com+. The compilation was successful in NAnt. I also have
created a WiX file that currently installs the UI DLLs and Exe and it works
As uppercase guids are important shouldn't wixcop fix them? Is that a
feature request?
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason
Ginchereau
Sent: 12 June 2008 20:46
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Thanks for the response! I'm currently reading through the site you sent.
I've been tasked with making a couple installs with Installshield. I'm a C#
developer so I've made the custom actions in C#. That's all complete and
working now. Problem is that I'm not getting feedback from my custom
In my opinion, the biggest current issue is the fact that you still have to
have a bootstrapper to install MSI 4.5 before you can start your MSI, followed
by a lack of desire to take on distributing MSI 4.5 for those of us deploying
over the internet.
The fact that almost no one knows about
On attempting to install Wix 3.0.2925 I receive an error message Votive,
the WiX project and editor package for Visual Studio cannot be installed
because Visual Studio Standard Edition or higher is not installed. When I
acknowledge that message it appears that WiX is installed.
I have Visual
CopyFile element should be able to do that.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laplante, Patrick
Sent: Wednesday, June 11, 2008 18:23
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] same file, multiple destination folder
Hi, is it
I created a new wxs file with a Fragment in it, then I moved my SqlDatabase
element over into the Fragment element like this:
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:sql=http://schemas.microsoft.com/wix/SqlExtension;
Fragment
sql:SqlDatabase Id=DB1
Howdy, folks. I've been trying to keep up with the evolution of 3 in the
weeklies, and so far none of the breaks have been too painful, but I don't
understand what to do to remediate this one from Visual Studio 2008:
The Product element contains an unhandled extension element 'sql:SqlDatabase'.
Votive generates Product ID and UpgradeCode GUIDs which, from the Windows
Installer point, are wrong.
That may not be an issue if we assume that nobody will enhance msi files
manually or using Windows Installer API and using GUID from Votive-generated
template. I'd rather see a warning from
Did you add a reference to the SqlExtensions? Right click on the References
node in solution explorer and in the resulting dialog add WixSqlExtensions.dll.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Reed (SQL)
Sent: Thursday, June 12,
Hrm. Didn't have to do that with earlier weeklies, providing the commandline
args in the project properties was previously sufficient (-ext WixUIExtension
-ext WixSqlExtension). I guess adding a reference would the intuitive developer
task; time to wake up my VS reflexes. Duh.
FWIW, I had to
Brian Simoneau [EMAIL PROTECTED] writes:
Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
PROP1 exists. Something like
CustomAction Id=SetANOTHER_PROP Property=ANOTHER_PROP
Value=[PROP1]/
Custom Action=SetANOTHER_PROPPROP1/Custom
You can do the same thing for PROP2 or
3.0.2925 is way old, from before VS 2008 was released. Use a newer version
from http://wix.sf.net/releases/ and it will work
regards,
Simon
On Fri, Jun 13, 2008 at 12:44 AM, Mark Stega [EMAIL PROTECTED]
wrote:
On attempting to install Wix 3.0.2925 I receive an error message Votive,
the WiX
43 matches
Mail list logo
