That's true. I was keeping it simple since `custom actions are evil`. :-)
Checkout: http://www.itwriting.com/blog/?p=198These guys seem to have
gone down this road already.
"Wilson, Phil" <[EMAIL PROTECTED]> wrote:
v\:* {behavior:url(#default#VML);} o\:* {behavior:url(
To further elaborate, consider the following snippet (I tested and it
works):
(VersionNT) AND (NOT
VersionNT64)
Ive uploaded the MSI that causes the problem to
http://www.netspeed.com.au/frankeden/junk.zip
I havent added a new bug because this one: - "[1576981 ] Dark cannot
decompile Votive.msi"
looks similar, but the date that bug was submitted was over a year ago, so
does this mean that development on
I wouldn't think the package architecture would be terribly important. A
32-bit package can be installed on either. I believe the key would be
marking the individual components as either 32-bit or 64-bit by setting the
msidbComponentAttributes64bit attribute. You could even go so far as
separati
Another thing to check for is whether or not one of the products is
installed per-user and not per-machine. If its installed per-user but
not for the currently logged-in user, then the Upgrade table won't
detect it.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
On Jan 4, 2008 2:51 PM, Chad Petersen <[EMAIL PROTECTED]> wrote:
>
>
> I'm working on two installers that are both hotfixes. One is for the client
> and one is for the server. Right now I'm having them both detect for one of
> our other installed applications and only proceed if it finds that it is
The difficulty with a registry check is that it can be out of date. It can look
one way but be in the opposite state because it requires a reboot to set it.
So if a user resets it the registry entry will say zero but it will still be
active until a reboot.
It seems to me that if it's the app t
Can I ask why you want to prevent your setup to be launched with UAC enabled?
Your installer will be run with UAC on most of the cases.
On Jan 4, 2008 2:07 PM, Scott Palmer <[EMAIL PROTECTED]> wrote:
> I want to detect if UAC is turned on in Vista and refuse to install if it
> is. How can I do th
I'm sure you about to get jumped for even thinking about it :-)However,
UAC/LUA can be manipulated via policy and it gets stored in the registry like:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"ConsentPromptBehaviorAdmin"=dword:0002
"Consent
Using WiX 2.0.5325.0
I'm working on two installers that are both hotfixes. One is for the
client and one is for the server. Right now I'm having them both detect
for one of our other installed applications and only proceed if it finds
that it is installed. They both look for the same thing. If
I want to detect if UAC is turned on in Vista and refuse to install if it
is. How can I do this?
Scott
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/
I've got a component that's installed by two products, via a merge module.
There's also some custom actions, conditioned something like this:
Install_Ensure, Condition: $Comp1 = 3
InstallRollback_Remove, Condition: $Comp1=3 AND NOT ?Comp1=3
Uninstall_Remove, Condition: $Comp1 = 2 AND NOT UPG
Bob Arnson írta:
> Szentpali Janos wrote:
>> Can you suggest some strategy to help one install components that do not
>> come in msi-s or msm-s but that are shared/common components that
>> could/would possibly be installed by non msi setups
>
> If you're not using stable component IDs through MSI,
My MSI works perfectly in the default but I can't figure out how to get
the msi to show a folder selection dialog to do an Admin install.
My command line says: "msiexec.exe /a mymsi.msi"
Do I have to author my own dialog or is there already one in the WIx
Source Files I can add using ?
I'm usi
This is basically an exercise in debugging. Standard operating procedure is
something like this:
1) Did it even load and start? Adding a messagebox call as a debug aid first
thing in the code will tell you whether it loaded and started. If it doesn't
get that far the issue is usually a dependen
My bet is that it's using two MSIs and bootstrapping, maybe with a shared
'external' cab for less overhead in size.
Christopher Painter <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/04/2008 09:20 AM
To
Bob Arnson <[EMAIL PROTECTED]>, SaiTeja <[EMAIL PROTECTED]>
cc
wix-users@lists.sourcef
According to Stefan Krueger's blog Advanced Installer 6.1 supports the ability
to build unified mixed 32/64 bit packages. I haven't looked to see how they do
it under the hood and I don't know if the technique is one that WiX would
support one day or not.
http://msmvps.com/blogs/installs
Hi,
> And in some cases, it WILL break. For example, feature ids are limited
> to 38 characters, regardless of schema.
Good to know. But my case is limited to the CustomAction table...
Kind regards,
Henning
-
This SF.net em
I have the exact same problem, but adding the line didn't solve it.
The following line leads to the same problem (my service is a VB.NET EXE):
But the problem disappear when I remove the Assembly attribute:
JC
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De
Jared Hughes wrote:
> I'm trying to prepare my product for localization and I ran into a problem
> localizing the GUIDs for the Product ID and Upgrade Code. I noticed a couple
> messages about this and I also saw that a bug about this was closed several
> months ago, and I'm curious if this has bee
SaiTeja wrote:
> 1) Is it possible to create one MSI for both 32bit and 64 bit OS
>
If you need to install 64-bit components, you must have a 64-bit
package. If you have only 32-bit components, then a 32-bit package will
install fine on an x64 OS.
--
sig://boB
http://joyofsetup.com/
Szentpali Janos wrote:
> Can you suggest some strategy to help one install components that do not
> come in msi-s or msm-s but that are shared/common components that
> could/would possibly be installed by non msi setups
If you're not using stable component IDs through MSI, the closest you'll
get
Richard wrote:
> While I agree with this, I would add that in practice I've never seen
> a problem arising from overflowing the field. Still, it puts you in a
> position of "working by accident" instead of "working by design".
> I've learned the hard way over the years that "working by accident"
>
VersionNT64 is not a public or restricted public property. It is a standard
private property.
Stefan Pavlik <[EMAIL PROTECTED]> wrote:
SaiTeja wrote:
> Hi,
>
> How can I check the machine is 32 bit or 64 bit
>
>
Check the VersionNT64 public property.
http://msdn2.microsoft.com/en-us/lib
Hi,
While installing am getting following error.
am using all merge modules(ATL,CRT,DebugCRT,DebugMFC,MFCLOC,DebugMFCLOC etc)
can any one tell me what is the problem hre
Action 18:46:08: PublishProduct. Publishing product information
1: ARPPRODUCTICON.exe
1: console.exe
1: help.chm
Action 1
SaiTeja wrote:
> Hi Stefan
>
> after I searched I got
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> But I didnt udnerstand how to set the variable "env.BUILDTARGET"
In this case
Hi Stefan
after I searched I got
But I didnt udnerstand how to set the variable "env.BUILDTARGET"
Any inputs
Stefan Pavlik-2 wrote:
>
> SaiTeja wrote:
>> My main
SaiTeja wrote:
> My main aim is I want to set program files folder
> Is the following way is correct
>
>
>
>
>
>
>
>
>
>
>
>
It is not correct.
The VersionNT64 is public
Hi Stefan,
Thanks a lot.
My main aim is I want to set program files folder
Is the following way is correct
Stefan Pavlik-2 wrote:
>
> SaiTeja wrote
SaiTeja wrote:
> Hi,
>
> How can I check the machine is 32 bit or 64 bit
>
>
Check the VersionNT64 public property.
http://msdn2.microsoft.com/en-us/library/aa372497(VS.85).aspx
Stefan
-
This SF.net email is sponsored by:
Hi,
How can I check the machine is 32 bit or 64 bit
--
View this message in context:
http://www.nabble.com/Check-machine-type-tp14612557p14612557.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This S
Bob Arnson wrote:
>> Yeah, I've found this article before ... but how would I do this within
>> my app? Do I have to create multiple (identical) -elements like
>> this:
>>
>
> Yes. You can use CopyFile to install one and copy it elsewhere but it's
> about the same amount of work and CopyFile i
32 matches
Mail list logo
