Windows Installer XML (WiX) toolset

I also managed to call "aspnet_regiis.exe -sn W3SVC/1/Root/[folder]" using
CAQuietExec action. But I still have problem with it.

I haven't found proper stage of the installation to call it. It seems to work
for After="InstallFinalize" only which is a bit late. The progress bar does
not get updated during the call and there is no text message saying what's
actually in progress. The dialog is just "stuck" for a while which looks
confusing. Next problem has raised when the aspnet_regiis.exe call failed
because the installation is not rollbacked in such case. I have tried to start
the action in Before="InstallFinalize" but it was too early and returned an
error immediately. Is there any better solution ?

Thanks, Petr.

----- Original Message ----- 
From: "Joannic Laborde" <jlaborde@...>
To: "Frederik Carlier" <frederik.carlier@...>; "Petr Vones"
<petr.v@...>; <wix-users@...>
Sent: Thursday, January 26, 2006 5:41 PM
Subject: RE: [WiX-users] How to set ASP.NET version of a WebApplication ?


I'm calling aspnet_regiis.exe as a custom action, and it's working
pretty well. I'm also checking if ASP.NET is registered to IIS, using
this value:
HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer

I have been using that approach for almost a year without any problems.=20

Paul
=20

-----Original Message-----
From: wix-users-admin@...
[mailto:wix-users-admin@...] On Behalf Of Petr Vones
Sent: Monday, January 30, 2006 3:47 PM
To: wix-users@...
Subject: [WiX-users] Installing .NET windows service

I use ServiceInstall element to install a .NET windows service. Is this
a correct way compatible with .NET InstallUtil tool ? I guess the
ServiceInstall element is designed to install a Win32 windows service.
It seems to work for .NET one as well but I'd like to make sure it won't
make any problems.

Thanks, Petr.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems?  Stop!  Download the new AJAX search engine that
makes searching your log files as easy as surfing the  web.  DOWNLOAD
SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=3D=
121642
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

I use ServiceInstall element to install a .NET windows service. Is this a
correct way compatible with .NET InstallUtil tool ? I guess the ServiceInstall
element is designed to install a Win32 windows service. It seems to work for
.NET one as well but I'd like to make sure it won't make any problems.

Thanks, Petr.

A curious issue:

I have an installer that uses the XmlFile tag, and everything seems to 
install flawlessly...when the .MSI is executed on a system that has an 
open connection to the internet.  One of our test machines is behind a 
pretty restrictive firewall, and when we try to install it on that 
system, we get the following error:

    ExecXmlFile:  Error 0x8007006e: failed to load XML file:  C:\Program 
Files\Thingy 
4.0.2\Oracle\OC4J\j2ee\home\application-deployments\atlass\atlass-web\orion-web.xml

At which point, the install fails, and everything backs out.

I can replicate this on several other machines by simply pulling the 
network cable out of the NIC.  So apparently, when XmlFile attempts to 
modify the .xml file, it loads the validator, and that attempts to 
retrieve the .dtd externally.

Here's the xml file:

<?xml version="1.0"?>
<!DOCTYPE orion-web-app PUBLIC "-//ORACLE//DTD OC4J Web Application 
9.04//EN" "http://xmlns.oracle.com/ias/dtds/orion-web-9_04.dtd">

<orion-web-app deployment-version="9.0.4.0.0" 
jsp-cache-directory="./persistence" temporary-directory="./temp">
    <context-param-mapping name="installDirectory"></context-param-mapping>
    <security-role-mapping name="THINGY"/>
    <security-role-mapping name="GUEST"/>
</orion-web-app>

I've looked at the WIX .CHM file, and don't see any option to turn off 
external validation.  Am I completely off-base, here?

Thanks!

Ian Coleman

That sounds great, since the documentation can always improve but few
people actually want to work on that.

As far as I know, you need to sign the Copyright Assignment Agreement to
contribute to the documentation, so you may want to check that first:
http://blogs.msdn.com/robmen/archive/2004/04/14/112970.aspx.

Frederik.=20

