Hello everyone,
Can I use the attribute Win64 in the Component for 32 bit applications?
I read that Win64 attribute is applicable for both 32 and 64 bit.
Thanks and Regards,
Makarand
-
This SF.Net email is
From: Andy2k8 [mailto:[EMAIL PROTECTED]
Is there any property that i can use to detect itanium 64 bit
architecture and abort the installation?
Intel64 - http://msdn.microsoft.com/en-us/library/aa372396(VS.85).aspx
-
Hi.
I have created a installer with a custom dialog appearing after the progress
dialog, just before the exit dialog(I am using the InstallDir dialog set).
The custom dialog contains a checkbox, and I would like to execute a custom
action if the checkbox is checked. But is that possible when the
Hi,
I am setting permissions of a folder, but I would like to preserve the
default permissions and only append a user. The code below remove all
default permisions and set only the user I defined.
How can I set permissions to a folder without removing the default
permissions?
Thanks,
Eitan
1 - Yes it is the correct way but fix your order tags the src tag is
deprecated, use SourceFile instead. If you have one TargetImage your
patch will only update that version nothing else.
2 - This is a mailing list where people voluntarily offer their help.
Sending a bump 40 minutes after
Yes but you will get an ICE80 error when compiling if you set
Win64=yes on a component when your MSI is an x86 build vice-versa.
Why would you want to?
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
Mine is a 32 bit package..so i wonder if i can specify Intel64 in the
TemplateSummary..
Msix64 seems to be a better solution
J. J. Farrell wrote:
From: Andy2k8 [mailto:[EMAIL PROTECTED]
Is there any property that i can use to detect itanium 64 bit
architecture and abort the
It must be possible as all WiXUI have an optional checkbox on the
ExitDialog which runs a ShellExec Custom Action if checked. Have you
looked at using this instead of authoring a separate dialog? In the
documentation look under the How To Guides Section. The page title is
How To: Run the Installed
2008/10/28 Peter Vestergaard [EMAIL PROTECTED]:
Hi.
I have created a installer with a custom dialog appearing after the progress
dialog, just before the exit dialog(I am using the InstallDir dialog set).
The custom dialog contains a checkbox, and I would like to execute a custom
action if the
2008/10/28 Romeo Salayo Jr. [EMAIL PROTECTED]:
My objective was to create a short path of the INSTALLDIR after install files
to be used by other custom action to execute an executable. Your suggestion
will search registry during AppSearch and will not create a short path of
the INSTALLDIR
2008/10/27 cemiles [EMAIL PROTECTED]:
My situation is I want a launch condition to fire off if the product has yet
to be installed (it's a regsearch to look for any other related products).
If the product gets installed, I want to make it so the launch condition
doesn't fire off on
2008/10/28 Eitan Behar [EMAIL PROTECTED]:
Hi,
I am setting permissions of a folder, but I would like to preserve the
default permissions and only append a user. The code below remove all
default permisions and set only the user I defined.
How can I set permissions to a folder without
Just create a Launch Condition with VersionNT64 AND Intel64 as the
inner text.
http://msdn.microsoft.com/en-us/library/aa372497(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa369553(VS.85).aspx
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44
Thanks for your reply.
What do you mean by sequence it. I placed my custom dialog between progress
and exit dialogs.
I follwed Pally's advise and did this:
Publish Dialog=MyExitDialog Control=Finish Event=DoAction
Value=MyCustomActionCHECKBOXVALUE = 1 /Publish
The custom action is launched, but
Pally Sandher wrote:
Yes but you will get an ICE80 error when compiling if you set
Win64=yes on a component when your MSI is an x86 build vice-versa.
Why would you want to?
If you install mixed 32 and 64-bit components in a single install? We
have an installer that MUST do this. What
2008/10/28 Peter Vestergaard [EMAIL PROTECTED]:
Thanks for your reply.
What do you mean by sequence it.
Place it in the sequential UI flow.
I placed my custom dialog between progress
and exit dialogs.
I follwed Pally's advise and did this:
Publish Dialog=MyExitDialog Control=Finish
Thanks ! Seek and thou shall find !
On Tue, Oct 28, 2008 at 2:00 PM, Sébastien Mouren
[EMAIL PROTECTED] wrote:
Search the list, it was already asked and answered.
-
This SF.Net email is sponsored by the Moblin Your Move
If you need a mixed installer, then you have to make it a 64 bit
installer. It doesn't make sense to install 64 bit components on a 32 bit
system anyway, so just don't include those components in your 32 bit
installer, or alternately, don't offer a 32 bit installer. In some
corporate
Hmmm -- I guess my question is -- what am I risking? Getting rid of the
32-bit installer is a non-starter for us (this isn't a corporate
environment), and the 32-bit mixed installer works perfectly in both
environments. (Our 64-bit components don't actually take up much room).
A single
The gotcha is that you cannot have a 32 bit installer install 64 bit
components.
On Tue, Oct 28, 2008 at 4:13 PM, Michael Owings [EMAIL PROTECTED] wrote:
Hmmm -- I guess my question is -- what am I risking? Getting rid of the
32-bit installer is a non-starter for us (this isn't a corporate
MSI doesn't support a single installer for multiple architectures. That's
the problem. You'll never get a 32bit installer to validate with 64 bit
components in it, period. MSI requires that you build a single installer
for each architecture you target. You can use conditional statements and
On Mon, 27 Oct 2008 17:13:21 + (GMT), Andrew Kendall wrote:
Andrew,
extracting file to install this utility on the users system at the
same time as our main application.
No, it's not strongly discouraged, it is simply not supported and
impossible, plain and simple.. :-)
Use a
Yeah, I thought the only workaround would to be to use a
bootstrapper...guess I need to look into those and see what works.
Let me know if you have any suggestions or preferences.
Thank you,
Jon
On Mon, Oct 27, 2008 at 8:42 PM, Bryan Turner [EMAIL PROTECTED] wrote:
We have also experienced this
If your MSI is built for x86 (i.e. Platform = Intel) try as you may,
you will *not* be able to access the 64-bit system directories
ProgramFiles64Folder, System64Folder or CommonFiles64Folder. You may get
an MSI to build even look as though it installs but it won't ever
access these areas. When
A mixed install will *always* be unavoidable for us.
Some of our components are plugins for other applications -- which may
themselves be 32-bit or 64-bit (even on a 64-bit platform, a 32-bit app
could be in use, or a particular app may ONLY be 32-bit), which requires
the plugins built for the
Hi,
We've recently seen the following error sometimes in builds. When we retry the
build leg, the error disappears.
We've caught the error on different build machines with different products
where 3.0/2.0 wix are used.
Product with 3.0 wix:
1errors in directory
One approach to this that I have seen work is where you have one .wxs file that
generates both a 32-bit and a 64-bit .msi through conditional logic. You then
wrap both the 32-bit and 64-bit .msi in a bootstrapper that determines the
correct .msi to install at runtime. The bootstrapper can be
Hi,
I just uploaded a pre-release build of a new UI Handler that might be of
interest to WiX folk. Details are here:
http://www.acmedigitalwidgets.com/blog/
I'd appreciate any and all feedback.
Thanks, Jim Stout
-
This
Hi again, I'm running into trouble when I'm trying to install/remove/install a
patch which applies to multiple versions of a product. Here's a snippet from
the WXS for the patch in question:
(Imagine I'm upgrading product Foo to version C. Version A and B exist in the
wild.)
If there are issues they are in the Windows Installer since they provide the
tool for validation.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 08:49
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] error
I thought as much but got no response from the Windows Installer team after
inquiry. I'm curious to know, however, if any other parties on the Wix alias
are experiencing the same issue.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008
I'm running a WIX install on a Vista box and I get the below error when I
run a custom action. The action runs fine on an XP box. I am running the
installer with elevated privileges from an administrator account. Does
anyone have an idea what could be causing this. I am running build
Almost always, that message means the CustomAction crashed... unless your code
always leaks handles.
-Original Message-
From: Dave Largen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 11:10
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error 2769: Custom Action
Very strange, I put a little messagebox popup after the very last line of my
custom action Install call and it went all the way through without
exceptions and showed my custom message. I also get this very nice empty
dialog box that pops up at the end.
-Original Message-
From: Rob
1. I'm trying to write a custom action, and bug 2166658 is hitting me
despite upgrading to 3.0.4624 - I'm still getting
dutil.lib(precomp.obj) : fatal error LNK1103: debugging information
corrupt; recompile module errors. (I do see the new files... maybe the
headers could do some magic tricks in
I think the first issue is caused by the Wix utility static libraries
being build with VS 2008. You'd need to rebuild them with 2005, I
believe. This isn't a problem with 2.x (and VS 2005).
Curtis Jewell wrote:
1. I'm trying to write a custom action, and bug 2166658 is hitting me
despite
It is, (that's what 2166658 is about) and I see files named
dutil_2005.lib and wcautil_2005.lib - but shouldn't things just work
if you include the appropriate headers?
(Oh, they're linked in via the project properties and not via #pragma
comment(lib, ...) stuff in the headers, going to change
1. If the _2005.libs are not working for you, please add any additional
information available to the bug so it reopens.
-Original Message-
From: Curtis Jewell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 12:38
To: General discussion for Windows Installer XML toolset.
Does the content of the Path attribute to the DirectorySearch element in Wix
have any inherent limitation?
Doing this
Property Id='VS08EXISTS'
DirectorySearch Id='Check08Dir'
Path='[VS08IDE]\..\..\VC#\CSharpProjectItems'/DirectorySearch
/Property
elicits an error in the log
Subject: Re: [WiX-users] 3 problems with integration of WiX and VS2005 SP1
On Tue, 28 Oct 2008, Rob Mensching wrote about Re: [WiX-users] 3 problems...:
1. If the _2005.libs are not working for you, please add any additional
information available to the bug so it reopens.
Done. (Had to sign
Yes, Windows Installer has quite a few limitations. Such as no ... DrLocator
will have more rules.
-Original Message-
From: Vijai Kalyanapasupathy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 15:38
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Paths In
Hi there.
We are running a MSI in W2K3+Sp1, and we get the error below.
Is anyone familiar with this error?
MSI (s) (00:B8) [16:37:35:138]: Executing op:
CustomActionSchedule(Action=ExecXmlFile,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)MSI
(s)
Hi there. We are running a MSI in W2K3+Sp1, and we get the error below. Is
anyone familiar with this error? MSI (s) (00:B8) [16:37:35:138]: Executing op:
CustomActionSchedule(Action=ExecXmlFile,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)MSI
(s) (00:04)
Hi everyone and thanks Pally for replying.
Here is what I want to do -
I have two installers of a product, one for 32bit version and one for
64bit version. Now, my task is to combine them both into one single
installer. There are certain dlls that will go into both 32bit and
64bit. So I am
Bryan Turner wrote:
We have also experienced this issue. Fortunately, we have a
bootstrapper/chainer that allows us to install vcredist_x86.exe and
vcredist_x64.exe instead of merging those modules into our installer
directly.
The downside is that the redist has its own entry in ARP/PF
[EMAIL PROTECTED] wrote:
candle -o mystuff.wixlib mystuff.wxs -ext WixUtilExtension.dll
Note that candle produces .wixobj files, which you can combine into a
.wixlib using the lit tool.
--
sig://boB
http://joyofsetup.com/
MAKARAND HAZARIKA wrote:
I have two installers of a product, one for 32bit version and one for
64bit version. Now, my task is to combine them both into one single
installer.
Windows Installer doesn't support that. See Using 64-Bit Windows
Installer Packages in the MSI SDK for details.
--
Are there any operators supporting this ? AND , NOT, OR are logical operators,
right ?
Thanks and Regards
Mukesh
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based
48 matches
Mail list logo
