Hi Guys,
I am trying to overcome the headaches involved with maintaining the
dialogs for our MSI solutions and so have looked at the managed code
path.
While I know some of you will shun me for such a solution, I am merely
experimenting with the concept of using managed code to overcome one of
Something like this works for me:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=FontsFolder /
/Directory
DirectoryRef Id=FontsFolder
Component Id=MyFont.ttf Guid=YOUR-GUID-HERE
File TrueType=yes Name= MyFont.ttf KeyPath=yes /
/Component
Here is a complete sample which works with my fonts
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Id=a4ef658f-664b-45f9-8599-cdb70a87de99 Name=TrueType Font
Install Language=1033 Version=1.0.0.0 Manufacturer=Stefan Weber
Could anyone help me out with this ?
Thanks,
Stefan
-Ursprüngliche Nachricht-
Von: Weber Stefan (IT) [mailto:s.we...@noerr.com]
Gesendet: Dienstag, 10. März 2009 13:02
An: General discussion for Windows Installer XML toolset.
Betreff: [WiX-users] Self repair of files in user profile
Hi there
I have added a condition that disables the Next button on the installdir
dialog if the dest path is windows root drive.It works fine with next button
click.But if the user press Enter without changing the pathEdit focus, the
condition doesn't get evaluated and the UI get navigated to
how to automate version number
The best way IMO is to put the version information into a seperate
small file.
Something like this:
?xml version=1.0 encoding=utf-8?
Include
?define ApplicationVersion = 3 ?
?define MajorVersion = 1 ?
?define MinorVersion = 0 ?
?define
I tend to use the binding code and set the version number to the same
version as the primary file I am installing, e.g.:
?define Version = !(bind.fileVersion.MyApplication.exe) ?
Product Id=$(var.ProductCode) ...
Neil
-Original Message-
From: Tency Kuruvilla
Hello,
I think I found it myself :-)
The problem was:
I had two features. The first feature actually installs all the files and
creates the shortcut.
In the second feature I did all the configuration stuff.
Now I added the component from the second feature to the other one, so that
there is
Has anyone else ran xsd on wix.xsd to create a cs file? I'm trying to
automate the creation of my wix files but now need to add support for
iis. In a manually created file I included:
Xmlns:iis = http://schemas.microsoft.com/wix/IIsExtension; - to try and
replicate this I attempted to use line
Paragraph 2 should of course have referred to line 7. Apologies
Norman Lough
Developer
Tel: +44 (0)191 213
DDI: +44 (0)191 2028360
Email: norman.lo...@imass.co.uk
Imass Ltd, Northumbria House, Regent Centre, Gosforth, Newcastle upon
Tyne, NE3 3PX. http://www.imass.co.uk
The Microsoft reference on the CreateFolders Actions says The installer
creates folders both for components that run locally and run from source.
Doesn't this mean CreateFolders is officially approved for use during Admin
Installations? (See below for link)
If the AdminExecuteSequence is
hi,
i have a scenario as described below:
1. need to capture the DBSERVER on the fly.
2. need to capture *DBNAME* on the fly.
3. need to run a script which creates a database named *DBNAME.*
*4*. need to run another sql script which uses this DBNAME and run some
commands.
now the problem i am
Problem sorted. If anyone else is doing this sort of thing:
XmlSerializer writer = new XmlSerializer(typeof(Wix));
XmlSerializerNamespaces ns = new XmlSerializerNamespaces();
ns.Add(iis,
http://schemas.microsoft.com/wix/IIsExtension;);
I have added actions to the PushButtons. But i am receicving following errors:
ICE17: ICE Internal Error 105. API Returned: 1615.
ICE17: Error 2228: C:\Dokumente und Einstellungen\Thomas Bahn\Lokale
Einstellungen\Temp\v5eyv_-k\Cic.P04.WiXSetup.msi, ControlCondition, SELECT
I can offer some general suggestions. First, I assume that you will be using
osql or sqlcmd to execute the SQL inside of a custom action.
If you use sqlcmd, it can process scripting variables, which are basically
on-the-fly text substitions.
If you are using osql, I would recommend writing your
i am gettin the following error
failed to create SQL database: AkashDB, error detail: CREATE DATABASE
failed. Some file names listed could not be created. Check related errors..
this is how i am doing my stuff
Component Id =RUNSQL Guid =my-guid
sql:SqlDatabase Id =sqldb Database
In common with a lot of build processes ours uses a 4 part version
number, major.minor.day.revision, in a given day the revision can change
if the developers rebuild but the shipping product would never have the
same major.minor.day version. This causes a problem with Windows
Installer major
Are you getting this error from a verbose installer log? If so, including
the LOGVERBOSE=1 property on the command line might give more information.
I would also use SQL Profiler to capture what exactly is getting sent to the
SQL Server. This will probably be enlightening.
On Wed, Mar 11, 2009
Is there any way to get the directory in which the msi is executing from?
If we copy the MSI to c:\foo, i'd like to copy files to c:\foo without the
user having to specify this directory via Feature ConfigurableDirectory=
/.
I thought there might be an internal directory ID .. like CURRENTDIR ..
Hi All,
My installation needs to install several thousand files, most of which
are quite small. I can use heat to harvest these, but this isn't great,
because if a file changes I am in trouble. Furthermore, I have several
root folders, each of which constitutes a feature. If I run heat on
Nick,
It looks like the latest version of Heat can do a much better job:
http://icumove.spaces.live.com/blog/cns!FB93073C6534B681!461.entry.
Another option is a tool I created called Paraffin to make it easier. Here's
where you can get it:
Hey Nick,
Are you using the latest version of Heat.exe? You could set it up to harvest
sections of files using the -cg MyGroup command and then include that output
into your feature.
http://icumove.spaces.live.com/blog/cns!FB93073C6534B681!461.entry
Brian Rogers
Intelligence removes complexity. -
Hi,
I have a Wix 3 installer which has a UI written in C# using the DTF.
I'm aware that the actions in the InstallUISequence will not be executed
if I use a custom UI in this way, but does anyone know how I can force an
action (specifically AppSearch) to run from within the UI? I've tried using
Hello Rob,
I'm sorry for recovering this old thread, but it turned out to be a
(major) bug in the IIS extension. I have registered an artifact to the
bug database
(https://sourceforge.net/tracker/index.php?func=detailaid=2683227group
_id=105970atid=642714), but to tell the long story short, IIS
Hello,
I use Wix version 3.0.5106.0.
I encounter an error when I try to add the LocalSystem to the IIS_WPG
group on Windows 2003. The full error message is :
Failed to add user to group. (-2147023509 LocalSystem IIS_WPG )
The User element is declared as following:
util:User
Bahn Thomas wrote:
What PushButtons i need in FilesInUseDialog?
See ICE20 in the MSI SDK.
--
sig://boB
http://joyofsetup.com/
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering
Andy2k8 wrote:
I have added a condition that disables the Next button on the installdir
dialog if the dest path is windows root drive.It works fine with next button
click.But if the user press Enter without changing the pathEdit focus, the
condition doesn't get evaluated and the UI get
Bertrand Fritsch wrote:
I thought LocalSystem, as well as NetworkService and LocalService, were
names that the Wix extension translates into well-known SIDs when it
interacts with the operating system. Am I wrong? Does it not apply here?
The custom actions behind the User element doesn't
jnewton wrote:
Is it possible to add custom attributes to the Directory element?
At the moment, no; the compiler has to explicitly support extension
attributes and it doesn't for Directory elements. Please file a feature
request.
--
sig://boB
http://joyofsetup.com/
Neil Sleightholm wrote:
This works but is it a really bad thing to do?
It means that it's still possible to install an earlier version. If
they're never released, it's only a problem for your internal folks.
--
sig://boB
http://joyofsetup.com/
martin lavelle wrote:
The Microsoft reference on the CreateFolders Actions says The installer
creates folders both for components that run locally and run from source.
Doesn't this mean CreateFolders is officially approved for use during Admin
Installations?
No. I think you're still
Lough, Norman wrote:
Has anyone else ran xsd on wix.xsd to create a cs file? I'm trying to
automate the creation of my wix files but now need to add support for
iis.
WiX already supports that; see the
Microsoft.Tools.WindowsInstallerXml.Serialize namespace.
--
sig://boB
If I write custom action to detect Server 2008 Core installation where
should I schedule it?
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform
I have never liked the behavior of enabling/disabline push buttons. Instead
of disabling/enabling the control, you might consider publishing multiple
events for the push button. You can control the order of the events, which
allows you to do validation with three events.
The first event runs a
Where to schedule the CA depends on how you intend to use the results. If
you want to use it to prevent installation, you should schedule it before
LaunchConditions as an immediate CA and use a Condition element based on the
property set by the CA.
- Don Benson -
On Sun, Mar 8, 2009 at 11:43
I'm not sure you can do what you want to do with a custom action, either
managed or unmanaged. At least I've never seen it done. However I'm not at all
an expert on installer UI dialogs and events.
InstallMessage.ShowDialog is not valid for Session.Message/MsiProcessMessage.
It is only used by
The error is:
1387
ERROR_NO_SUCH_MEMBER
A new member could not be added to or removed from the local group
because the member does not exist.
So, I'm guessing that NetGroupAddUser / NetLocalGroupAddMembers don't
like the name LocalSystem; those API's expect SYSTEM (although they
are case
It sounds like either the SourceDir property or OriginalDatabase (with some
parsing) is what you want.
Phil Wilson
-Original Message-
From: troy hostetter [mailto:troy.hostet...@gmail.com]
Sent: Wednesday, March 11, 2009 8:17 AM
To: General discussion for Windows Installer XML
I think that's the case, yes, IIRC. A component repair results in a resiliency
check for the containing feature. .
Phil Wilson
-Original Message-
From: Weber Stefan (IT) [mailto:s.we...@noerr.com]
Sent: Wednesday, March 11, 2009 3:05 AM
To: General discussion for Windows Installer
Good point, that could even be considered a useful feature downgrades
without an uninstall.
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 11 March 2009 17:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Major Upgrades
This is what I have:
Condition Message=Windows Server Core is not supported
NOT ServerCore
/Condition
CustomAction Id=DetectServerCoreAction
BinaryKey=InstallActions
DllEntry=DetectServerCore
Return=check /
InstallExecuteSequence
Custom
According to the MSI docs, .ico can be transparent. Does this mean they can
be transparent only on top of text and control, or also on top of a
background image (jpg) ?
And I have verified that .ico file has transparency info there using
external image viewers.
However, in MSI once built from
Look at the CustomAction/@Execute attribute. This should be set to
firstSequence or Immediate. If you have a UI on your installer, I would use
firstSequence, in which case you will want to schedule the custom action in
both InstallExecuteSequence and InstallUISequence.
- Don Benson -
On Wed, Mar
Adding it to InstallUISequence fixed it. Thanks.
-Original Message-
From: Don Benson [mailto:dbenso...@gmail.com]
Sent: Wednesday, March 11, 2009 14:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting Server 2008 Core
Look at the
I didn't see any replies to this. I'm having the same problem. I
figured out the cause, but I'm not sure on what to do for a solution.
The problem is that windows does a redirect to the syswow64 folder, and
the applicationHost.config file doesn't exist there. So it can't be
accessed by anything
Hi all,
I am new on wix. I want to include some of the public assemblies from the
GAC into the setup but
I don't the way how to define the source for such files in FILE or is
there an y other tag that I can use to include such files.
The MSI built by the Visual studio somehow detects all these
I don't think you'd get a downgrade you would like. I think you would
end up with a mush of the two slightly different versions of the
application because of the component versions.
Example:
V1 - has component 21 with ver 1.1.27
V2 - has component 21 with ver 1.2.0
You try to reinstall V1
Hi Jason,
Thanks for the input. Perhaps I really am approaching this in the wrong
direction. From what I can tell from the Office 2007 installer is they
have a bootstrapper and UI bundled into a exe, which invokes MSI's which
have no UI. To be honest this would have been the direction I would
the error which i mentioned ... i got it from verbose log itself...
Please let me know, if some one can help me on this
thnks!
Akash
On Wed, Mar 11, 2009 at 8:36 PM, Don Benson dbenso...@gmail.com wrote:
Are you getting this error from a verbose installer log? If so, including
the
Akash
First check the application event log (for a failure error from
MSInstaller), the full text of the SQL error is there (I am assuming
that the Check related errors.. means you are reading this error from
the error dialog).
I suspect there is an MDF or LDF file hanging around in the SQL
50 matches
Mail list logo