Hello,
We need help with the following scenario: we use a BrowseDlg to allow the
user to select the installation path. On this dialog, if the following
sequence is executed, an invalid error message appears.
Sequence:
- Open the BrowseDlg
- Type the letter of a disk that
I've found out that this behavior is by design (see
http://msdn.microsoft.com/en-us/library/aa370749.aspx for information about
the PathEdit control).
The solution is to implement a custom Browse for Folder dialog.
-Original Message-
From: Dan Vasilov [mailto:d...@rms.ro]
Sent: Friday,
Hi,
I am creating a patch for my installer. I have my base version
installer and new installer. when I try to create patch, It fails(logs
attached).
Does anybody have any idea ?
Thanks Regards,
Sanjay Rao
ÿþ
* * * * * L o g s t a r t i n g : 2 0 1 0 - 0 7 - 0 9 1 3 : 1 7 : 1 9
As the message suggests, PatchWiz cant create a patch when the files are
compressed. You could perform an adminstrative installation of the base
and target MSIs and run PatchWiz on those instead of the MSIs.
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent:
Hi,
I am running following custom action which runs /RegServer command.
File Id='distributeserver' Name=DISTRIBUTESERVERFILE src=f:\Program
Files\Ambit ALM 6\ALMEngine\distributionserver.exe
/
CustomAction Id='DISTRIBUTESERVERCUSTOMACTION'
FileKey='distributeserver'
Hi all,
I'm struggling with the task to apply security settings to a registry key.
What I want to achieve is setting full access to Everyone for a registry
key, and I want this being inherited. Unfortunately I only get as far as
setting the full access right for Everyone on the key, but it
Hi,
We deliver our WIX created setup packages with predefined install locations by
setting the INSTALLDIR property in advance. One of our customers requires
installations to be done on the D:\ drive, so we have preset the install
location to D:\.
However, if somebody tries to install this
Hi,
I removed the license dialog from the WixUI_InstallDir.
but when i am running the installer i am getting the following error :
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2819.
below is the
My colleague had this same problem.
If you have a limited number of keys that are known at install time, you
can add them all explicitly and set permissions on them.
Since we wanted the permissions to cascade down to keys created by the
application and we were short of time, we used wix's qtexec
Hi yaan,
thnx for you suggestion. But I did that. Then the compilation is giving the
error as follows.
Error 3 The iis:WebAppPool/@Identity attribute cannot be specified unless
the element has a Component as an ancestor. A iis:WebAppPool that does not
have a Component ancestor is not
That's exactly the problem. The permission must be inherited to keys created
later by the application.
I already have the code to put in a custom action but I try to use built-in
functionality as much as possible. So I would prefer if there was a way to
do it natively with Windows Installer or
Not sure if this helps but I posted an example of doing this here:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Neil
-Original Message-
From: subrat agasti [mailto:subrat.w...@gmail.com]
Sent: 09 July 2010 12:25
To: wix-users@lists.sourceforge.net
Subject:
Sadly, you cant do it. Yan found the specific bit of code that causes
this problem so if you are prepared to recompile wix yourself, you could
make the fix.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registry-P
ermissions-td2939332.html#a2939332
-Original Message-
Or use the WiX v3.0+ tools instead which are far more powerful than
patchwiz.
On Fri, Jul 9, 2010 at 1:29 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
As the message suggests, PatchWiz cant create a patch when the files are
compressed. You could perform an adminstrative installation of the
You should be able to start at the torch step if you have (and you really
should keep these) the MSIs and .wixpdbs from the different builds you want
to patch.
--
virtually, Rob Mensching - http://RobMensching.com LLC
On Thu, Jul 8, 2010 at 8:42 AM, Coates, Anthony
Peter --
thanks for pointing that out. Obviously with this information I could fix
the behavior by patching the WiX sources and building my own binaries. But
looking at the current head of the 3.5 development I see the same code there
as in 3.0. So I guess it is not planned to change the
Hello,
just set MigrateFeatures=yes in your UpgradeVersion element.
http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm
Andreas Hirth
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Thursday, July 08, 2010 2:45 PM
To: General
Hello wix users!
I have the following UI setup:
!-- Use the built in WixUI_InstallDir GUI --
UIRef Id=WixUI_InstallDir /
UI
!-- These dialog references are needed for CloseApplication above to
work correctly --
DialogRef Id=FilesInUse /
DialogRef Id=MsiRMFilesInUse
Windows Installer doesn't support logging the console output of command you
execute through a custom action.
Consider using CAQuietExec to execute your custom action. That will do two
things for you:
1.) Hide the command prompt window that shows up for console applications.
2.) Capture your
The limit of 16 is somewhat arbitrary. The way the build process works, a fixed
number of entrypoints must be reserved at compile time in the sfxca.dll
unmanaged stub for managed CAs. The limit can be increased by changing the
sfxca.dll source code and rebuilding. The entrypoint reservations
Thanks for the assistance to date, it's appreciated.
I'm at a point now where I've created a custom action DLL using a .NET
class library that I invoke as follows:
CustomAction Id=CreateDirs BinaryKey=CREATE_DIRS
DllEntry=CreateDirectories Execute=immediate Return=check /
Binary Id=CREATE_DIRS
No problem.
I'll throw in the EntryPoints.h/.def added entrypoints code I already did so
the fix is as close to cut and paste as possible.
Rob.
From: jason...@microsoft.com
To: wix-users@lists.sourceforge.net
Date: Fri, 9 Jul 2010 21:42:50 +
Subject: Re: [WiX-users] DTF
Hi;
What's the easiest way to have WIX perform COM registration of a DLL?
Preferably a way where we don't have to update the file's version numbers.
??? - thanks - dave
--
This SF.net email is sponsored by Sprint
What
Use the heat tool?
-Original Message-
From: David Thielen [mailto:da...@windward.net]
Sent: Friday, July 09, 2010 4:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] COM registration of a DLL
Hi;
What's the easiest way to have WIX perform COM registration of a DLL?
That sets the version number so we then have to update for every build. I'd
prefer to avoid that. Isn't there an attribute to the file command that tells
the system to register it?
thanks - dave
From: Blair [os...@live.com]
Sent: Friday, July 09, 2010
Hi,
Thanks for reply. Actually I want to register our com exe. We are using heat to
create the .wxs file. It contains the information about class and interface ids
but still it is not registering. We want to see our COM exes into dcomcnfg. Our
COM exes only showing in dcomcinfg after using
hi Sunkesula, Srivardhan,
how your question is merged in to my query? is there any problem ?
srinivas
--
View this message in context:
Hi ,
how these 2 problems merged? My problem is not solved?
Any one can answer to my question please?
srinivas
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/webapppool-to-my-virtual-directory-tp5242027p5276993.html
Sent from the wix-users
28 matches
Mail list logo
