Hi,
I run my insaller (e.g. msiexec /i XYZ.msi). Select a network path to install
(e.g. \\somecomputer\someshare\installdir). Product is installed with success.
Now delete the network path. Run the installer again. It returns 1606 saying
that could not access the network location. Installer
Hi all,
I want to know how the iis:mimemap tag works, it seems to need an id but do not
know how to add an MIME element although in the helpfile is written that it
schould be child of Wix tag.
Second thing is that I want to add a wildcard mime (after I know how to add a
MIME to a
It gets even stranger.
For some reason, it does uninstall properly when I start the msi from an
admin command prompt like this:
msiexec /i setup.msi /l*vx admin.log
but if I start it from a non admin account like this:
msiexec /i setuprip.msi /l*vx nonadmin.log
it leaves behind the items an
Hi
I need my installer to install the font Wingdings3 on install
Any ideas?
Thanks
--
View this message in context:
http://www.nabble.com/Install-a-Font-tf4717844.html#a13486672
Sent from the wix-users mailing list archive at Nabble.com.
The recommended way to do this is to create language transforms and then
call the msi from a setup.exe bootstrapper which will pass the correct
transform name along as a command line parameter. You'd have to add a
dialog in the bootstrapper to choose the language or include the logic to
determine
No it isn't. It will work if I put the box in the UI during the setup and
have it checked. If it is placed in the uninstall sequence however it will
not acknowledge the box is checked.
Bob Arnson-6 wrote:
xyavier wrote:
boB, It does however bring up my UI when someone clicks the change
hi
in my product the installation takes place in many modes.
there z a set of features in this product.
each mode support some mandatory features and some optional fearture.
there are some feartures which are not supported in some mode decided by
their installation condition.
i used
It turns out, the problem was because I was installing a component based on
the existence of a file on the end users computer, like this.
Property Id=DEPFOUND
DirectorySearch Id=deppath Path=[SystemFolder]
FileSearch Id=depfile Name=depfile.dll /
/DirectorySearch
Would adding 'Or Installed' to the condition work as well? Wouldn't it
then remove the file if it's there, and leave it if it isn't?
Kelly
Anthony Wieser [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/30/2007 08:00 AM
To
wix-users@lists.sourceforge.net
cc
Subject
Re: [WiX-users]
If I add the XmlConfig in my wxs my 2 customactions no longer work because
the customaction.Installstate can not be found. When I remove the XmlConfig
element everything is fine.
I need to delete and otherwise manipulate the web config and XmlFile is not
enough.
Here is the element:
It's not my file. I'm modifying a registry entry based on whether I find a
file in the system folder.
Anthony Wieser
Wieser Software Ltd
- Original Message -
From: Kelly Leahy
To: Anthony Wieser
Cc: wix-users@lists.sourceforge.net ; [EMAIL PROTECTED]
Sent: Tuesday,
Craig0ss wrote:
I need my installer to install the font Wingdings3 on install
Check with its developer to see if they provide a redist:
http://www.ascendercorp.com/msfonts/wingdings3.html.
--
sig://boB
http://joyofsetup.com/
shambhu kumar wrote:
now i want to disable the showing of fetures in selection tree used in
custom setup if this feature is not supported in tis particular mode(i.e its
installation condition is false).
The selection tree control doesn't support that -- features can only be
hidden, not
xyavier wrote:
No it isn't. It will work if I put the box in the UI during the setup and
have it checked. If it is placed in the uninstall sequence however it will
not acknowledge the box is checked.
How are you using the check box value?
--
sig://boB
http://joyofsetup.com/
I just meant that the component wouldn't be excluded on maintenance if you
had 'or Installed' regardless of the value of DEPFOUND, but perhaps it
wouldn't work.
Kelly
Anthony Wieser [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/30/2007 08:41 AM
To
wix-users@lists.sourceforge.net
cc
Hi. Thanks for the reply.
But isn't it true that the DLL itself should be registered, since the
.MSC acts as a configuration/shortcut to the actual snap-in, which
resides in a DLL. I deployed the MSC, but I am just getting Snap-in
failed to initialize and Snap-in creation failed messages when I
In article [EMAIL PROTECTED],
xyavier [EMAIL PROTECTED] writes:
No it isn't. It will work if I put the box in the UI during the setup and
have it checked. If it is placed in the uninstall sequence however it will
not acknowledge the box is checked.
OK, you know there's no such thing as
In article [EMAIL PROTECTED],
Sankaranarayanan [EMAIL PROTECTED] writes:
I am using Managed Custom Action [...]
What is your custom action doing? The MSDN documentation leads people
to believe that they need managed custom actions for all sorts of
things that the standard actions and
This is how it is set up
--
Control Id='All_Files' Type='CheckBox' X='10' Y='30' Width='400'
Height='18' Property='DELALL' CheckBoxValue=1
TextCheck the box to Delete extensibility.dll/Text
/Control
Control Id='RemoveNow'
This is how it is set up
--
Control Id='All_Files' Type='CheckBox' X='10' Y='30' Width='400'
Height='18' Property='DELALL' CheckBoxValue=1
TextCheck the box to Delete extensibility.dll/Text
/Control
Control Id='RemoveNow'
I use custom action for the following operations
1) Read XML Config file and set installer properties
2) Install Device Drivers
3) Loading MOF
4) Setting Windows Service privileges
5) Installing .NET Perf Counters.
etc...
WiX doesn't support these actions by default.
Please let know if you
I am packaging an MSI that I would like to have perform a Major Upgrade
when deployed on a machine with an older version of said package already
installed.
My setup:
* Product Id is set to ----
* Upgrade Code is set to some GUID which does not change
* The Upgrade
I am trying to share a directory to a group of users rather than a particular
user, i.e. the Administrators group on the local machine
([ComputerName]\Administrators). However, the Permission element within a
FileShare must point to a User. From the Tramontana tutorial, you can set
the User's
It appears that the Wix Certificate file-based installation and the Overwrite
option are currently incompatible. If a Certificate element is configured with
Request=no and Overwrite=yes and CertificatePath=PathToCertificateFile,
installation will fail. The error logged is Invalid
The problem is the sequencing. By the time InstallFinalize has happened,
the install is already committed, so you can't roll back the install of
version 2, at least if I'm understanding it correctly. You probably want
your RemoveExistingProducts to be somewhere earlier in the sequence, so
I have used the ServiceControl element as below:
ServiceControl Id='ADService' Name='XYZ AdminConsole' Start='both'
Stop='uninstall'/
I have logged on as Administrator and XYZ AdminConsole is running.
Now if I run my MSI package, it is failing and showing: Service 'XYZ
Whenever I run a tool in version 3307, 3328 or 3419 builds obtained from
wix.sourceforge.net/releases, I get a System.IO.FileLoadException
(0x80131040) saying that the wix assembly could not be loaded. Turning on
the binding logging gives this information:
=== Pre-bind state information ===
LOG:
I thought I'd sent a message on this one but must have deleted a draft.
There are two sorts of MMC snap-in:
MMC 3.0 only: .NET 2.0 classes which inherit
Microsoft.ManagementConsole.SnapIn
All versions: COM objects which implement IComponent and IcomponentData (not
to be confused, in .NET, with
Managed custom actions are officially unsupported by Windows Installer
because of the way that the CLR 'taints' the process it loads into. You
cannot reliably ensure that the correct CLR version is loaded at the correct
time. See Rob's blog post
In article [EMAIL PROTECTED],
Kelly Leahy [EMAIL PROTECTED] writes:
The problem is the sequencing. By the time InstallFinalize has happened,
the install is already committed, so you can't roll back the install of
version 2, at least if I'm understanding it correctly. You probably
In article [EMAIL PROTECTED],
shapla [EMAIL PROTECTED] writes:
I have used the ServiceControl element as below:
ServiceControl Id='ADService' Name='XYZ AdminConsole' Start='both'
Stop='uninstall'/
But didn't you say you wanted to *restart* the service? The calls for
a
See
http://www.microsoft.com/typography/fonts/font.aspx?FID=39FNAME=Wingdings%2
03FVER=1.55 for a list of Microsoft products that this font ships with. If
you can rely on one of these being installed, you won't need to ship it
yourself. This table doesn't appear to have been updated for the 2007
In article [EMAIL PROTECTED],
xyavier [EMAIL PROTECTED] writes:
This is how it is set up
Well, I think you're going to have to dig into log files and your MSI
with Orca instead of just relying upon inspection of WiX fragments to
debug this problem.
Have you tried that?
--
The Direct3D
iis:MimeMap is only for setting the MIME type for a given file extension.
This governs what IIS will send in the Content-Type header for static web
content. It sounds like you need to add an ISAPI filter and as far as I can
see, you need to do this with a WebApplicationExtension element.
I'm
A given package can only be localized into one language. One approach that
you can take to save space is to ship the package in one language with a
number of transforms (.mst) which, when applied, translate the package into
other languages. Microsoft have used this approach before and it's the
In article [EMAIL PROTECTED],
Mike Dimmick [EMAIL PROTECTED] writes:
[...] Microsoft have used this approach before and it's the
recommended one in the SDK. See Localizing a Windows Installer Package at
http://msdn2.microsoft.com/en-us/library/aa369769.aspx.
This thread had me looking
The INSTALLDIR property will be modularized by WiX when building the MSM, so
when the final package is executed, [INSTALLDIR] will not evaluate to the
place you thought it would.
If it's a file you're installing, using [#fileid] is a better option than
forming the path yourself. See the
I have tried like below just to stop a service:
ServiceControl Id='PMService' Name='XYZ AdminConsole' Stop='install'
Wait='yes'/
Installation goes on without any error, but the service is not stopped. I
can stop the same service from command prompt(net stop XYZ AdminConsole)
Any idea?
In article [EMAIL PROTECTED],
shapla [EMAIL PROTECTED] writes:
Any idea?
What does the log say?
--
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
http://www.xmission.com/~legalize/book/download/index.html
Legalize Adulthood!
In article [EMAIL PROTECTED],
Aris Green [EMAIL PROTECTED] writes:
I have been using managec C++ CA's coded in Visual Studio 2003 for
installs.
IMO, you might as well just use native C++ at that point.
Well, you get the picture. One wrinkle, the VC 2005 requires linking to the
C++
[dropping wix-devs]
John Hancock (HSG) wrote:
It appears that the Wix Certificate file-based installation and the
Overwrite option are currently incompatible. If a Certificate element
is configured with Request=no and Overwrite=yes and
CertificatePath=PathToCertificateFile, installation
I have been using managec C++ CA's coded in Visual Studio 2003 for
installs. You create a .NET dll and use unmanaged exports .e.g
__declspec(dllexport) int __stdcall MyCustomAction(MSIHANDLE hInstall);
All your logic is in the installation package and you don't have to leave a
carcass behind with
xyavier wrote:
Component Id='MyComponent' Guid='BLah BLah BLah-123456789012'
Condition
DELALL = 1
/Condition
RemoveFile Id='LogFile' On='uninstall' Name='*.*' /
RemoveFolder Id='TheDir' On='uninstall'/
Hey WiX Folks,
If I am not wrong, WIXv3 Toolset produces Windows Install v3.1 MSI. I also
remember some blogs where WIX Team have met with MSI Team to do the
enhancements to WIX Toolset to use new features of MSI 4.0.
Can you answer the following?
1)WIXv3 Current Build produces MSI v3.1.
Laxmi Narsimha Rao Oruganti (SQL CE) wrote:
If I am not wrong, WIXv3 Toolset produces Windows Install v3.1 MSI. I
also remember some blogs where WIX Team have met with MSI Team to do
the enhancements to WIX Toolset to use new features of MSI 4.0.
Can you answer the following?
1)
Mike Dimmick wrote:
Whenever I run a tool in version 3307, 3328 or 3419 builds obtained from
wix.sourceforge.net/releases, I get a System.IO.FileLoadException
(0x80131040) saying that the wix assembly could not be loaded.
It's a known issue and the WiX buildmeisters are working on the fix
46 matches
Mail list logo