-----Original Message-----
From: wix-users-admin@...
[mailto:wix-users-admin@...] On Behalf Of Martin
Lavelle
Sent: vrijdag 27 januari 2006 19:47
To: wix-users@...
Subject: [WiX-users] Offer of Documentation Help

Hello,
By profession, I am a software packager.
Over the past year, I have used WIX heavily in a large complex
development project. Despite its Beta status and incomplete
documentation, I felt obliged to use WIX because:
1 It supports most of the technologies that I needed to deploy.
2 Any Developer could easily understand what was going on (Thanks to
Fragments and a straight forward notation).
3 I found unit testing and debugging easier with WIX, because it is easy
to move features and components between MSI's without disturbing the
code or using merge modules.
4 My client stipulated MSI, and to use a standard approach.
5 Your code is more likely to be bug free than mine would have been, and
writing deployment tools would be my last resort.
6 I had objections with alternative products.
As I have to document my work, it occurs to me that I can return
something to this project/community.
So if you are looking for help with documentation then please advise.

Regards


Martin Lavelle


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems?  Stop!  Download the new AJAX search engine that
makes searching your log files as easy as surfing the  web.  DOWNLOAD
SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=3D=
121642
_______________________________________________
WiX-users mailing list
WiX-users@...
https://lists.sourceforge.net/lists/listinfo/wix-users

I'm having a bit of a trouble with getting a CustomAction to execute.  
Here's my Wix code:


    <CustomAction
      Id="CustomAction_RunInstall"
      ExeCommand=" -i  dsm.inf  Root\FiiDsm  [TARGETDIR]"
      FileKey="File_DriversInstaller"
      Execute="commit"
      Return="check"
      Impersonate="yes">
    </CustomAction>


    <InstallExecuteSequence>
      <Custom
        Action="CustomAction_RunInstall"
        Before="InstallFinalize">
      </Custom>
    </InstallExecuteSequence>

The MSI log complains that the action cannot be executed because it must 
be executed between InstallInitialize and InstallFinalize.  I've tried 
various Before, After and Sequence settings but I always get the same 
error from the MSI execution and the same message in the log file. The 
MSI error is:

DEBUG: Error 2762:  Unable to schedule operation. The action must be 
scheduled between InstallInitialize and InstallFinalize.
The installer has encountered an unexpected error installing this 
package. This may indicate a problem with this package. The error code 
is 2762. The arguments are: , ,

I LOVE WiX because it allows me to avoid the dreaded Fischer-Price setup 
wizard in the IDE (which drives me nuts).  However, the IDE built setup 
does run a custom action post commit without any problems.  The strange 
part is that I can't find any evidence of the custom action in the MSI 
log after the install has completed.  That worries me...

TIA


-- 

Robert Randall
Proficient Solutions, Inc.
533 Clover Lane
Minneapolis, Minnesota 55426
US
voice  +1 612.216.1253
fax    +1 866.835.2144
mobile +1 612.770.9612

There are a couple of reasons we do not want to use ClickOnce. The main
one being, simply said, that we - need full MSI installer functionality.

So far we have been using WISE, and WISE has a (terribly done) automatic
update check, based on an INI file on a HTTP share. It is badly done
mostly because it asks every 2 weeks whether it should check, instead of
just checking (optionally) and telling the user to update. We get a lot
of complaints from users that do not want to be bothered with the dialog
popping up - especialyl as the sofftware in question is RARELY updated
(it is just a loader, so we update it basically once every half year or
so).

We thought about writing an automatic update mechanism ourselves. It
would be .NET based (not a problem for us - we anyhow require the .NET
framework to be installed, as our software is .NET). I am still
wondering whether:

* Is aonyone aware of any existing (open source) library for this?
* Can we hook somehow into the ClickOnce update mechanism? At least for
the download/version check? It would be great if we could somehow
integrate, but documentation is sparse on that topic, and the complete
ClickOnce thing just is "not my thing" here. I want ONE msi file,
downloaded, installed.
* What is the best way to do the regular checks? I sort of do not want
to hook up a schefuled task for every application.

I am particularly interested in any details how ClickOnce actually
handles the automatic check without the application being changed - that
mechanism looks interesting for us, too.

Any tips welcome.

Thomas Tomiczek

