Yes! It worked now!
Thank you very much, Alex.
Alexander Shevchuk wrote:
>
> I found original email with the code. There is a typo in it. Add "Set"
> in front of fso = CreateObject...:
>
> Set fso = CreateObject(Scripting.FileSystemObject)
>
>
>
>
> -Original Message-
> From: [E
Daryn Mitchell wrote:
> - Should a merge module's Secure Custom Properties be automatically put
> into the consuming MSI's own SecureCustomProperties automatically when
> it incorporates the merge module? (i.e. is Wix not doing something it
> should be doing? Much more likely that I don't know bes
Michael Ballou wrote:
This is in regards to the problems using ServiceControl to start a
service that is dependent on side-by-side assemblies.
It seems I have been recently hit by this problem in a way I didn't
really expect. I have a C++ (non-.NET) service built with VS 2005.
It seem
Paul McCloskey wrote:
Does anyone have a _simple_ CopyFile example they can share? One of
our MSIs needs to copy a file from its current directory (CD) to the
INSTALLDIR.
That will cause failures if the user doesn't have the CD in the drive
during a modify/repair. A safer way is to use a
Riyaz Mogharabin wrote:
> I have decided to use the WiXUI.INSTALLDIR to create a file installer. I
> want to know if I can manage the dialogs that are used in the WiXUI library.
> Is it possible to use the dialogs in some other sequence, or put custom
> dialogs between two of them?
>
Yes but s
Flavio Stanchina wrote:
> OK, they show up in the order I want if I put the s directly
> under rather than using s. If this is expected, we
> should document this, and if it isn't, we need to fix so it
> works the same as in this respect.
>
You're relying on two accidents:
1. That featur
Kevin Burton wrote:
The second method has the major drawback of the fact that I don't know
how to conditionally force an uninstall then proceed with the "normal"
installation.
That's what a major upgrade is. Just schedule RemoveExistingProducts
immediately after InstallInitialize. See the
Riyaz Mogharabin wrote:
> But when I put this code into the WiXUI library to use, everything goes
> wrong. I mean, I can not assign the Value I get from the registry to the
> INSTALLDIR which is used in the WiXUI.InstallDir. Is it possible to use this
> option with WiXUI.InstallDir at all? Do I nee
Ravit Shapira wrote:
It seems that I missed some important details - our msi installs
Speech recognition components that are part of Windows Vista, and on
Vista we do use trusted Installer service.
Our main problem is with the registry key. We cannot overwrite keys in
the registry on Vista
V K Gangwar wrote:
> I tried to put custom action in UISequence also but it is not working
> for me, I am getting error 2762.
As 2762 points out, you're trying to run a deferred CA in a sequence
where that's not allowed. It needs to be in InstallExecuteSequence, not
the UI.
--
sig://boB
http:
Mark Visser wrote:
> Is there any particular reason heat creates a ComponentGroup with -
> sfrag, and no ComponentGroup without?
>
Because without -sfrag, Heat creates many individual fragments, so a
ComponentGroup doesn't save any effort.
> Also, with -sfrag, heat creates a top-level Direct
[EMAIL PROTECTED] wrote:
In my installer, INSTALLDIR is falling under "Pfiles" (In one case, I
use ".") , as seen in my example/
ProgramFilesFolder is explicitly 32-bit, hence the error.
ProgramFiles64Folder is the 64-bit version.
--
sig://boB
http://joyofsetup.com/
faheemitian wrote:
>> MSI (s) (FC:B4) [12:56:42:668]: Component: TestServExe; Installed: Local;
>> Request: Null; Action: Null
>>
Action:Null means that the component won't be installed, so MSI won't do
anything with the service.
--
sig://boB
http://joyofsetup.com/
-
Xu nanxuan wrote:
> Thanks, it works. But another question. After starting a new Wix
> Project in VS, everytime I add somelines involving a stock dialog, say
> (just e.g.):
>
>
> Value="CancelDlg">1
>
>
>
> systemwill report error like:
> Error5ICE17: Bitmap: 'WixUI_Bmp_Dialog' for Control: 'Bit
Richard Bain wrote:
1) Does EmbeddedChainer suit what I want?
Yes but...
2) If so, is there any examples anywhere of how to use it. Does it
need custom actions or do you literally just pass in another msi (can
it even take in msi's?)
Yes, you need a custom action -- one that implements a c
I found original email with the code. There is a typo in it. Add "Set" in
front of fso = CreateObject...:
Set fso = CreateObject(Scripting.FileSystemObject)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Shevchuk
Sent: Saturday, March 08
Hi Mikko,
Two options here:
- Use Orca tool. Open your MSI, go to "Tools/Dialog Preview...". Choose
whatever dialog you want to see.
- Add to your install command EXECUTEMODE=None, ie: msiexec /I mymsi.msi
EXECUTEMODE=None
EXECUTEMODE: http://msdn2.microsoft.com/en-us/library/aa368567(VS.85).
The error you are getting is 0x800A01B6 - Object does not support this property
or method.
Check if spelling in fso.FileExists is correct.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justintu
Sent: Saturday, March 08, 2008 5:28 AM
To: wix-users@list
I guess thatÂs pretty much what I was looking for. Not a real need for
forums with such site I guess.
Thanks a lot for the link! (It should be posted on the main site and wikiÂ
)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hall
Sent: mardi 4 mars 2008 10:13
To: wix-
Hi Alex,
Thank you very much for the help.
I have tried the code you posted but got an error stopped the MSI
installation:
"Error 1720. There is a problem with this Windows Installer package. A
script required for this install to complete could not be run. Contact your
support personnel or pack
Hi Alex,
Thank you very much for the help.
I have tried the code you posted but got an error stopped the MSI
installation:
"Error 1720. There is a problem with this Windows Installer package. A
script required for this install to complete could not be run. Contact your
support personnel or pack
21 matches
Mail list logo
