Thanks a lot - it works for me too.
Bo
Ben Greenberg-3 wrote:
>
> I got this to work in WiX3 by linking to WixDifxAppEntension and adding
> the Custom Actions manually:
>
>
> DllEntry="ProcessDriverPackages" HideTarget="no" Impersonate="no"
> Execute="immediate" Return="check"/>
>
Garth wrote:
> It could be due to a classic UNICODE overflow bug in the file
>
> http://wix.cvs.sourceforge.net/wix/wix/src/ca/serverca/scaexec/scacertexec.cpp?view=markup
>
> WCHAR wzFriendlyName[256] = { 0 };
> DWORD cbFriendlyName = sizeof(wzFriendlyName);
>
> Should read
>
> WCHAR wzFriendlyNam
DexterSinister wrote:
> The problem seems to be the Preselected property and the condition on the
> MaintenanceWelcomeDlg,
> which is 'Installed AND NOT RESUME AND NOT Preselected' ... this is the
> stock dialog that comes with
> WiX, and the condition that is built in to the stock ResumeDlg is 'In
Gonzalo Diethelm wrote:
I guess that's arguable. I already had to provide all those details
(service name, startup information, etc.) in the EXE itself, in order
to support the /install, /remove, /start and /stop switches. Why would
I want to repeat that in the installer, instead of just callin
Andrey T wrote:
> I have .wxs file with element`s attribute FileSource=".\". Files
> that resides in components belonging to that directory don`t specify any
> "Source" attributes. What algorithm uses light.exe when it builds final .msi
> file? Does it use folder where .wixobj file resides or .
Must be time to create an MSI log of UI and non-UI to see what's going
on.
Have you searched your system for the files involved? It's not unusual
for files to end up being installed at some unexpected location (such as
C:\filename), so it's possible that skipping the UI sequence is
resulting
Since build 3.0.3328's zip file had Strong Name problems, I installed
the msi. That package has problems with paths with spaces. Using 8.3
names works ok.
It works if you only ask for help, but fails if a link is attempted.
Dave
"c:\Program Files\Windows Installer XML v3\bin\light.exe" -?
Micros
Excellent, Thanks!
Eric
From: John Vottero [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 4:57 PM
To: Eric Latendresse; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] How to configure SQL Express bootstrap
Find the Package.xml file for SQL Express, edit it and look
Find the Package.xml file for SQL Express, edit it and look for the
mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Tuesday, October 02, 2007 5:41 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to configure SQL Express bootstrap
I created a bootstrapper with MSbui
2.0.4701 is pretty old now. As far as I can see from the latest release,
5325 (from May this year), this error shouldn't occur.
The error would be coming from either validating the XML against the schema
- but HttpHeader is listed as an element that can appear under WebSite in
the latest schema
I created a bootstrapper with MSbuild to install SQL Express, but I'd
like to change the configuration... Since it is in a bootstrap it
doesn't show the install wizard. Surely configuring the database engine
is possible. Does someone have an example or can please point me in the
right direction?
Why add this functionality to your program when Windows XP and Server 2003
ship net.exe which can start and stop services, and sc.exe, which can create
and delete services as well? Net.exe has been able to start and stop
services since Windows NT 4.0 at least, and sc.exe was previously part of
the
Apparently wix.dll was strong named with a different public key this time
around while all the other tools are using the correct one. We are looking what
caused the problem and will get a fix and release a new build once its fixed.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of M
Chad Petersen wrote:
>
> Have you tried running the same MSI a second time. Does it do the same
> thing as when you click Change in Add/Remove Programs? If so, you should
> be able to have it create a verbose log which might lend some clues,
> like whether or not ARPNOMODIFY is being set or not.
On 2 Oct 2007, at 18:54, Wilson, Phil wrote:
> The only time I've ever seen this error message is when the shell
> folders registry entries are incorrect. MSI checks every entry in
> the Directory table for validity, so make sure you don't have a
> directory/property name that is resolving
Hello,
I have a relatively simple installer. It fails during initialization
when it tries to compute the space for a network drive that is password
protected.
Is there any way to cancel this space-check or only look at local disks?
Or, is there a way to continue even if the space check fails?
The problem you are hitting is that the Wixpdb contains no information about
msm's they are merged in after the fact.
Three options:
1. Instead of using the wixpdb, just use the admin image functionality I added
in order to create transforms for the products that contain msm's.
2. Use Melt.exe
Thanks Bob, thanks Peter for your answers.
I will not have problems with the localizations. The only problem will be
the time to generate a patch, because my setup takes a very long time to
build - about 30 mins for each MSI and I have over 20 MSI's (12 languages *
2 - due to x86 and x64). Knowi
Collected but not used by me, this VBScript used in a custom action may
help:
Function Combo()
' This function initializes and then sets variables to set values for
the four columns
' of the ComboBox table (Property, Order, Value and Text). Then a
function is called to add
' the row of v
The only time I've ever seen this error message is when the shell folders
registry entries are incorrect. MSI checks every entry in the Directory table
for validity, so make sure you don't have a directory/property name that is
resolving to a ?, and it's probably worth making sure that these fo
Hi,
I have a uninstall which Fails sometimes but not always
It prints the error
DeleteMachineCertificate: Deleting certificate with friendly name: Garth
"DeleteMachineCertificate: Failed to delete certificate with friendly
name: Microsoft Root Authority, continuing anyway."
MSI (s) (94:24) [
Have you tried running the same MSI a second time. Does it do the same
thing as when you click Change in Add/Remove Programs? If so, you should
be able to have it create a verbose log which might lend some clues,
like whether or not ARPNOMODIFY is being set or not.
-Original Message-
From:
I meant pyro when I said torch below.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu
Sent: Tuesday, October 02, 2007 10:15 AM
To: Bob Arnson; Cristian Baiu
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fw: Some STUPID Limitation
You should be able to pass transforms generated from wixpdb's in combination
with ones generated from admin images. You will need a transform passed to
torch for each product you want to target because product code information is
important and I assume each language you ship has a different prod
Use the VersionMsi standard Windows Installer property.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss
Sent: Friday, September 28, 2007 3:41 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Determine which Version of Win
Thank you much. I figured it was something simple like that, but I didn't
know the syntax for it.
On 10/2/07, Chad Petersen <[EMAIL PROTECTED]> wrote:
>
> ..\ is the syntax for one folder up from the current folder.
>
>
> --
>
> *From:* [EMAIL PROTECTED] [mailto:
> [
I got it working by adding the following
Can't remeber where I got this from...
Think I extraced it from somewhere...
Seems to work for me...
You'll also need the set the var DIFxAppPath
I got this to work in WiX3 by linking to WixDifxAppEntension and adding the
Custom Actions manually:
Those DLLs are from Difx distribution.
bg
On Tue, 02 Oct 2007 09:08:10 -0700, Bob Arnson <[EMAIL PROTECTED]> wrote:
> bcs wrote:
>> I am trying to install
Hi Folks -
I've run in to some weirdness with an installation package when trying to
modify an existing installation.
In Add/Remove Programs, both the Change and Remove buttons are displayed ...
but the Change button doesn't work as expected.
When the Change button is clicked, the installation
I guess that's arguable. I already had to provide all those details
(service name, startup information, etc.) in the EXE itself, in order to
support the /install, /remove, /start and /stop switches. Why would I
want to repeat that in the installer, instead of just calling the EXE?
Thanks and best
bcs wrote:
> I am trying to install a driver using Wix 3.0 and DifxAppExtension.
> When I build my installer I get this linker error:
>
> Unresolved reference to symbol 'CustomAction:MsiProcessDrivers'
>
Difx doesn't currently support WiX v3. The Difx extension exists for
when they support it.
Ben Greenberg wrote:
> But, since MsiProcessDrivers is declared in the Difx MSM, light doesn't know
> about it and complains that CustomAction:MsiProcessDrivers is an unresolved
> symbol reference.
>
> Is there a way to do this in WiX?
>
No. WiX merges the module's contents via mergemod.dll a
Cristian Baiu wrote:
> So far I don't know how to instruct pyro to address my patch to all
> MSIs unless I make differences for
> all of them and pass all these difference sets to pyro.
> Can you please advice me if it's possible to target multiple MSIs with
> only one set of differences and how ?
Gonzalo Diethelm wrote:
The only reason not to use ServiceInstall and ServiceControl is the
DRY principle (Don't Repeat Yourself).Since I MUST provide a way for
users to start/stop/install/delete the service from the console, I
don't want to replicate that mechanism anywhere else, hence the ver
Srinivas Tirupati wrote:
> Biut this is not working
>
How?
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/M
Anidil wrote:
> and in the WiX installer source file.
> and i add My_WixUI_InstallDir.wixlib,which is a custom library to the light
> command line,
> and have followed the instructions given in the WiX tutorial to create
> custom library..
> I get the same error though.any comments?
>
The err
..\ is the syntax for one folder up from the current folder.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jessi
Darling
Sent: Tuesday, October 02, 2007 8:47 AM
To: wix-users
Subject: [WiX-users] Reference one directory up.
How do you speci
Use heat.exe instead
On 02/10/2007, Sergei Shelukhin <[EMAIL PROTECTED]> wrote:
> Hi. How come there's no tallow utility in Wix 3.0 binaries?
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsof
It's been replaced by a similar tool called "heat".
rrraven wrote:
>
> Hi. How come there's no tallow utility in Wix 3.0 binaries?
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) V
Tallow doesn't exist in WiX 3.0. Take a look at Heat.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergei Shelukhin
Sent: Tuesday, October 02, 2007 8:36 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] no tallow in wix 3.0
Hi. How come there's no tallow utility in Wix
Massive thanks guys for your help ... in the end it was a simple spelling error
which didn't show up in the compile stage...
The additional information and guidance (such as using Orca) certainly
helped to tie it down and will be very useful going forward,
Also the -sice:ICE03 flag does suppress
How do you specify where your files are located when you don't want to hard
code the directory, just have it point to one directory up?
Thanks in advance.
--
Jessica Darling
-
This SF.net email is sponsored by: Microsoft
Def
Okay I figured it out... you need to ommit the transform's file extension.
In my example, just call the file "1036" and embed this.
--
View this message in context:
http://www.nabble.com/Embedded-locale-transforms-tf4523004.html#a13001287
Sent from the wix-users mailing list archive at Nabble.c
Hi. How come there's no tallow utility in Wix 3.0 binaries?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Hi,
I get the following error when running the Candle.exe in the WiX Release
3.0.3328.0 :
Unhandled Exception: System.IO.FileLoadException: Could not load file or
assembly 'wix, Version=3.0.3328.0, Culture=neutral,
PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located
assemb
OneReallyCoolApplication wrote:
>
> I am supposed to create a MSI package using WiX that can detect whether
> the computer it's on has 32-bit or 64-bit architecture, and install
> different files for each.
>
I believe that this is possible (using the VersionNT64 property) *provided
you're not t
The MSDN Windows Installer documentation should be sufficient to explain
this limitation. I'd start here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_on_64_bit_operating_systems.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ms
Presumably though, one can have an x64 and an x86 MSI, and a
boot-strapper that detects architecture and runs the correct MSI?
Yes, definitely.
John
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Micr
Presumably though, one can have an x64 and an x86 MSI, and a boot-strapper that
detects architecture and runs the correct MSI?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Gantoi
Sent: 02 October 2007 14:54
To: OneReallyCoolApplication; wix-users@lists.sourceforge.net
Sub
What you can do with MSI :
- create an installer which will install Win32 components on Win32 platforms
- create an installer which will install x64 and/or Win32 components on x64
platforms
You can't however create a single MSI for both Win32 and x64 platforms.
Because a MSI must be specified as "
The latest nightly build, version 3.0.3328.0, seems to be broken -
specifically there seems to be a problem with the strong name signing:
Unhandled Exception: System.IO.FileLoadException: Could not load
file or assembly 'wix, Version=3.0.3328.0, Culture=neutral,
PublicKeyToken=ce35f76fcda8
I am trying to install a driver using Wix 3.0 and DifxAppExtension.
When I build my installer I get this linker error:
Unresolved reference to symbol 'CustomAction:MsiProcessDrivers'
My Wix source code is shown below.
Can anyone help me find out how to avoid this linker error?
Thanks
Bo
http:
I am trying to install a driver using Wix 3.0 and DifxAppExtension.
When I build my installer I get this linker error:
Unresolved reference to symbol 'CustomAction:MsiProcessDrivers'
My Wix source code is shown below.
Can anyone help me find out how to avoid this linker error?
Thanks
Bo
http:
Bob Arnson wrote:
It will update the shared component but it won't update the other product,
so a repair operation can "undo" the patch. That's why merge modules are
falling way out of favor...
Hello Bob,
Thanks for your clarification.
It seems I will have to adress all the products using the MSM
Hi,
I want to use a custom action to fill dynamically a combobox. But I do not know
how the output of the custom action should look like. I only think to know that
I have to bind a property to the ouput to get the selected item of the combobox.
Regards, Peter
---
55 matches
Mail list logo