Well, it looks then like I will go on and use Wix 3. As long as someone
if willing to add fixes within a reasonable timeframe should we run into
problems (and I find this relatively unlikely - note that we do not do a
lot of stuff, basically, and are just pretty lame in our installers) I
think it will be workable.

Rolling out new Wix versions is not a problem we have. First of all, we
do not use Votive for pretty hard reasons so far - we do not do and
never want to do setup as part of the visual studio standard build
process. Not saying we could not use Votive (in separate solutions), but
bascialyl I do not want a setup to be triggerable from the source code
project. Setup comes at a different stage for us. Second, we have a
centrally maintained build environment anyway that is rolled out by
group policy. Right now we distribute Nant (and some extensions and
central build files) through this, and we can add Wix to this easily.
That means I can roll out new versions from a central location :-)

On a side-querstion - do you guys plan to actually get the drop creation
a little mor up to speed? The last drop is 13th of december. Doing
nightly autoamted builds seems to be getting out of favout (nant does
not do so anymore neither) - is there a reason for that?

Thomas

> -----Original Message-----
> From: wix-users-admin@...
> [mailto:wix-users-admin@...] On Behalf Of=20
> Derek Cicerone
> Posted At: Sonntag, 29. Januar 2006 23:08
> Posted To: wix-users
> Conversation: [WiX-users] (no subject)
> Subject: RE: [WiX-users] (no subject)
>=20
>=20
> It's completely up to you to decide if/when 3.0 is right for=20
> you.  We are officially suggesting people stay off it, at=20
> least for now because there hasn't really been any good=20
> testing yet.  This is mostly due to the fact that no one is=20
> using it yet.  So it's a bit of problem because we need some=20
> adventurous people to start using it in order to get the=20
> quality up.  We'd prefer that these adventurous groups having=20
> a ship date that is pretty far out in the future so that if=20
> they hit a problem, we have ample time to fix the issue properly.
>=20
> Another big problem with moving to 3.0 too early is that the=20
> schema is being moved around a little bit.  The=20
> File/@LongName attribute is deprecated, FragmentRef is=20
> deprecated, nesting Registry elements under one another will=20
> be deprecated, all server-based elements like WebPool,=20
> WebSite, ... have moved into an extension, etc...  If you=20
> move to 3.0 now, you risk having to update your source code=20
> every time you take a new drop of the toolset in order to=20
> keep it working properly.  Now, we've made a tool called=20
> WixCop which can automate updating your code to these latest=20
> schemas, but it will also completely dictate the style of=20
> your code be 2-space indentation, double-quotes for=20
> attributes, and no unnecessary whitespace.  So it's a bit=20
> disruptive the first time you use WixCop.
>=20
> Another problem with moving to 3.0 is that the wixlib and=20
> wixout files it produces are not compatible with WiX 2.0. =20
> You can use a wixlib file from 2.0 in 3.0, but not the other=20
> way around.  The wixout files are completely incompatible. =20
> So if you send wixlib files to another team, they need to=20
> upgrade to the same version of 3.0 that you are on in order=20
> to be able to use it.
>=20
> Derek
>=20
> -----Original Message-----
> From: wix-users-admin@...
> [mailto:wix-users-admin@...] On Behalf Of=20
> Thomas Tomiczek
> Sent: Sunday, January 29, 2006 9:28 AM
> To: wix-users@...
> Subject: [WiX-users] (no subject)
>=20
> Hm, when do you think people with some adventuring=20
> willingness could start using Wix 3.0? It looks like Wix 3.0=20
> will finally have some serious advantages over all the other=20
> stuff. As our setups are currently REALLY simple in their=20
> feature set (and it does not look like we are going to have a=20
> lot more complex stuff like db setup etc. soon), I would=20
> rather willingly try Wix 3.0.
>=20
> ESPECIALLY when we talk about features like getting rid of=20
> the terrible short names :-)
>=20
> I hope you check that one in soon. I have a couple of setups=20
> to make here. Inherently simple (create folder, copy dll's=20
> in, some shortcuts, some file stuff). Still I would really=20
> love and prefer not to have to deal with the idiocy of short=20
> file names. So your fix sort of really is something I am drooling for.
>=20
> Thomas
>=20
> > -----Original Message-----
> > From: wix-users-admin@...
> > [mailto:wix-users-admin@...] On Behalf Of Derek=20
> > Cicerone Posted At: Freitag, 27. Januar 2006 02:23 Posted To:=20
> > wix-users
> > Conversation: [WiX-users] Any ETA on the Short=20
> > Filenames=3DAutogeneratedHash fix?
> > Subject: RE: [WiX-users] Any ETA on the Short=20
> > Filenames=3DAutogeneratedHash fix?
> >=20
> >=20
> > This is a WiX 3.0-only feature.  We are currently=20
> discouraging people=20
> > from using WiX 3.0 until next year because this is the active=20
> > development branch (for instance - I recently found a two=20
> big problems=20
> > with auto-generation of registry identifiers).  WiX 2.0=20
> should be the=20
> > toolset for all products shipping this year.
> >=20
> > Beyond these warnings, I'm still holding onto the fix because I'm=20
> > worried that I'm missing something (I'm not sure what -=20
> it's just an=20
> > intuition).  We also need to have some discussions about how this=20
> > affects the nomenclature of other attributes like=20
> Directory/@Name and=20
> > Directory/@LongName.
> > I'll try to get it checked in within the next month.
> >=20
> > Derek
> >=20
> > -----Original Message-----
> > From: wix-users-admin@...
> > [mailto:wix-users-admin@...] On Behalf Of Thomas=20
> > Tomiczek
> > Sent: Thursday, January 26, 2006 1:36 AM
> > To: wix-users@...
> > Subject: [WiX-users] Any ETA on the Short=20
> Filenames=3DAutogeneratedHash=20
> > fix?
> >=20
> > OK :-)
> >=20
> > Anyone has an ETA (estimated time of arrival) when we will see the=20
> > automated generation of short filenames in a build? I am ready to=20
> > start WIX installers for about half a dozen projects here,=20
> and that is=20
> > pretty much a "taking half the work" from me thing. Like=20
> most others=20
> > here we do not support installation on short filenam only=20
> file systems=20
> > by any mean (due to the fact that our applications simply would not=20
> > run anyway), and having them to be determined was something that=20
> > really got on my nerves left and right in the whole windows=20
> installer=20
> > experience till now - from Installshield to Wise.
> >=20
> > Thomas
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log=20
> > files for problems?  Stop!  Download the new AJAX search=20
> engine that=20
> > makes searching your log files as easy as surfing the  web.=20
>  DOWNLOAD=20
> > SPLUNK!
> > =
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@...
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log=20
> > files for problems?  Stop!  Download the new AJAX search=20
> engine that=20
> > makes searching your log files as easy as surfing the  web.=20
>  DOWNLOAD=20
> > SPLUNK!
> > =
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@...
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files for problems?  Stop!  Download the new AJAX=20
> search engine that makes searching your log files as easy as=20
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files for problems?  Stop!  Download the new AJAX=20
> search engine that makes searching your log files as easy as=20
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>=20

