Lack of welcome page is what I find retrograde. I guess it is personal opinion,
I am quite happy with both the welcome and licence dialogs - it is what other
installs do so I prefer not to show my users something different. Jumping
straight to licence just looks odd as I haven't seen it before
Use a RegistrySearch to find some well-known key or value installed by
.NET 4.0. That's pretty much all the NetFxExtension properties do.
On the subject of v3.5, Microsoft themselves have been using it to ship
retail products such as Visual Studio 2010 long before it was even
upgraded to release
Does anyone know what happened to the microsoft.public.platformsdk.msi forum?
It used to be a
newsgroup but then Microsoft started changing all their newsgroups to
discussion groups. It used to
be here at
Hi,
We have been following the scheme that Rob is suggesting for a few
years, I think in our main product we are down to two dialogue in most
scenarios.
We have a welcome/license page and then a ready to install page.
I have noticed other applications doing this too, Visual studio setup
has lots
I agree with Neil. The welcome page is very useful for informing the
user what they're actually installing before they are faced with things
license agreements or even Install buttons (with possible UAC elevation
shield). It's clean, uncluttered gets the information across to the
user without
Hi,
From my point of view the concept to kick the Welcome dialog is ok if
there is no additional information than on the default dialog sets.
Usability clearly says if something doesn't provide additional
information kick it. And (IMO) the Welcome dialog is one of these
dialogs as there is not
Hi all,
I need to delete a specific file (created by our product) after
uninstalling the product. For that I'm using the Quiet Execution
CustomAction like:
Property Id=QtExecDeferred Value='[SystemFolder]\Cmd.exe /C del /Q
[INSTALLLOCATION]\momo.txt'/
CustomAction Id=QtExecDeferred
Use the RemoveFile element instead.
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 29 November 2010 13:45
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] QtExecDeferred and using a property in the cmd line
Hi all,
I need to delete
Hi Peter.
Thx for your answer, but I can't do that because I need the files to be
removed _only_ when uninstall (not updates) and I have
RemoveExistingProducts After=InstallInitialize/. And as I described
here:
Hi Michael,
Thanks for your answer.
Because of this, the premise that a component condition can prevent
the RemoveFile table entry from executing during uninstall is flawed,
I wouldn't have expected that, because of:
1) The code works as expected when I have REP after installFinalize,
I don't have the answer to this question but I have also tried to find ways
in the past to send feedback to the Windows Installer team.
Why is there no way to report bugs or suggest enhancements? I know that
there is a (rarely updated)Windows Installer blog but why nothing official
(think
The trick here is that in the working case, the component is never
uninstalled. With REP after InstallFinalize, the new install
increments the component's reference count, possibly installing
updated contents. Then REP uninstalls the earlier version, which
merely decrements this component's
I see why you need a custom action. Your best approach is to have your
custom action write temporary rows to the RemoveFile table and let
Windows Installer do the deleting for you. That would prevent some
potential problems.
The pattern for these types of CAs is described in Bob's well-thumbed
I have a need to allocate a 64K size in a property value for storage. This is
to keep feature compatibility with a previous Wise Installer.
What is the best way to do that in WiX or is it possible with WiX?
If allocating 64K size of storage is not possible, is there another alternative
doing
Hi,
We are currently using WIX 2 to build our MSI files. We are merging in the vc80
merge modules, apparently successfully. (Stuff runs :-)
While trying to upgrade to WIX 3, I noticed that the MSI files it produces are
a few megs bigger than the ones produced by WIX 2. But more critically, the
Hi,
I think that since the installation will run only once or so, the extra click
on Next should be not a problem to most users.
The fact that the installation behaves differently is more of an issue, this
will generate some additional stress to our helpdesk I fear.
I think that the entire
Hi:
That's what I'm in the process of doing for a very similar situation.
I'll post code when finished, should be a couple of days.
Cheers
Sean.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 29 November 2010 15:05
To: General discussion for Windows
v8.0.50727.762 of the VC++ 8.0 libraries is ancient (VS2005 SP1). Are
your binaries definitely built against that version of the VC++
libraries as the ATL security fix (which is in essence a stealth SP2 for
VS2005) released in July last year updates them to v8.0.50727.4053.
That'd be the first
We made modifications to the util:PermissionEx element (based upon code
by Cody Cutrer) in order to accomplish this:
CreateFolder util:InheritDacl=no
util:PermissionEx User=[USER] Domain=[DOMAIN] Type=allow
ApplyToSelf=yes ApplyToSubfolders=yes ApplyToFiles=no Read=yes
ReadAttributes=yes
On 29 Nov 2010, at 15:54, Pally Sandher wrote:
v8.0.50727.762 of the VC++ 8.0 libraries is ancient (VS2005 SP1). Are
your binaries definitely built against that version of the VC++
libraries as the ATL security fix (which is in essence a stealth SP2 for
VS2005) released in July last year
Sorry for the slow response...
Yes, it seems that was the dumb thing I'd done to myself. The annoying thing is
I thought I had tried setting mutually exclusive conditions without success,
but it worked fine today.
Thanks also to Palbinder Sandher who gave the same information.
Regards,
It's too bad that RemoveFile won't work, since it does provide
appropriate transacted functionality; that said, the answer to using
properties within the command line is to use a custom action to set the
property value:
CustomAction Id=SetAspNet20_Cmd Property=SetAspNet20
I'd have to agree that this change in functionality should be optional.
As it stands upgrading to 3.5 has changed the way it worked and I now
have to sell that change to my users rather than it being transparent
(or of course replace the UI with the old one but that involves coding
and testing).
This may be an issue with the SxS and policies depending on your OS. Some
people install the redist with the vcredist exe which also installs publisher
policy that redirects everyone up to the newly installed libraries. Some people
install with the VC merge modules and (somewhat randomly)
This works great, thanks.
I have a related followup question, but will post it in another email (in order
to avoid getting off topic).
Thanks,
Bob
From: Blair [os...@live.com]
Sent: Wednesday, November 24, 2010 10:03 PM
To: 'General discussion for
Perhaps this question has been answered before, but I couldn't find
anything in the wix-users archive.
I found a problem where when we do a major update when a component in
the newer version has a key file with an older version than the version
its updating. The problem is that the component
Just an update on this. I tried changing the Component GUID, but
realized that that won't work, because the files still target the same
location, so I get the same error. That is, it's not looking up the
Component GUID for determining if the component is pre-existing, but
rather the destination
When you start the installation of WiX's EULA license file, the initial screen
displaying the eula.rft is blank, unless you
press the scroll bar.
This issue is found in the WiX 3.5 RC candidate version( 3.5.2229.0).
Thanks!
Is this in the GAC? Sounds like that upgrade GAC problem.
http://support.microsoft.com/kb/905238
Phil Wilson
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com]
Sent: Monday, November 29, 2010 11:20 AM
To: General discussion for Windows Installer XML toolset.
On Mon, 29 Nov 2010 11:58:30 -0800 (PST)
Brian Pang bria...@yahoo.com wrote:
When you start the installation of WiX's EULA license file, the
initial screen displaying the eula.rft is blank, unless you
press the scroll bar.
This issue is found in the WiX 3.5 RC candidate version(
No this isn't anything in the GAC. The component in question is a piece
of a driver installed using the DifxAppExtension, and its absence wreaks
havoc on the attempt to install the driver, failing the major update.
However, the problem itself occurs prior to this, in that very early on
the
Hi,
Can someone share an example or directions to display directory selection
dialog using the browsedialog?
The code below does not work
Control Id=Browse Type=PushButton X=20 Y=252 Width=50
Height=17 Property=ANSWERSDIR Text=Browse
Publish Property=ANSWERSDIR
Hello,
I am getting the following error when using the installer built using WiX:
Error 1324. The folder path '?' contains an invalid character.
The following is some of the text from the log file when using the installer.
MSI (c) (3C:E8) [13:37:21:690]: PROPERTY CHANGE: Modifying
Hi,
A couple questions, both regarding DIFxApp. (We use it to install three
drivers for three plug-and-play USB devices for a hardware product that we
ship.)
1. Some time ago Rob Mensching mentioned the following on this list:
Yeah, there are some design issues in the DIFxApp code around
Hi,
A couple questions, both regarding DIFxApp. (We use it to install three
drivers for three plug-and-play USB devices for a hardware product that we
ship.)
1. Some time ago Rob Mensching mentioned the following on this list:
Yeah, there are some design issues in the DIFxApp code around
1. We see the exact same problems with DIFxApp on major upgrades (which
is the only type of upgrade we do). I would love to be able to track
down the cause and have a better solution. If anyone has anything
approaching a solution, please let us know! I realize that this issue is
probably
Dev Environment: VS 2010, Win XP
Prod Environment: Either XP or Win7
I need to know how to create a shortcut in the SendToFolder. This is
user-specific, and there is no All Users SendToFolder in Windows. But I
will settle for the current user's SendToFolder.
~ Shaun
In the Seattle area
Dev Environment: VS 2010, Win XP
Prod Environment: Either XP or Win7
I need to know how to create a shortcut in the SendToFolder. This is
user-specific, and there is no All Users SendToFolder in Windows. But I
will settle for the current user's SendToFolder.
~ Shaun
In the Seattle area
Hi,
I've done a lot of web search regarding the issue where the program size being
displayed in Programs and Features dialog box doesn't match up with what is
actually being installed (especially when your install takes more than 4 Gig
and dialog box will only show the remainder of the 4 Gig).
On 26-Nov-10 06:31, Rob Hamflett wrote:
Slight typo. This was meant to say It would be nice to know what I can
expect to happen if costing
*hasn't* completed yet
AFAICT, costing completed; only the property wasn't updated.
--
sig://boB
http://joyofsetup.com/
G'day All,
I am trying to display a MessageBox only if a feature has been selected and
only if IIS 6 Compatability is NOT turned on on a machine with IIS 7 enabled
(as the Feature needs IIS 6). This MesageBox should be displayed if the
conditions are met for it to be displayed when the Next
On 29-Nov-10 12:04, Neil Sleightholm wrote:
I'd have to agree that this change in functionality should be optional.
As it stands upgrading to 3.5 has changed the way it worked and I now
What change? WiX has used the WixUI_Advanced set (which combines the
welcome and license pages on clean
Hi,
I am currently using WIX 3.0 with VS 2008. We need to upgrade our application
to Visual Studio 2010. Can anyone provide me the WIX version supported by
Visual Studio 2010. I found somewhere on internet to use WIX 3.5.1623.0 for VS
2010 but I am not able to find the same version on
You don't have to find a special build of WiX 3.5. Just pick the latest one,
which is now an escrow release:
http://robmensching.com/blog/posts/2010/11/25/WiX-v3.5-now-escrow.-Production-release-imminent
If you run the install on a clean machine then the welcome page is
displayed during the initial page and then it jumps straight to the
licence page. I have to admit I can't see the code that does this but I
am not the only one to see this. I have seen this with the WiX 3.5
install and
WiX 3.5 introduces the Component/@Feature attribute
(http://www.joyofsetup.com/2007/12/07/simplifying-the-wix-v3-language/)
which should make it much simpler to include components as you only need
to write code for the components and can potentially skip the
ComponentGroup part but I am
46 matches
Mail list logo
