Just FYI: the feature request has been filed, # 2544928
-- Yan
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Wednesday, January 28, 2009 7:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Features of XmlConfig -
Thanks for a hint, Rob! I had something similar in my mind.
-- Yan
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Wednesday, January 28, 2009 7:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where to store SQL
Unsubscribe
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
Isn't it what the ContinueOnError attribute is there for? I have
searched through this mail archive and I can see that people often put
ContinueOnError=yes for uninstall SQL strings. This sounds quite
logical: don't interrupt the uninstall, and let the admin to manually
drop the broken references
Dear all,
attached you can find the verbose log and a screenshot of the message box. Full
string of drop down box Use source: is
C:\DOKUME~1\UWE~1.STU\LOKALE~1\Temp\\{CAF30021-1370-494F-B1AE-071885DADBEC}\.
The message box appears at: 09:17:44:437 (related to the log file).
I have clicked
Hello all
Right now I am using a language bootstrapper and applying localization
transforms using
msiexec /i msiname /qf TRANSFORMS=:de_DE.mst according to the language
selection the user has made.
I want to get rid of the language bootstrapper and want the MSI auto detect
User locale on the
hi
i am new to WIX,
i am reffering Wix Totorial meant for 2.0
colud you please tell me how go Wix ui step by step
creating dialog and ui liberaray.
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge
cheers rob,
got it sorted in the end
FYI this is my custom protocol handler:
RegistryKey Id=regCaseFlowKey Action=createAndRemoveOnUninstall
Key=nameofmyprotocol Root=HKCR
RegistryValue Id=DefaultValue Action=write Value=URL:my
custom protocoll Type=string /
HI,
When I set a property to true or false and set it to a check Box it is
taking true. If I retrieve the value for the property the value is 0
if false and 1 if true.
I'm writing a Config file based on the property. If I'm setting the
value in the Config it is stored as 0 or 1 and not false or
I think this may be a bug in the Wix toolkit (not sure how). We have
several installers that are based on the original beta-exit build of Wix
3.0. Most seem to be exhibiting this behavior. We haven't been able to
identify a common thread between the different installers, except that
this problem
Dear all,
after some research I found a workaround:
I do wrap my msi to an exe file with setupbld now by using the command line
option -msuc (c added). c means enable msi caching. So the whole msi gets
cached in Windows\Installer. On uninstall the msi file will be found by MSI and
the message
On Wed, Jan 28, 2009 at 8:35 PM, Bob Arnson b...@joyofsetup.com wrote:
Jon W wrote:
Has anybody succeeded at creating a transform that adds files?
That's a patch.
So, a patch is an acceptable way to install add-on products? Sounds a
bit unorthodox.
Should I create 3 msi products and
1. It is unorthodox but I think what Bob was saying that if you want a
transform to transform *and* update files it's called a patch.
2. Bootstrapper (aka: chainer) is pretty much how it's done.
-Original Message-
From: Jon W [mailto:know...@gmail.com]
Sent: Thursday, January 29,
I think this is a bug introduced with the large changes to IIS CA recently to
handle UAC/IIS7 better. Can you try an older build and see if the problem
reproduces there? If it does repro with older builds then please open a bug
with as much information as possible (especially the info below).
Anyone have any suggestions on how to debug this? I have checked the SQL
server logs and there is nothing there pertaining to this WiX error.
Thank you in advance for your help with this.
This is the exact error:
Error -2147217900: failed to execute SQL string, error detail: RESTORE
DATABASE is
When I set permission using RegistryPermissions, the existing users
are wiped out and the new user and SYSTEM are being added to the
permissions. How do I retain all the existing permissions and add just
the new user. Also, how to make permissions apply to subkeys also.
Component Id=COMPPerm
Verbose log file is always where I start.
-Original Message-
From: Morris, John - Raleigh [mailto:john.mor...@softprocorp.com]
Sent: Thursday, January 29, 2009 04:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DISABLEROLLBACK not working
I think
Util:PermissionEx merges. Not sure about the subkeys... I forget.
-Original Message-
From: Reddy, Mallikarjun (GWM-CAI) [mailto:mallikarjun_re...@ml.com]
Sent: Thursday, January 29, 2009 08:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Adding permissions using
Not much that is helpful. When I've had really hard SQL issues, I've always
used the SQL profiler to dig through all the calls and find the one that is
failing.
Note: I have seen successful attaches of database files but never tried to do a
restore from backup. I always have issues restoring
This isn't strictly wix related but more a general setup question:
Is anyone aware of a robust check to see that SQL Server (2005, express,
std, or ent) and IIS (6, 7 + compatibility components) are installed?
Any help would be appreciated.
Thanks,
Peter
Hello,
is there a way to integrate a Microsoft SQL Server SSIS package into a Wix
setup? The setup should install the SSIS package and if possible allow to
define some user settings. I'm not sure if I need a Wix custom action to
achieve this (maybe somebody already wrote one), or if there is
Hi,
I wonder if anybody has an idea how to conditionally add a group to a
user that is created during install? I am creating an user to run an IIS
web application (well 5 actually). I need to target different versions
of IIS, and it turns out I need to add the user to different groups for
each
Rob, thanks for the quick reply.
No change in behavior with PermissionEx.
xmlns:util='http://schemas.microsoft.com/wix/Util'
Registry Id=Perm Root=HKLM Key=SOFTWARE\Test Action=append
util:PermissionEx Extended=yes Append=yes Domain=MyDomain
User=MyUser GenericAll=yes /
/Registry
I
I've done restores successfully this way. Profiler will help determine the
call(s) made and more details about why they failed.
Eric, assuming that you're using integrated security, are you sure that your
installer is running elevated at the point where the restore is attempted?
We've since
Been there, done that a few times. It depends on the package, Daniel. How are
the package configurations setup? Environment variables? User registry keys?
XML config files? I've used all three, including manipulating the XML files at
installation time to persist user selections made during
That really surprises me... are you sure you rebuilt and completely
uninstalled/installed (i.e. didn't use cached package)?
-Original Message-
From: Reddy, Mallikarjun (GWM-CAI) [mailto:mallikarjun_re...@ml.com]
Sent: Thursday, January 29, 2009 09:29
To: General discussion for Windows
Hi,
We are not able to update a dll present in gac through patch. I am new to wix.
I want to know which tag/ attribute in the wix controls this behaviour. What’s
the use of ‘AssemblyManifest’ of file and is it some how related to the above
behaviour.
Any link to the documentation will be
The custom actions are type 51. The problem is that the merge modules have
type 51 CA's using properties they expect me to set. They have it authored
properly to be put in the msi before CostInitialize. Instead of going in
before CostInitialize which is at sequence 800, they are merged in as
Yan Sklyarenko wrote:
Isn't it what the ContinueOnError attribute is there for?
Yes or DropOnUninstall=no, as long as you leave a hint for the user
somewhere that there are manual steps needed.
--
sig://boB
http://joyofsetup.com/
Andy2k8 wrote:
I want to get rid of the language bootstrapper and want the MSI auto detect
User locale on the target system and load the respective MSI that is
available on the CD.Would building separate MSIs for different languages
help me achieve that?
MSI doesn't have a supported
Uwe Stump wrote:
I do not know if attachements are allowed. So here is the critical section of
the log file:
...
MSI (s) (0C!4C) [09:17:43:187]: Resolving source.
The critical part is right before: That's where MSI identifies the
resource it needs the source for.
--
sig://boB
Lisa Wright wrote:
I did find a workaround that seems to be working. I'm merging multiple msm's
but have found that if the one I'm trying to work with is first in the list
it gets merged properly and are sequenced in the 700's as they should.
Unfortunately, mergemod.dll has its own
check:
1. the new dll has a new file assembly version?
2. the linker option -fv is set?
On Thu, Jan 29, 2009 at 8:30 PM, Sandeep Prakash
sandeep.prak...@microsoft.com wrote:
Hi,
We are not able to update a dll present in gac through patch. I am new to
wix. I want to know which tag/
To whom it may concern,
I have just upgraded to WiX 3.0.4923 and am witnessing the same issue
installing an IIS website on Server 2003. The web site home directory
is not populating, even though the directory is specified correctly in
the wix script, there are no install errors reported, etc.
Yep, thanks, we have a bug open on this now. I'll make sure Mike is working on
it tonight.
-Original Message-
From: Brantley, Garth [mailto:gbrant...@dejarnette.com]
Sent: Thursday, January 29, 2009 11:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
So I persisted my property value to the registry and use a registry search
in the property to try to retrieve the value.
My issue is 2 fold. One, the property values aren't being populated from the
registry properly on uninstall. It might be that the keys are deleted
(uninstalled) before they get
Thanks David. I got this to work! Seems that putting USE master; in
front of the script did the trick. Which makes complete sense now. So
sending your code helped! I appreciate your time!
Eric
-Original Message-
From: David Reed [mailto:david.r...@microsoft.com]
Sent: Thursday,
Hi Eitan,
I verified the following:
1) Old dll has version 3.8.173.1 and the newer one has 1.8.173.2 . Is it ok to
differ at the fourth place only?
2) We have an internal site http://patchman/wipe which takes old msi and the
modified dlls as input and gives msp and modified msi as output. I
The fourth place (the revision) is generally ignored by MSI.
--
John M. Cooper
-Original Message-
From: Sandeep Prakash [mailto:sandeep.prak...@microsoft.com]
Sent: Thursday, January 29, 2009 2:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Have you tried running the uninstall with logging enabled (msiexec /x
setup.msi /L*vx Setup.log) to see what is going on?
Neil
-Original Message-
From: Peter Oehlert [mailto:poehl...@securityinnovation.com]
Sent: 29 January 2009 22:09
To: 'General discussion for Windows Installer XML
I think that is only true for the MSI version, all parts of file
versions are used.
Neil
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: 29 January 2009 22:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need some
I'm using a WiX custom action to import an RSA key container for
encrypting parts of my config files, which is working fine. However,
I have a concern - in order to import the container, I have to somehow
include the RSAKeyValue XML in the .msi, which effectively means that
anybody with Orca can
There is no Windows Installer feature that encrypts the data inside an MSI.
The MSI features you are talking about 1. Prevent data from being logged to the
log file (Property/@Hidden and CustomAction/@HideTarget) and 2. Enable you to
pass Properties from the UI sequence to the Execute sequence
PS: Data Protection API sounds more suited for what you need.
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Thursday, January 29, 2009 15:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Secure custom
Sandeep Prakash wrote:
2) We have an internal site http://patchman/wipe which takes old msi and the
modified dlls as input and gives msp and modified msi as output. I found the
following in its build log. Are you suggesting to use -f in the case of
light.exe?
No, because that's
Yea, I have the logfile but it's not really indicating to me the failure.
The reg keys get deleted, the property initialization from the reg search
never seems to happen and the database uninstall script uses the hard coded
values from the properties rather than the values from the registry key.
Hi,
In WiX 3.0, is there a way to create a Quick Launch shortcut and Desktop
shortcut based on the user's choice?
I know there is a way to create a checkbox for Launch Applition option:
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
I'm wondering if there is a way to create
For the desktop you can use a standard Windows Installer directory reference
(see the SDK). For quick launch the only way I have found is to use this:
Directory Id=AppDataFolder
Directory Id=Microsoft Name=Microsoft
Directory Id=InternetExplorer Name=Internet Explorer
Sorry for delay with this response, Rob.
I have run a simple test for 3 different builds: 4513, 4805 and 4923. It
works the same way for any.
Actually, the result is the following: the DTC service gets started
automatically once addressed either by IIS extension or by IIS console,
when you try to
49 matches
Mail list logo