I hate to complain about a volunteer effort, please think of this as
constructive criticism.  Overall, I think WiX is great but a couple of
the things you said about 3.0 didn't exactly thrill me.

First, why is File/@LongName deprecated?  Generating short names is a
great feature but, some of us specifically enter long and short names,
is that deprecated?  Why?

Also, WiXCop sounds like a great idea but not if it's going to dictate
my indentation size and usage of white space.  Why would it do that?

Thanks,

John Vottero


> -----Original Message-----
> From: wix-users-admin@...
> [mailto:wix-users-admin@...] On Behalf Of=20
> Derek Cicerone
> Sent: Sunday, January 29, 2006 5:08 PM
> To: 'Thomas Tomiczek'; wix-users@...
> Subject: RE: [WiX-users] (no subject)
>=20
> It's completely up to you to decide if/when 3.0 is right for=20
> you.  We are
> officially suggesting people stay off it, at least for now=20
> because there
> hasn't really been any good testing yet.  This is mostly due=20
> to the fact
> that no one is using it yet.  So it's a bit of problem=20
> because we need some
> adventurous people to start using it in order to get the=20
> quality up.  We'd
> prefer that these adventurous groups having a ship date that=20
> is pretty far
> out in the future so that if they hit a problem, we have=20
> ample time to fix
> the issue properly.
>=20
> Another big problem with moving to 3.0 too early is that the=20
> schema is being
> moved around a little bit.  The File/@LongName attribute is=20
> deprecated,
> FragmentRef is deprecated, nesting Registry elements under=20
> one another will
> be deprecated, all server-based elements like WebPool,=20
> WebSite, ... have
> moved into an extension, etc...  If you move to 3.0 now, you=20
> risk having to
> update your source code every time you take a new drop of the=20
> toolset in
> order to keep it working properly.  Now, we've made a tool=20
> called WixCop
> which can automate updating your code to these latest=20
> schemas, but it will
> also completely dictate the style of your code be 2-space indentation,
> double-quotes for attributes, and no unnecessary whitespace. =20
> So it's a bit
> disruptive the first time you use WixCop.
>=20
> Another problem with moving to 3.0 is that the wixlib and=20
> wixout files it
> produces are not compatible with WiX 2.0.  You can use a=20
> wixlib file from
> 2.0 in 3.0, but not the other way around.  The wixout files=20
> are completely
> incompatible.  So if you send wixlib files to another team,=20
> they need to
> upgrade to the same version of 3.0 that you are on in order=20
> to be able to
> use it.
>=20
> Derek
>=20
> -----Original Message-----
> From: wix-users-admin@...
> [mailto:wix-users-admin@...] On Behalf Of=20
> Thomas Tomiczek
> Sent: Sunday, January 29, 2006 9:28 AM
> To: wix-users@...
> Subject: [WiX-users] (no subject)
>=20
> Hm, when do you think people with some adventuring willingness could
> start using Wix 3.0? It looks like Wix 3.0 will finally have some
> serious advantages over all the other stuff. As our setups=20
> are currently
> REALLY simple in their feature set (and it does not look like we are
> going to have a lot more complex stuff like db setup etc.=20
> soon), I would
> rather willingly try Wix 3.0.
>=20
> ESPECIALLY when we talk about features like getting rid of=20
> the terrible
> short names :-)
>=20
> I hope you check that one in soon. I have a couple of setups to make
> here. Inherently simple (create folder, copy dll's in, some shortcuts,
> some file stuff). Still I would really love and prefer not to have to
> deal with the idiocy of short file names. So your fix sort of=20
> really is
> something I am drooling for.
>=20
> Thomas
>=20
> > -----Original Message-----
> > From: wix-users-admin@...
> > [mailto:wix-users-admin@...] On Behalf Of=20
> > Derek Cicerone
> > Posted At: Freitag, 27. Januar 2006 02:23
> > Posted To: wix-users
> > Conversation: [WiX-users] Any ETA on the Short=20
> > Filenames=3DAutogeneratedHash fix?
> > Subject: RE: [WiX-users] Any ETA on the Short=20
> > Filenames=3DAutogeneratedHash fix?
> >=20
> >=20
> > This is a WiX 3.0-only feature.  We are currently=20
> > discouraging people from using WiX 3.0 until next year=20
> > because this is the active development branch (for instance -=20
> > I recently found a two big problems with auto-generation of=20
> > registry identifiers).  WiX 2.0 should be the toolset for all=20
> > products shipping this year.
> >=20
> > Beyond these warnings, I'm still holding onto the fix because=20
> > I'm worried that I'm missing something (I'm not sure what -=20
> > it's just an intuition).  We also need to have some=20
> > discussions about how this affects the nomenclature of other=20
> > attributes like Directory/@Name and Directory/@LongName. =20
> > I'll try to get it checked in within the next month.
> >=20
> > Derek
> >=20
> > -----Original Message-----
> > From: wix-users-admin@...
> > [mailto:wix-users-admin@...] On Behalf Of=20
> > Thomas Tomiczek
> > Sent: Thursday, January 26, 2006 1:36 AM
> > To: wix-users@...
> > Subject: [WiX-users] Any ETA on the Short=20
> > Filenames=3DAutogeneratedHash fix?
> >=20
> > OK :-)
> >=20
> > Anyone has an ETA (estimated time of arrival) when we will=20
> > see the automated generation of short filenames in a build? I=20
> > am ready to start WIX installers for about half a dozen=20
> > projects here, and that is pretty much a "taking half the=20
> > work" from me thing. Like most others here we do not support=20
> > installation on short filenam only file systems by any mean=20
> > (due to the fact that our applications simply would not run=20
> > anyway), and having them to be determined was something that=20
> > really got on my nerves left and right in the whole windows=20
> > installer experience till now - from Installshield to Wise.
> >=20
> > Thomas
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> > through log files for problems?  Stop!  Download the new AJAX=20
> > search engine that makes searching your log files as easy as=20
> > surfing the  web.  DOWNLOAD SPLUNK!
> > =
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@...
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> > through log files for problems?  Stop!  Download the new AJAX=20
> > search engine that makes searching your log files as easy as=20
> > surfing the  web.  DOWNLOAD SPLUNK!
> > =
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@...
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web. =20
> DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web. =20
> DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>=20

