Hi all,
I want to install a service, but the service needs a runtime installed
first to be able to run. More importantly, the C runtime.
My current setup is,
Feature Id=ServiceToInstall Level=1 InstallDefault=local
TypicalDefault=Install
MergeRef Id=msvc80 /
ComponentRef
Really, I did not try out, starting a managed custom action deferred. It needs
the installercontext, of the current install to work, is the context still
active at that time? Sorry, I don't know.
Any hints welcome.
Oliver
From: Hao Liu [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 24. Oktober
Hi Richard,
I assume this isn't done in the Media element as I can only see that you
can specify that the cab is embedded and it's name..
Simon
--
Message: 8
Date: Tue, 23 Oct 2007 09:24:31 -0600
From: Richard [EMAIL PROTECTED]
Subject: Re: [WiX-users] Digital
Not a direct answer, but if you run WiX 3.0's heat.exe against your 32-bit
COM DLLs then it'll generate the right Class, AppID, Interface etc. output.
--
View this message in context:
http://www.nabble.com/wix-2.0-to-3.0---COM-registration-tf4682182.html#a13382551
Sent from the wix-users
If my CA in MyCA.dll needs to call a fn in MyUtils.dll then I'm currently
expecting to have to write a separate pair of CAs that pull MyUtils.dll out
of the Binary table and then delete it at end-of-setup.
InstallShield provides just such a handy pair of Custom Actions
(ISSETUPFILESEXTRACT co.),
Geoff Finger-2 wrote:
The specific problem in this case is the x64 installer was working
just fine but someone pointed out that one of the files was 32 bit and
thus should be installed to Program Files (x86) instead of the
normal Program Files folder.
On 64-bit Windows,
All my DLL's are .net assembly but they can be registered as COM.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karim
MacDonald
Sent: Wednesday, October 24, 2007 3:21 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] wix 2.0 to 3.0 - COM
On one of my Virtual PC's Custom Actions fails to execute.
Log:
MSI (c) (E0:F0) [14:10:03:142]: Machine policy value 'AlwaysInstallElevated'
is 0
MSI (c) (E0:F0) [14:10:03:142]: User policy value 'AlwaysInstallElevated' is
0
...
MSI (s) (70:B8) [14:10:37:218]: Executing op:
I was under the impression that while it is only permitted to *trigger*
one NewDialog operation, it is permitted to include definitions for
several trigger operations as long as the conditions under which the
separate dialogs are shown are mutually exclusive.
I agree however that is not what the
I am trying to give the option to delete some extra files if the user checks
a checkbox on uninstall. I can bypass the checkbox and make it delete the
files but when the checkbox is present, it deletes the files whether it is
checked or not. Any ideas what I am doing wrong?
Code segments below.
Is anything in Wix 3.0 documented?
Sorry. I just couldn't resist.
Rob Mensching [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/23/2007 03:11 PM
To
'Rob Mensching' [EMAIL PROTECTED], 'Adam Majer' [EMAIL PROTECTED]
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] wixout file
Nitin Chaudhari wrote:
All my DLL's are .net assembly but they can be registered as COM.
Sorry, I should've looked more closely at your registry entries. FWIW,
here's my take on the problem:
Using registry keys is the recommended way of registering .NET Assemblies for
COM Interop.
http://msdn2.microsoft.com/en-us/library/aa367520.aspx
Use the Registry table instead of the Class table when you register COM
Interop for an assembly.
-Ursprüngliche Nachricht-
Von: [EMAIL
You can use the 'undocumented' -scom switch with heat.exe to generate only
RegistryKey/RegistryValue-entries (instead of Class/ProgId/...).
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] Im Auftrag von Strele Franz
Gesendet: Mittwoch, 24.
shambhu kumar wrote:
UIText Id=SelAbsent![CDATA[This feature will not be
available.]]/UIText
UIText Id=Seldvertise![CDATA[This feature will be installed when
required.]]/UIText
UIText Id=SelAllLocal![CDATA[This feature, and all subfeatures,
will be installed on local hard
Geoff Finger wrote:
Instead what I found was a post claiming I don't think you want to
reference ProgramFiles64Folder either. Use ProgramFilesFolder and
Windows Installer will put things in the correct directory based upon
the Component's Win64 setting.
That's not how it works. A 64-bit
Adam Majer wrote:
How can I structure this such that the merge module is installed
completely prior to installing the component?
That's not how Windows Installer works: Merge modules lose their
identity when merged, so they're just a bunch of components in the .msi.
Then, each resource of
Simon Topley wrote:
I assume this isn't done in the Media element as I can only see that you
can specify that the cab is embedded and it's name..
Yes, you have multiple Media elements and use the DiskId attribute to
control which components go into which .cab.
--
sig://boB
for wix v3, build 3419, why is there a difference in the wix.dll that is
installed with the msi and the version found in the zip file?
if i install the msi to get the votive stuff and the xml references and
stuff installed for VS, but then use binaries extracted into a temp
directory to compile
On 1/22/07, Goetz, Russ [EMAIL PROTECTED] wrote:
Thanks to help from this group I am now able to specify which UI I wish
to use by passing the following to light.exe: -ext
WixUIExtension.dll-cultures:en-us and specifying say
UIRef Id=WixUI_Minimal /
In my .wxs file. The minimal UI
koawmfot wrote:
for wix v3, build 3419, why is there a difference in the wix.dll that
is installed with the msi and the version found in the zip file?
It's a bug in the build process. For now, stick with the .msi copy.
--
sig://boB
http://joyofsetup.com/
Scott Palmer wrote:
Is there a way to actually get the license agreement to show on the
license agreement screen without having to highlight the text or
adjust the scrollbar? I find that my license agreement is there - but
is not drawn until I try to manipulate the text control that it is
I know you're being slightly flippant but truly the answer is, Yes, the
schema is all documented. The command-lines and the tools to use are
documented. I'm happy for people to say, Hey, such-and-such isn't
documented. can I expect it to remain constant supported and all that good
stuff? I'll
In article [EMAIL PROTECTED],
xyavier [EMAIL PROTECTED] writes:
I am trying to give the option to delete some extra files if the user checks
a checkbox on uninstall. I can bypass the checkbox and make it delete the
files but when the checkbox is present, it deletes the files whether it
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] writes:
I was under the impression that while it is only permitted to *trigger*
one NewDialog operation, it is permitted to include definitions for
several trigger operations as long as the conditions under which the
separate dialogs are
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
How can I structure this such that the merge module is installed
completely prior to installing the component?
In addition to what Bob Arnson said, check your install execute
sequence and look at the relative ordering of
In article [EMAIL PROTECTED],
V K Gangwar [EMAIL PROTECTED] writes:
I need to invoke a function (method) in a DLL and want to use return va=
lue of that function. How this can be done.
The best practice is to minimize the amount of custom code that's
running at install time.
What is
In article [EMAIL PROTECTED],
Nitin [EMAIL PROTECTED] writes:
All my DLL's are .net assembly but they can be registered as COM.
Regasm /File will dump out a registry file of all the registry
values/keys that are needed to register your assembly.
Is there some tool in WiX that will eat a
It is a mistake in the build process. I've been screwing around with the
public key and the way that we store it on the build machine and the way we
reference it in the build system and I apparently got things crossed
somewhere. I'll get into it before the next build.
Thanks for pointing
Bob Arnson wrote:
Adam Majer wrote:
How can I structure this such that the merge module is installed
completely prior to installing the component?
That's not how Windows Installer works: Merge modules lose their
identity when merged, so they're just a bunch of components in the .msi.
Yep... I kinda forgot the smiley in my email :)
So where is the 'command lines and the tools to use' documentation
located, precisely?
Kelly
Rob Mensching [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/24/2007 09:05 AM
To
'Kelly Leahy' [EMAIL PROTECTED]
cc
[EMAIL PROTECTED],
Richard wrote:
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
How can I structure this such that the merge module is installed
completely prior to installing the component?
In addition to what Bob Arnson said, check your install execute
sequence and look at the
We have one service in the installer that replies on a file being
installed to the GAC, so the service can't be started until after
InstallFinalize. I use a deferred Custom Action to NET START
servicename and it seems to be working fine for our customers. Just
thought I'd mention that option.
That's correct, Vista uses the same SxS model with Fusion to install the
C++ runtimes as GAC installation, so the runtimes aren't available until
after InstallFinalize.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adam Majer
Sent:
Well, “-?” is documentation. smile/
The tools are supposed to be documented in WiX.chm… although, I expect we’re
behind on that and I’d happily take bugs assigned to me to address.
From: Kelly Leahy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 09:50
To: Rob Mensching
Most likely your custom action is crashing. If it works when you run it
elevated then it's probably a security issue. Are you checking the results of
API calls?
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benas
Sent: Wednesday, October 24, 2007 4:30 AM
To:
Rob Mensching wrote:
schema is all documented. The command-lines and the tools to use are
documented.” I’m happy for people to say, “Hey, such-and-such isn’t
documented… can I expect it to remain constant supported and all that
good stuff?” I’ll then go into the tools and see if it is a
Trying to add a reference to the WixSqlExtension.dll on my project, and
adding
xmlns:Sql=http://schemas.microsoft.com/wix/SqlExtension;
I always get this error:
The extension 'Microsoft.Tools.WindowsInstallerXml.Extensions.SqlCompiler'
uses the same xml schema namespace,
On 10/24/07, Bob Arnson [EMAIL PROTECTED] wrote:
Scott Palmer wrote:
Is there a way to actually get the license agreement to show on the
license agreement screen without having to highlight the text or
adjust the scrollbar? I find that my license agreement is there - but
is not drawn
Hi,
There was a strange issue which occured. I created a msi which was running
perfectly on mine as well as another developer's machine, but
it just ended prematurely when we copied this msi to another colleague
(non-developer)'s machine.
Of special notice is that it ended when the pressing on
Hi, do you compile your custom action in Debug or in Release? Whic version of
C++ are you using? Be sure to deploy the VC runtime too.
Run depends.exe tool on your friend´s machine and validate each dependence of
your custom action dll.
Regards
Silvio.
-Original Message-
From:
I did look at them in Orca, it looks OK to me.
My verbose log is as follows when it is not checked:
MSI (s) (AC:D0) [14:19:52:507]: Component: MyComponent; Installed: Local;
Request: Absent; Action: Absent
PROPERTY CHANGE: Deleting DELALL property. Its current value is '1'.
The log is the
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] writes:
Having said that, the scenario which prompted the question may still not
work exactly as desired - specifically that the dialog which
*immediately* follows the one showing the feature tree varies based on
the presence (or
In article [EMAIL PROTECTED],
xyavier [EMAIL PROTECTED] writes:
MSI (s) (AC:D0) [14:19:52:507]: Component: MyComponent; Installed: Local;
Request: Absent; Action: Absent
OK, this says your component is installed and will be removed. Isn't
there anything later in the log about files
Hi Thanks Silvio!!
The c++ was done in debug mode and we shifted to release mode and it works
perfectly!
Thanks!
Date: Wed, 24 Oct 2007 16:39:31 -0300 From: [EMAIL PROTECTED] To:
wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Minimum
Requirements for msi on client machine.
Wilson, Phil wrote:
That's correct, Vista uses the same SxS model with Fusion to install the
C++ runtimes as GAC installation, so the runtimes aren't available until
after InstallFinalize.
Solution:
* Install merge module if (VersionNT 600) OR Version9X . In other
words, install the
Scott Palmer wrote:
Ok, thanks. It's funny that the Mondo UI doesn't show the same
problem with the same RTF file. Must be related to the dimensions of
the control or something.
That's because the EULA isn't shown in the first dialog in that set.
That's the trigger.
--
sig://boB
jrcolons wrote:
The extension 'Microsoft.Tools.WindowsInstallerXml.Extensions.SqlCompiler'
uses the same xml schema namespace,
'http://schemas.microsoft.com/wix/SqlExtension', as previously loaded
extension 'Microsoft.Tools.WindowsInstallerXml.Extensions.SqlCompiler'.
Please either remove
48 matches
Mail list logo