Hm, when do you think people with some adventuring willingness could
start using Wix 3.0? It looks like Wix 3.0 will finally have some
serious advantages over all the other stuff. As our setups are currently
REALLY simple in their feature set (and it does not look like we are
going to have a lot more complex stuff like db setup etc. soon), I would
rather willingly try Wix 3.0.

ESPECIALLY when we talk about features like getting rid of the terrible
short names :-)

I hope you check that one in soon. I have a couple of setups to make
here. Inherently simple (create folder, copy dll's in, some shortcuts,
some file stuff). Still I would really love and prefer not to have to
deal with the idiocy of short file names. So your fix sort of really is
something I am drooling for.

Thomas

> -----Original Message-----
> From: wix-users-admin@...
> [mailto:wix-users-admin@...] On Behalf Of=20
> Derek Cicerone
> Posted At: Freitag, 27. Januar 2006 02:23
> Posted To: wix-users
> Conversation: [WiX-users] Any ETA on the Short=20
> Filenames=3DAutogeneratedHash fix?
> Subject: RE: [WiX-users] Any ETA on the Short=20
> Filenames=3DAutogeneratedHash fix?
>=20
>=20
> This is a WiX 3.0-only feature.  We are currently=20
> discouraging people from using WiX 3.0 until next year=20
> because this is the active development branch (for instance -=20
> I recently found a two big problems with auto-generation of=20
> registry identifiers).  WiX 2.0 should be the toolset for all=20
> products shipping this year.
>=20
> Beyond these warnings, I'm still holding onto the fix because=20
> I'm worried that I'm missing something (I'm not sure what -=20
> it's just an intuition).  We also need to have some=20
> discussions about how this affects the nomenclature of other=20
> attributes like Directory/@Name and Directory/@LongName. =20
> I'll try to get it checked in within the next month.
>=20
> Derek
>=20
> -----Original Message-----
> From: wix-users-admin@...
> [mailto:wix-users-admin@...] On Behalf Of=20
> Thomas Tomiczek
> Sent: Thursday, January 26, 2006 1:36 AM
> To: wix-users@...
> Subject: [WiX-users] Any ETA on the Short=20
> Filenames=3DAutogeneratedHash fix?
>=20
> OK :-)
>=20
> Anyone has an ETA (estimated time of arrival) when we will=20
> see the automated generation of short filenames in a build? I=20
> am ready to start WIX installers for about half a dozen=20
> projects here, and that is pretty much a "taking half the=20
> work" from me thing. Like most others here we do not support=20
> installation on short filenam only file systems by any mean=20
> (due to the fact that our applications simply would not run=20
> anyway), and having them to be determined was something that=20
> really got on my nerves left and right in the whole windows=20
> installer experience till now - from Installshield to Wise.
>=20
> Thomas
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files for problems?  Stop!  Download the new AJAX=20
> search engine that makes searching your log files as easy as=20
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files for problems?  Stop!  Download the new AJAX=20
> search engine that makes searching your log files as easy as=20
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>=20

Well, I found that I could work around the 'WindowsFolder" not existing
in the directory table (I'm gessing <Registry> processing requires
knowing where the Windows Folder is):
=20
I had to add an empty <Directory Id=3D"WindowsFolder" /> entry in *one*
fragment wxs file where <Registry> entries appeared under a <Component>.
=20
If I added that <Directory> entry in more than one fragment, I got
duplicate Id errors (not surprisingly).
=20
If I tried to use <Directory> in the main .wxs file, and <DirectoryRef>
in the fragments, it is not resolved a WiX compilation time.
=20
If I tried to use <Directory> in the main .wxf file by itself (where
there are no <Registry>entries), at installation time the old error
("WindowsFolder not in Directory table") returned.
=20
So, it looks like I need that empty <Directory> entry in *one* wxs file
(main or fragment) that *also* has a <Registry> entry.
=20
That soulds like a WiX misfeature to me, but I'm just a WiX noob. Is
there a better way of getting <Registry> to work without such hackery?
=20
I only found the hack above after searching the net led me to a patch
file for someone's wxs source that had that entry. Talk about obscure.
=20

________________________________

From: Rene Hollan=20
Sent: Thursday, January 26, 2006 8:35 PM
To: 'Bob Arnson'
Cc: wix-users@...
Subject: RE: [WiX-users] replacing self-registration with installer
registration


Bah. When I do that, and include the <Registry> entries from the
fragment created, I get the following in the installer log:
=20
Action 20:34:19: WelcomeDlg. Dialog created
DEBUG: Error 2727:  The directory entry 'WindowsFolder' does not exist
in the Directory table
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2727. The arguments are: WindowsFolder, ,=20
MSI (c) (7C:B8) [20:34:23:509]: Product: MSN TAF XTC Toolkit 2.0 (WTT
2.2.2098.226) -- The installer has encountered an unexpected error
installing this package. This may indicate a problem with this package.
The error code is 2727. The arguments are: WindowsFolder, ,=20
=20
Action ended 20:34:23: WelcomeDlg. Return value 3.

________________________________

From: Bob Arnson [mailto:wix@...
Sent: Thursday, January 26, 2006 7:34 PM
To: Rene Hollan
Cc: wix-users@...
Subject: Re: [WiX-users] replacing self-registration with installer
registration


Rene Hollan wrote:=20

	I have two dlls that are normally installed with regsvr32. Their
DllServerInstall entry points just call a ServerInstall entry point
which is automatically generated because of a [MODULE] attribute. How
can I glean all the bits so I can author the WiX code to get them
installed and forgo self-installation? They are not my dlls -- IK am
just writing the installer.=20

Use Tallow.exe with the -s switch to generate a partial fragment that
contains the registry values.

I'm guessing I could load it with regsvr32 and then browse the registry
to get the information required. Then, create Registry entries to match
that. But, are all those GUIDs likely to stay the same if the component
is recompiled?

________________________________

From: wix-users-admin@...
[mailto:wix-users-admin@...] On Behalf Of Rene Hollan
Sent: Thursday, January 26, 2006 6:00 PM
To: wix-users@...
Subject: [WiX-users] replacing self-registration with installer
registration


I have two dlls that are normally installed with regsvr32. Their
DllServerInstall entry points just call a ServerInstall entry point
which is automatically generated because of a [MODULE] attribute. How
can I glean all the bits so I can author the WiX code to get them
installed and forgo self-installation? They are not my dlls -- IK am
just writing the installer.
=20

Hi=20all,
=20
With=20an=20installer=20that=20we=20have=20written=20in=20WiX=20we=20have=20=
a=20component=20that
is=20a=20database=20install...=20as=20we=20have=20legacy=20systems=20that=20=
didn't=20have=20an
installer,=20the=20database=20is=20set=20to=20a=20feature=20that=20default=
s=20to=20not=20be
installed=20(in=20case=20the=20user=20already=20has=20a=20suitable=20datab=
ase)=20however
this=20can=20be=20turned=20on=20even=20if=20the=20user=20already=20has=20t=
he=20database
installed,=20not=20a=20problem=20so=20far=20but....
I've=20discovered=20that=20if=20a=20user=20who=20already=20has=20the=20dat=
abase=20installed
attempts=20to=20use=20the=20Installer=20to=20install=20the=20database=20an=
d=20chooses=20the
same=20name=20as=20an=20existing=20database=20the=20installer=20fails=20(a=
s=20I=20would=20hope
it=20would)=20but=20then=20the=20rollback=20deletes=20the=20existing=20dat=
abase.....
=20
Is=20there=20any=20way=20to=20stop=20this=20behaviour?
=20
Many=20thanks=20for=20any=20replies
=20
Owen=20Evans
=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Owen=20Evans,=20Developer/Tester,=20Cresta=20Group=20Ltd
Mobile:=20+44=20(0)79=2021761557=20Direct:=20+44=20(0)20=207448=204635
Office:=20+44=20(0)20=207448=204620=20Fax:=20+44=20(0)20=207448=204651
Email:=20Owen.Evans@...
Address:=20120=20Moorgate,=20London,=20EC2M=206SS,=20UK.
Web=20Site:=20http://www.cresta.net=20<http://www.cresta.net/>=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
=20


This=20email=20and=20any=20attachments=20are=20confidential=20and=20intend=
ed=20solely=20for=20the=20use=20of=20the=20individual=20or=20entity=20to=20=
whom=20they=20are=20addressed.=20=20If=20you=20are=20not=20the=20intended=20=
recipient=20please=20do=20not=20disclose,=20copy=20or=20take=20any=20actio=
n=20in=20reliance=20on=20it.=20=20If=20you=20have=20received=20this=20mess=
age=20in=20error=20please=20tell=20us=20by=20reply=20or=20telephone=20+44=20=
(0)20=207448=204620=20and=20delete=20all=20copies=20on=20your=20system.=20=
=20Any=20opinion,=20advice=20or=20information=20in=20this=20email=20are=20=
not=20necessarily=20those=20of=20the=20owners=20or=20officers=20of=20Crest=
a.=20
=20
Cresta=20have=20taken=20reasonable=20precautions=20to=20ensure=20that=20an=
y=20attachment=20to=20this=20e-mail=20has=20been=20swept=20for=20viruses.=20=
=20However,=20we=20cannot=20accept=20liability=20for=20any=20damage=20sust=
ained=20as=20a=20result=20of=20software=20viruses=20and=20would=20advise=20=
that=20you=20carry=20out=20your=20own=20virus=20checks=20before=20opening=20=
any=20attachment.=20=20Please=20note=20that=20communications=20sent=20by=20=
or=20to=20any=20person=20through=20our=20computer=20systems=20may=20be=20v=
iewed=20by=20other=20Cresta=20employees=20or=20officers,=20strictly=20in=20=
accordance=20with=20applicable=20law.

You could create a "response transform".

-- 
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)

"Hugh Williams" <hugh@...> schrieb im Newsbeitrag 
news:96b44c3a0601270458h48868881o364ccafabbb0f68@......
Is there a WiX technique for passing a response file into msiexec
along with the .msi file?

Just to be clear, what I'd like to do is take this:

msiexec -i foo.msi bar1=fred bar2=barney bar3=wilma bar4=betty

... and just do something like this instead...

msiexec -i foo.msi USEINI=setup.ini

... where a file called "setup.ini" would have...

bar1=fred
bar2=barney
bar3=wilma
bar4=betty


I know there are other installers that let you do this... any advice?

Thanks.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642

Hello,
By profession, I am a software packager.
Over the past year, I have used WIX heavily in a large complex
development project. Despite its Beta status and incomplete
documentation, I felt obliged to use WIX because:
1 It supports most of the technologies that I needed to deploy.
2 Any Developer could easily understand what was going on (Thanks to
Fragments and a straight forward notation).
3 I found unit testing and debugging easier with WIX, because it is easy
to move features and components between MSI's without disturbing the
code or using merge modules.
4 My client stipulated MSI, and to use a standard approach.
5 Your code is more likely to be bug free than mine would have been, and
writing deployment tools would be my last resort.
6 I had objections with alternative products.
As I have to document my work, it occurs to me that I can return
something to this project/community.
So if you are looking for help with documentation then please advise.

Regards


Martin Lavelle