Re: [WiX-users] creatind DB and running SQL script

[akash bhatia]

hi,

problem solved
thanks all for your valuable inputs. some problem with SQL only. not
able to figure out what...ll share once figure it out. moreover i have
made some changes to wxs file as well and tested on other server... its
working fine...
















thnks again guys for ur time

Regards,
Akash
On Fri, Mar 13, 2009 at 4:02 AM, Michael Osmond wrote:

> Akash,
>
> The problem is unlikely to be WIX or MSI problem as such, so I doubt
> that all the DTF CA work would be worth it.  The error is an SQL error,
> and to me appears to be either path or file name related.  SQL databases
> are persisted on the file system as a set of files, and it is in
> creating these files that the error occurs.
>
> There may be some information in the SQL Management log.
>
> Your next step should be to create that exact same database manually -
> from an SQL script not the Management Studio gui - and see if you get
> the same error.
>
> Then you need to check what files SQL server is trying to create.
>
> I would also suggest that you try this on another machine and see if you
> get the same error.
>
> Michael
>
> -Original Message-
> From: akash bhatia [mailto:911ak...@gmail.com]
>  Sent: Thursday, 12 March 2009 10:22 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] creatind DB and running SQL script
>
> hi Michael,
>
> thanks for your reply.
> that is wat i got from Event viewer and same from verbose log, which is
> as below
>
> CreateDatabase:  Error 0x80040e14: failed to create to database:
> Akash_DB,
> error: CREATE DATABASE failed. Some file names listed could not be
> created.
> Check related errors.
> Error 26201. Error -2147217900: failed to create SQL database: Akash_DB,
> error detail: CREATE DATABASE failed. Some file names listed could not
> be created. Check related errors..
> MSI (s) (8C!84) [20:01:24:015]: Product: Akash_WixProject -- Error
> 26201.
> Error -2147217900: failed to create SQL database: Akash_DB, error
> detail:
> CREATE DATABASE failed. Some file names listed could not be created.
> Check related errors..
>
> Action ended 20:01:24: InstallFinalize. Return value 3.
>
> this is exact what i got from verbose
>
> i am not gettin anything to support this... there is no info more than
> this in eventvwr.
>
> Please suggest me any other way to tackle this.
> or else i would be left to last option of using DTF CA for executing
> sqlscripts.
>
> regards,
> Akash
>
>
>
> On Thu, Mar 12, 2009 at 11:04 AM, Michael Osmond
> wrote:
>
> > 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 Server
>
> > default data folders with the same name as the database you are trying
>
> > to create.  (Did you detach this database some time but not delete the
>
> > files).
> >
> > Can you try creating the database using a script not the installer.
> > Do you get the same error?
> >
> > Finally, use the SQL Profiler to trace what is going on.
> >
> > Michael
> >
> > -Original Message-
> > From: akash bhatia [mailto:911ak...@gmail.com]
> > Sent: Thursday, 12 March 2009 3:16 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] creatind DB and running SQL script
> >
> > 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 
> wrote:
> >
> > > 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 at 10:34 AM, akash bhatia <911ak...@gmail.com>
> > wrote:
> > >
> > > > 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
> > > >
> > > >
> > > > 
> > > >
> > > >  > > > ="[SERVER]"
> > > > CreateOnInstall="yes" DropOnUninstall="no" ContinueOnError="no">
> > > >
> > > >  > > > ExecuteOnInstall ="yes" RollbackOnInstall ="yes" ContinueOnError
> > > > ="no"/>
> > > >
> > > > 
> > > >
> > > > 
> > > > am not able to locate the cause of this error, can any one help me
>
> > > > on
> > > this
> > > > ?
> > > >
> > > > in sql script i am adding few tables into my database
> > "[ORGANIZATIONDB]"
> > > >
> > > > i am not using "USE [ORGANIZATIONDB]" insode sql script, which i
> > > > guess it takes automatically as its inside sql:Sq

Re: [WiX-users] Bootstrapper selection & questions - Specificscenario requirements

[Don Benson]

On Thu, Mar 12, 2009 at 12:01 PM, Holmgren Mathias
wrote:


> I just want uninstall to remove all application components (ie
> exe+interop dll), regardless if those components where installed at
> first install (primary scenario) or in a second "module" install
> according to the secondary scenario.
>

If you want your MSI to remove post-install-generated content, you can use
RemoveFile elements, assuming you know the folder where the content is
located. Wildcards are allowed on the file name, but not on the folder. If
you have subfolders to be removed, I think you'd have to write a custom
action to handle that.

If at all possible, I would really want to keep the integrity of "one"
> app MSI, so professional organizations would use this same app MSI but
> without the bootstrapper. This would reduce the corp confusion and team
> maintenance pain of having multiple app MSIs.
>

Configuration in an MSI is usually handled via public properties (i.e.
properties whose Id is all caps, like INSTALLDIR and DBSERVERNAME). These
properties can be set through the UI, but they can also be defined from the
command line, which would override the default value you would set. This
allows an installation-savvy user do a command line install like this:

msiexec /i MyApp.msi /qn INSTALLDIR="my path" DBSERVERNAME="DB1"
SERVICEURL="http://myhost.com";

A novice user, who will simply "run" the MSI file, will get the UI and will
have the default values you put in for those properties. WiX has an advanced
template that allows users to click Install from one the early dialogs and
skip over any customization dialogs. I think You should still include
customization dialogs in the MSI for these properties. This supports the
"semi-professional" user. That is, they know the customizations they want,
but they don't know how to use msiexec from the command line.

Or, maybe the bootstrapper itself can include the property values in
> play so all we have to have per partner is a different bootstrap exe
> (and the app MSI in distributed format can be identical for all
> customers and partners while avoiding transforms altogether)?
>

Bootstrappers are usually pretty dumb. They are customized to say here are
the products to be installed before I launch the final product installation.

I'm not sure I understand your relationship with the users of the app. Who
is going to run your installer? The partners? Or are the partners giving the
installer to end users, and the partner relies on you, the author, to
provide appropriate partner-specific defaults?

Instead of generating different bootstrappers, I would generate multiple
MSIs. This can be automated as part of your build process. The public
properties' default value can be a variable you define. That variable can be
passed on the command line in your build process. Assuming your app has the
same third-party prerequisites for all partner distributions, the
bootstrapper will have the same configuration for each customized MSI.

My confusion here is not so much how a bootstrapper fits into this (or
> rather not) but more about what would be *best practice* for this kind
> of post install, extra MSI-module install scenario that does not
> fragment the main installation scenario into a big mess of
> sub-MSI-packages per Office version??
>

When  you configure the bootstrapper, you can either download the PIA
installer file and include it in your distribution, or you can configure it
to download it from a web site. That could be your own web site, or you
might choose to use the Microsoft web site.

If you choose to include the interop installers with your distribution, you
could author your MSI to put them into a sub-folder within your
installation. Then your app can be execute the provided installer since you
know the name and relative location. I don't like this idea, myself.

I would opt for downloads. In your app, I would show a dialog that includes
a hyperlink that takes the customer to the Microsoft web site where they can
download and run the installation for the PIA.

I hope that my suggestions are appropriate for your scenario. If I've made
any poor suggestions, hopefully somebody else will chime in.

- Don Benson -
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Modifying a pre-existing value, and it can't be deleted on uninstall - how?

[Don Benson]

I haven't tried this, but what if you make that registry value a the key
path of its own component and mark the component as Permanent. I suspect
that will not be removed when the app is uninstalled.

- Don Benson -

On Thu, Mar 12, 2009 at 9:00 PM, Andrew Lowe <
al...@immersivetechnologies.com> wrote:

> Hi all,
>Sorry if this a basic question, I'm very very new to Wix and am
> still trying to make sense of it. Our application runs on dedicated
> machines and I need to turn off Simple File Sharing. This is controlled
> by the registry value:
>
> HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest
>
> What I need to do is set this to false, value = 0, during the install
> and for the uninstall of the software to set it back to true, value = 1.
>
> At present I'm doing
>
>.
>..
>...
> Key="SYSTEM\CurrentControlSet\Control\Lsa">
> Value="0"/>
>
>...
>..
>.
>
> But this removes the "ForceGuest" entry upon uninstall, which in turn
> freaks out the computer and causes all sorts of trouble upon reboot.
> There must be a way to modify this value upon install and restore it
> upon uninstall, in fact I don't really care about the uninstall, it can
> stay as is. Can anyone prod me in the right directions?
>
>Regards,
>Andrew Lowe
> Disclaimer:
> This message contains confidential information and is intended only for the
> individual(s) named. If you are not the named addressee you should not
> disseminate, distribute or copy this email. Please immediately delete it and
> all copies of it from your system, destroy any hard copies of it, and notify
> the sender. Email transmission cannot be guaranteed to be secure or
> error-free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. To the maximum extent
> permitted by law, Immersive Technologies Pty. Ltd. does not accept liability
> for any errors or omissions in the contents of this message which arise as a
> result of email transmission.
>
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line options to wix file

[Don Benson]

Public properties can be defined on the command line. Any properties that
are all caps (e.g. INSTALLDIR) are public properties. An example of a public
property used by some of the WiX extensions is LOGVERBOSE. The following
example would run the installer with the built-in logging and set two public
properties:

msiexec /i MyInstaller.msi /l*v InstallDebug.log LOGVERBOSE=1
INSTALLDIR="D:\Custom Programs\My Program"

- Don Benson -

On Thu, Mar 12, 2009 at 5:16 PM, Sudripta Nandy (Sarangsoft Corporation) <
v-su...@microsoft.com> wrote:

> In my setup program, the user needs to specify certain properties (like
> install location) from the command line. I am declaring these properties
> within my wix file and depending on the value of these properties, I am
> doing different stuff. How do I do that? Can I pass command-line options to
> be accessed within my wix file?
>
>
> Thanks.
> // Sudripta.
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom action only executed on install

[Don Benson]

Try putting a condition of "Not Installed" on the  element where you
sequence the action.

- Don Benson -

On Thu, Mar 12, 2009 at 12:57 PM, wimpos  wrote:

>
> Hi
>
> I have a custom action in my wix installer executing a powershell script.
> This scripts adds a line to a file. Now a line get's added when I install
> my
> app AND when I uninstall my app.
> Is it possible to configure a custom action to only be executed on install?
>
> thank you for your time
>
>
> Kind regards
> Wim Devos
> --
> View this message in context:
> http://n2.nabble.com/Custom-action-only-executed-on-install-tp2468625p2468625.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Modifying a pre-existing value, and it ca n't be deleted on uninstall - how?

[Andrew Lowe]

Hi all,
Sorry if this a basic question, I'm very very new to Wix and am
still trying to make sense of it. Our application runs on dedicated
machines and I need to turn off Simple File Sharing. This is controlled
by the registry value:

HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest

What I need to do is set this to false, value = 0, during the install
and for the uninstall of the software to set it back to true, value = 1.

At present I'm doing 

.
..
...



...
..
.

But this removes the "ForceGuest" entry upon uninstall, which in turn
freaks out the computer and causes all sorts of trouble upon reboot.
There must be a way to modify this value upon install and restore it
upon uninstall, in fact I don't really care about the uninstall, it can
stay as is. Can anyone prod me in the right directions?

Regards,
Andrew Lowe
Disclaimer:
This message contains confidential information and is intended only for the 
individual(s) named. If you are not the named addressee you should not 
disseminate, distribute or copy this email. Please immediately delete it and 
all copies of it from your system, destroy any hard copies of it, and notify 
the sender. Email transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. To the maximum extent permitted by law, 
Immersive Technologies Pty. Ltd. does not accept liability for any errors or 
omissions in the contents of this message which arise as a result of email 
transmission.

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Major Upgrades without version change

[Castro, Edwin (Hillsboro)]

You are correct. We do rely on a single source for the build number, we only 
have one build server, and we don't expect our repository to move/change during 
the lifetime of our project.

Developer builds are not consumed outside the individual developer and we have 
found that version numbers matter a little less in that case. One scenario 
where it does matter is when developers are explicitly testing an upgrade 
scenario. The build system allows them to inject whatever build number they 
deem appropriate for their private developer build so we can emulate this well 
enough at dev time. All official builds are consumed from our CI build server, 
those are the authoritative builds. Our version scheme works well for our 
context and has the added benefit that all of our official builds are always 
well-behaved major upgrades even if they are created on the same day.

Clearly, your development environment has different requirements which require 
a different versioning scheme with the unfortunate result that you can only 
perform major upgrades on a day by day basis. We were able to tailor our 
environment to match the output we wanted because the restrictions you 
mentioned didn't affect us.

My goal was to share one versioning scheme that played nice with Windows 
Installer. I'm sure there are others. I was not trying to describe a 
one-size-fits-all solution nor was I trying to convince anyone to adopt our 
scheme.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Thursday, March 12, 2009 3:34 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
> That is one view of version numbers but it doesn't work for me. It
> relies on there being a single source of the build number, if two
> builds are started on different servers were does the build number come
> from. Using revision from the source repository doesn't work if the
> repository moves or the repository changes.
>
> For me the solution that has worked most reliably is to set major and
> minor manually (usually a marketing decision), build is the number of
> days since a fixed date and revision the seconds number of seconds
> since the start of today / 10. This is totally deterministic and not
> dependant on any external files or systems. The build server can
> produce builds and so can developers and none have the same number
> (well they would if started with 10s but I can live with that).
>
> Having said that, that wasn't really my question but it is nice to hear
> other peoples approaches.
>
> Neil
>
> -Original Message-
> From: Castro, Edwin (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: 12 March 2009 20:28
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
> System.Version defines the following format:
>
> major.minor[.build[.revision]]
>
> We defined those as follows:
>
> The product release defines major and minor numbers (static and changed
> manually).
> The build number is the CI build number (automatically increments by
> one every build).
> The revision number is the changeset number in our source control
> repository for that build (determined automatically at build time).
>
> This structure allows us to track deployed assemblies/installers/etc to
> specific builds/changesets very easily.
> Our goal is to automatically produce major upgrades every build (we
> schedule RemoveExistingProducts early).
>
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: Neil Sleightholm [mailto:n...@x2systems.com]
> > Sent: Thursday, March 12, 2009 1:31 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Major Upgrades without version change
> >
> > I don't think that is that case as my RemoveExistingProducts is
> > scheduled at the beginning (if it wasn't I think you are correct). As
> > you say major upgrades are the best solution but that just doesn't
> work
> > with automated builds that use 4 part version numbers.
> >
> > Neil
> >
> > Neil Sleightholm
> > X2 Systems Limited
> > n...@x2systems.com 
> >
> >
> > 
> >
> > From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
> > Sent: Thu 12/03/2009 00:06
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Major Upgrades without version change
> >
> >
> >
> > I don't think you'd get a downgrade you would like.  I think you
> would
> > end up with a mush of the tw

Re: [WiX-users] Major Upgrades without version change

[Neil Sleightholm]

That is one view of version numbers but it doesn't work for me. It relies on 
there being a single source of the build number, if two builds are started on 
different servers were does the build number come from. Using revision from the 
source repository doesn't work if the repository moves or the repository 
changes.

For me the solution that has worked most reliably is to set major and minor 
manually (usually a marketing decision), build is the number of days since a 
fixed date and revision the seconds number of seconds since the start of today 
/ 10. This is totally deterministic and not dependant on any external files or 
systems. The build server can produce builds and so can developers and none 
have the same number (well they would if started with 10s but I can live with 
that).

Having said that, that wasn't really my question but it is nice to hear other 
peoples approaches.

Neil

-Original Message-
From: Castro, Edwin (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: 12 March 2009 20:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Major Upgrades without version change

System.Version defines the following format:

major.minor[.build[.revision]]

We defined those as follows:

The product release defines major and minor numbers (static and changed 
manually).
The build number is the CI build number (automatically increments by one every 
build).
The revision number is the changeset number in our source control repository 
for that build (determined automatically at build time).

This structure allows us to track deployed assemblies/installers/etc to 
specific builds/changesets very easily.
Our goal is to automatically produce major upgrades every build (we schedule 
RemoveExistingProducts early).

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Thursday, March 12, 2009 1:31 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
> I don't think that is that case as my RemoveExistingProducts is
> scheduled at the beginning (if it wasn't I think you are correct). As
> you say major upgrades are the best solution but that just doesn't work
> with automated builds that use 4 part version numbers.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com 
>
>
> 
>
> From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
> Sent: Thu 12/03/2009 00:06
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
>
>
> 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 and you will end up keeping component 21 with
> ver 1.2.0
>
> Major upgrades keep proving to be the safest method for us
>
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Wednesday, March 11, 2009 12:12 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
> 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 without version change
>
> 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/
>
>
>
> ---
> -
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly
> and easily build your RIAs with Flex Builder, the Eclipse(TM)based
> development software that enables intelligent coding and step-through
> debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ---
> -
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platfor

Re: [WiX-users] creatind DB and running SQL script

[Michael Osmond]

Akash,

The problem is unlikely to be WIX or MSI problem as such, so I doubt
that all the DTF CA work would be worth it.  The error is an SQL error,
and to me appears to be either path or file name related.  SQL databases
are persisted on the file system as a set of files, and it is in
creating these files that the error occurs.

There may be some information in the SQL Management log.

Your next step should be to create that exact same database manually -
from an SQL script not the Management Studio gui - and see if you get
the same error.

Then you need to check what files SQL server is trying to create.  

I would also suggest that you try this on another machine and see if you
get the same error.

Michael

-Original Message-
From: akash bhatia [mailto:911ak...@gmail.com] 
Sent: Thursday, 12 March 2009 10:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creatind DB and running SQL script

hi Michael,

thanks for your reply.
that is wat i got from Event viewer and same from verbose log, which is
as below

CreateDatabase:  Error 0x80040e14: failed to create to database:
Akash_DB,
error: CREATE DATABASE failed. Some file names listed could not be
created.
Check related errors.
Error 26201. Error -2147217900: failed to create SQL database: Akash_DB,
error detail: CREATE DATABASE failed. Some file names listed could not
be created. Check related errors..
MSI (s) (8C!84) [20:01:24:015]: Product: Akash_WixProject -- Error
26201.
Error -2147217900: failed to create SQL database: Akash_DB, error
detail:
CREATE DATABASE failed. Some file names listed could not be created.
Check related errors..

Action ended 20:01:24: InstallFinalize. Return value 3.

this is exact what i got from verbose

i am not gettin anything to support this... there is no info more than
this in eventvwr.

Please suggest me any other way to tackle this.
or else i would be left to last option of using DTF CA for executing
sqlscripts.

regards,
Akash



On Thu, Mar 12, 2009 at 11:04 AM, Michael Osmond
wrote:

> 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 Server

> default data folders with the same name as the database you are trying

> to create.  (Did you detach this database some time but not delete the

> files).
>
> Can you try creating the database using a script not the installer.  
> Do you get the same error?
>
> Finally, use the SQL Profiler to trace what is going on.
>
> Michael
>
> -Original Message-
> From: akash bhatia [mailto:911ak...@gmail.com]
> Sent: Thursday, 12 March 2009 3:16 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] creatind DB and running SQL script
>
> 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 
wrote:
>
> > 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 at 10:34 AM, akash bhatia <911ak...@gmail.com>
> wrote:
> >
> > > 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
> > >
> > >
> > > 
> > >
> > >  > > ="[SERVER]"
> > > CreateOnInstall="yes" DropOnUninstall="no" ContinueOnError="no">
> > >
> > >  > > ExecuteOnInstall ="yes" RollbackOnInstall ="yes" ContinueOnError 
> > > ="no"/>
> > >
> > > 
> > >
> > > 
> > > am not able to locate the cause of this error, can any one help me

> > > on
> > this
> > > ?
> > >
> > > in sql script i am adding few tables into my database
> "[ORGANIZATIONDB]"
> > >
> > > i am not using "USE [ORGANIZATIONDB]" insode sql script, which i 
> > > guess it takes automatically as its inside sql:SqlDatabase element
> > >
> > >
> > > any help will be appreciated.
> > >
> > > thanks!
> > > Akash
> > >  On Wed, Mar 11, 2009 at 7:06 PM, Don Benson 
> > wrote:
> > >
> > > > 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 scripts to

> > > > not reference a database at all. Instead of MyDB.dbo.MyTable, 
> 

[WiX-users] Passing command line options to wix file

[Sudripta Nandy (Sarangsoft Corporation)]

In my setup program, the user needs to specify certain properties (like install 
location) from the command line. I am declaring these properties within my wix 
file and depending on the value of these properties, I am doing different 
stuff. How do I do that? Can I pass command-line options to be accessed within 
my wix file?


Thanks.
// Sudripta.
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Enable logging inside MSI package

[Jacek Dudziak]

Is there a way to change those  properties using WIX?

--
From: "Wilson, Phil" 
Sent: Thursday, March 12, 2009 10:46 AM
To: "General discussion for Windows Installer XML toolset." 

Subject: Re: [WiX-users] Enable logging inside MSI package

> MSI 4.0 has the MsiLogging and MsiLogFileLocation properties, but you're 
> correct, there's nothing before that except MsiEnableLog in the calling 
> process.
>
> Phil Wilson
>
> -Original Message-
> From: Jacek Dudziak [mailto:jacekdudz...@hotmail.com]
> Sent: Thursday, March 12, 2009 1:52 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Enable logging inside MSI package
>
> Is it possible to turn on verbose logging from inside the MSI package 
> itself? Today my customers can do it by running 'msiexec /l*v' but the 
> problem is that they do not know that command, as they usually double 
> click on the MSI file itself.
>
> I know I can make it work by creating setup.exe which internally can call 
> msiexec command, but I would hope to avoid that as there are some issues 
> with VS 2008 and setup.exe produced by.
>
> Thanks
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> 

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Major Upgrades without version change

[Castro, Edwin (Hillsboro)]

System.Version defines the following format:

major.minor[.build[.revision]]

We defined those as follows:

The product release defines major and minor numbers (static and changed 
manually).
The build number is the CI build number (automatically increments by one every 
build).
The revision number is the changeset number in our source control repository 
for that build (determined automatically at build time).

This structure allows us to track deployed assemblies/installers/etc to 
specific builds/changesets very easily.
Our goal is to automatically produce major upgrades every build (we schedule 
RemoveExistingProducts early).

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Thursday, March 12, 2009 1:31 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
> I don't think that is that case as my RemoveExistingProducts is
> scheduled at the beginning (if it wasn't I think you are correct). As
> you say major upgrades are the best solution but that just doesn't work
> with automated builds that use 4 part version numbers.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com 
>
>
> 
>
> From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
> Sent: Thu 12/03/2009 00:06
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
>
>
> 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 and you will end up keeping component 21 with
> ver 1.2.0
>
> Major upgrades keep proving to be the safest method for us
>
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Wednesday, March 11, 2009 12:12 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Major Upgrades without version change
>
> 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 without version change
>
> 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/
>
>
>
> ---
> -
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly
> and easily build your RIAs with Flex Builder, the Eclipse(TM)based
> development software that enables intelligent coding and step-through
> debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ---
> -
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly
> and easily build your RIAs with Flex Builder, the Eclipse(TM)based
> development software that enables intelligent coding and step-through
> debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ---
> ---
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly
> and easily build your RIAs with Flex Builder, the Eclipse(TM)based
> development software that enables intelligent coding and step-through
> debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Apps built with the Adobe(R) Fl

Re: [WiX-users] FW: Permanent xml tag for File?

[Hugo Vale]

Thanks guys, that worked. I changed the file to be independently on its own
component and then assign the Permanent attribute to that component.

Hugo Vale

-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com] 
Sent: Thursday, March 12, 2009 1:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] FW: Permanent xml tag for File?

Hey Hugo,

Have you looked at the Component/@Permanent attribute?

http://wix.sourceforge.net/manual-wix3/wix_xsd_component.htm

Thanks,

Brian Rogers
"Intelligence removes complexity." - Me
http://icumove.spaces.live.com


On Thu, Mar 12, 2009 at 10:07 AM, Hugo Vale  wrote:

> Hi,
>
>
>
> I recently changed one of my visual studio setups to WiX. However I'm
> having
> trouble in finding out a replacement for the 'Permanent' property on the
> files being deployed.
>
>
>
> Is there such a functionality when deploying files through WiX? Basically,
> I
> don't want that file to be uninstalled when uninstalling the setup.
>
>
>
> Thanks in advance,
>
> Hugo Vale
>
>
>
>
>
>
>

--
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to define source for System files in GAC

[Ghazala Fazil]

Hi Bob,

Actually my program is not refereing such libraries. As I am moving the
project form the Visual Studio to the Wix. I have noticed these additional
files.

So I thought may be I can add them in Wix as well.

Thanks a lot Bob fro saving me from more searching.

Regards,
Ghazala

On Thu, Mar 12, 2009 at 6:10 PM, Bob Arnson  wrote:

> Ghazala Fazil wrote:
> > I am new on wix. I want to include some of the public assemblies from the
> > GAC into the setup but
> >
>
> WiX doesn't support that; it's generally a bad idea to pick up arbitrary
> deployed files. Instead, the files you need to deploy should be built or
> checked in to your version control system.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding system wide module to IIS7 on 64-bit OS

[Scott Sam]

I figured out my problem.  I was using
[SystemFolder]inetsrv\config\applicationHost.config as the file, which
resolved to c:\windows\syswow64\inetsrv\config\applicationHost.config.
I switched to
[WindowsFolder]System32\inetsrv\config\applicationHost.config, and that
worked.

-Original Message-
From: Scott Sam [mailto:s...@clearviewecm.com] 
Sent: Wednesday, March 11, 2009 4:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding system wide module to IIS7 on 64-bit OS

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 running in 32-bit. I'm using wix version
3.0.4721.0.  Anyone have any suggestions?

-Original Message-
From: Adam Eversole [mailto:adam.evers...@microsoft.com] 
Sent: Monday, January 26, 2009 4:33 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding system wide module to IIS7 on 64-bit OS

Additional info, I am using WIX 3.0.4827.0
With the following:


  
  
  
  

  
  
  
  

  


I didn't get any replies in my e-mail, but noticed there was an actual
reply on the archive.

If anybody could help I would be most appreciative

Thanks,

Adam
From: Adam Eversole
Sent: Friday, January 23, 2009 2:24 PM
To: 'wix-users@lists.sourceforge.net'
Subject: Adding system wide module to IIS7 on 64-bit OS

I have a setup that installs a system-wide managed-code module in IIS7.
I do this as follows:

  
   




  

With the following preprocessor command setting var.64bit:


  

  


This seems to work just fine in 32-bit, but in 64-bit it fails with the
following error:

Action 14:21:52: ExecXmlConfig.
Error 25541. Failed to open XML file
C:\Windows\system32\inetsrv\Config\applicationHost.config, system error:
-2147024786

I can't figure it out, I made sure I have access to the file in elevated
mode (the elevated prompt comes up), and it works great in 32-bit.

Any ideas? Is there a better way to do this?

Thanks,

Adam


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based
development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting MSI Execution Directory

[greenaj]

Checkout the SourceDir Property.  Just don't do that during an Uninstall or any
other time you would not want the source directory to be resolved (resulting in 
a promt).

Regards,
agreen
 troy hostetter  wrote: 
> 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  />.
> 
> I thought there might be an internal directory ID .. like CURRENTDIR .. or
> something.
> 
> - Troy
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Pyro system requirements

[Bob Arnson]

Alexander Schulz wrote:
> I just have a Pentium 4 with 512 MB RAM and wait for every patch more 
> than 2 hours.
> What could be a good hardware to do such a job? Or is there another way ?
>   

You're likely running low on memory.

-- 
sig://boB
http://joyofsetup.com/



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Re-evaluating feature conditions

[Bob Arnson]

Jackie Ng wrote:
> When I run this installer, if I pick "Bundled Configuration" or "Manual
> Configuration", when I get to the feature selection dialog, the Apache Web
> Server feature is still enabled when I would have expected it to be disabled
> because I changed the value of MGWEB_CONFIG.
>
> Is there a way that I can force a re-evaluation of feature conditions before
> I get to the feature selection dialog?
>   

No but you can use AddLocal and Remove control events to accomplish the 
same thing as feature conditions.

-- 
sig://boB
http://joyofsetup.com/



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Own UI-File

[Bob Arnson]

Bahn Thomas wrote:
> The next problem i have, is to specify the ErrorText-Control to appear in 
> Control_First field of the dialog table. Which Attribute let me set this in 
> WiX?
>   

Make it the first child element of the Dialog.

-- 
sig://boB
http://joyofsetup.com/



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to define source for System files in GAC

[Bob Arnson]

Ghazala Fazil wrote:
> I am new on wix. I want to include some of the public assemblies from the
> GAC into the setup but
>   

WiX doesn't support that; it's generally a bad idea to pick up arbitrary 
deployed files. Instead, the files you need to deploy should be built or 
checked in to your version control system.

-- 
sig://boB
http://joyofsetup.com/



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Enable logging inside MSI package

[Wilson, Phil]

MSI 4.0 has the MsiLogging and MsiLogFileLocation properties, but you're 
correct, there's nothing before that except MsiEnableLog in the calling 
process. 

Phil Wilson 

-Original Message-
From: Jacek Dudziak [mailto:jacekdudz...@hotmail.com] 
Sent: Thursday, March 12, 2009 1:52 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Enable logging inside MSI package

Is it possible to turn on verbose logging from inside the MSI package itself? 
Today my customers can do it by running 'msiexec /l*v' but the problem is that 
they do not know that command, as they usually double click on the MSI file 
itself. 
 
I know I can make it work by creating setup.exe which internally can call 
msiexec command, but I would hope to avoid that as there are some issues with 
VS 2008 and setup.exe produced by.
 
Thanks
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] FW: Permanent xml tag for File?

[Brian Simoneau]

Components can be marked Permanent.  Any files in the component would
not be uninstalled.

-Brian Simoneau 

-Original Message-
From: Hugo Vale [mailto:hugov...@gmail.com] 
Sent: Thursday, March 12, 2009 1:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Permanent xml tag for File?

Hi,

 

I recently changed one of my visual studio setups to WiX. However I'm
having
trouble in finding out a replacement for the 'Permanent' property on the
files being deployed.

 

Is there such a functionality when deploying files through WiX?
Basically, I
don't want that file to be uninstalled when uninstalling the setup.

 

Thanks in advance,

Hugo Vale

 

 


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based
development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] FW: Permanent xml tag for File?

[Brian Rogers]

Hey Hugo,

Have you looked at the Component/@Permanent attribute?

http://wix.sourceforge.net/manual-wix3/wix_xsd_component.htm

Thanks,

Brian Rogers
"Intelligence removes complexity." - Me
http://icumove.spaces.live.com


On Thu, Mar 12, 2009 at 10:07 AM, Hugo Vale  wrote:

> Hi,
>
>
>
> I recently changed one of my visual studio setups to WiX. However I'm
> having
> trouble in finding out a replacement for the 'Permanent' property on the
> files being deployed.
>
>
>
> Is there such a functionality when deploying files through WiX? Basically,
> I
> don't want that file to be uninstalled when uninstalling the setup.
>
>
>
> Thanks in advance,
>
> Hugo Vale
>
>
>
>
>
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] FW: Permanent xml tag for File?

[Hugo Vale]

Hi,

 

I recently changed one of my visual studio setups to WiX. However I'm having
trouble in finding out a replacement for the 'Permanent' property on the
files being deployed.

 

Is there such a functionality when deploying files through WiX? Basically, I
don't want that file to be uninstalled when uninstalling the setup.

 

Thanks in advance,

Hugo Vale

 

 

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Custom action only executed on install

[wimpos]

Hi

I have a custom action in my wix installer executing a powershell script.
This scripts adds a line to a file. Now a line get's added when I install my
app AND when I uninstall my app.
Is it possible to configure a custom action to only be executed on install?

thank you for your time


Kind regards
Wim Devos
-- 
View this message in context: 
http://n2.nabble.com/Custom-action-only-executed-on-install-tp2468625p2468625.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper selection & questions - Specificscenario requirements

[Holmgren Mathias]

Thanks for the good feedback Don! My questions and comments inline,

> Removal: It sounds like you are asking the removal of your app to
remove
> the prerequisites that the bootstrapper installed. Bootstrappers are
not
> designed to do this because it is a bad idea. Other programs may need
> these prerequisites, including the PIA assemblies.

I did not mean uninstall would uninstall OS SPs or the framework, I
agree that would not be a good idea.

I just want uninstall to remove all application components (ie
exe+interop dll), regardless if those components where installed at
first install (primary scenario) or in a second "module" install
according to the secondary scenario.

> You could provide separate downloads for each installation. In this
case,
> your build process would build separate MSIs and would generate a
separate
> bootstrapper EXE for each partner.

If at all possible, I would really want to keep the integrity of "one"
app MSI, so professional organizations would use this same app MSI but
without the bootstrapper. This would reduce the corp confusion and team
maintenance pain of having multiple app MSIs.

> A second alternative is to include customization dialogs as part of
the
> MSI that set properties based on the selected partners.

This is what I want to do, but there might not have to be any dialogs.
For a partner distribution these MSI properties should be filled in with
partner specific values at some point (not by end user who has no clue,
see below).

During installation, these MSI properties are written to app.config (or
similar). Pro customers can use msiexec to set these properties at will,
or accept the default property values.

My question for this scenario is rather my options in how to apply and
set these properties and when. Would I have to apply a transform (?) or
set them in some other way before the bootstrapper executes?

If transform, can this be applied after building the boostrapper, or
does it have to be before (CI/build issue).

Or, maybe the bootstrapper itself can include the property values in
play so all we have to have per partner is a different bootstrap exe
(and the app MSI in distributed format can be identical for all
customers and partners while avoiding transforms altogether)?

As you can see, my knowledge of Windows Installer technology is a bit
fuzzy on the whole transform thing and how to best combine it with what
a bootstrapper can do in terms of customization and what it can carry in
terms of usable payload.

> The third alternative is to design this partner-specific customization
> into the app itself, post-installation.

There will of course have to be some new code in the app that knows what
to do with these property values, which mostly has to do with how to
connect to which servers and create user configuration information the
first time the app starts. This is why some information must be provided
before install time.

The whole idea is for the customer to not have to fill in that fragile
mumbo jumbo information manually. And in doing so get the user up and
running as fast as possible by magic, while reducing customer service
issues (due to fat fingers, confusion and whatnot).

> Post-installation execution of Excel: The bootstrapper cannot really
> handle this automatically because the bootstrapper does not run again
> after the app is installed. In fact, the user may have deleted the 
> installation EXE once your app is installed. Your app should detect
the 
> missing PIA scenario and initiate the PIA installation.

Yeah, the app would of course have to have some code to shell to msiexec
or just ask the user to install it and restart. The bootstrapper, at
most, would put some sort of installation module/MSI-thingy on disk
containing only the PIA packages and corresponding app DLLs based on
Excel-version (or the URL to that thingy in app.config).

My confusion here is not so much how a bootstrapper fits into this (or
rather not) but more about what would be *best practice* for this kind
of post install, extra MSI-module install scenario that does not
fragment the main installation scenario into a big mess of
sub-MSI-packages per Office version??

Here, I fall a little short in my knowledge about merge modules (?), how
to combine pieces of one installation into another, etc. Any pointers
would be appreciated.

> I might also suggest not trying to bootstrap OS service packs

Ok, seems reasonable. Thanks, we'll follow that advice.

> Your users should know how to uninstall a program.

Yes, you would think. I agree...! ;)

Again, I appreciate the quality response Don.

/Mathias

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download

Re: [WiX-users] Bootstrapper selection & questions - Specific scenario requirements

[Don Benson]

I've spent the past couple weeks configuring a bootstrap process with
dotNetInstaller beta version 1.6. dotNetInstaller can handle pretty much
everything you require except for the following statements:

Removal: It sounds like you are asking the removal of your app to remove the
prerequisites that the bootstrapper installed. Bootstrappers are not
designed to do this because it is a bad idea. Other programs may need these
prerequisites, including the PIA assemblies. Your users should know how to
uninstall a program.

Customized properties: Bootstrappers are designed to combine prerequisites
and your single MSI. I can suggest three ways to handle partner-specific
customization. You could provide separate downloads for each installation.
In this case, your build process would build separate MSIs and would
generate a separate bootstrapper EXE for each partner. dotNetInstaller
supports this scenario. A second alternative is to include customization
dialogs as part of the MSI that set properties based on the selected
partners. The third alternative is to design this partner-specific
customization into the app itself, post-installation.

Post-installation execution of Excel: The bootstrapper cannot really handle
this automatically because the bootstrapper does not run again after the app
is installed. In fact, the user may have deleted the installation
EXE once your app is installed. Your app should detect the missing
PIA scenario and initiate the PIA installation.

The hard part of dotNetInstaller, and most bootstrappers, is that they do
not come prepackaged with URL settings or executables for prerequisites. You
have to provide those yourself.

I might also suggest not trying to bootstrap OS service packs. You can put
conditions on the bootstrapper and your MSI to prevent installation when the
OS is below a certain level and include a message to indicate they should
use Windows Update to get the latest service pack and security updates.

- Don Benson -

On Thu, Mar 12, 2009 at 8:51 AM, Holmgren Mathias
wrote:

> I've read up a bit on bootstrappers, but can't figure out yet which path
> to take on this.
>
> - We got an application MSI built using WiX 3, works great
> - Application uses Office PIA* to integrate real time with Excel (data
> update, app->excel)
> - Depending on the Excel version, our app MSI installs a different
> version of app DLL for excel-integration (refs matching PIA assembly
> version)
>
> Now we want to streamline pre-requisite installation since distribution
> through partners to private end users (ie day traders, etc) is expected
> to expand (previously, pro financial institutions w their own
> IT-departments was dominant customer segment).
>
> Primary Scenario Requirements
> 1 - Bootstrapper should detect pre-requisites, inform user when missing
> and install on demand if allowed.
> 1.1   - Detect OS, download and install required service pack X for this
> OS as needed
> 1.2   - If .NET FW 2.0 SP1 is missing, download and install
> 1.3.1 - Detect Excel version, download and install corresponding PIA
> version.
> 1.3.2 - If no Excel, skip PIA install (see 7 below).
> 1.4   - Install app MSI
> 2 - Bootstrapper and app MSI should be one single downloadable file
> (exe/msi or equiv, not zip).
> 3 - Some app MSI properties should be pre-set w different values based
> on partner (server url, etc)
> 4 - Works painless in a modern CI environment (rel paths, text source
> format, build script friendly, etc)
> 5 - Seamless and painless full uninstall no matter what (local copy of
> all necessary MSIs, etc)
> 6 - Bootstrapper supports all modern Windows platforms: XP, Win Server
> , Vista, Win7, etc
>
> Note that we have different pre-reqs & app install depending on which
> Excel-version the user has installed, if any.
>
> Secondary Scenario Requirement
> 7 - User did not have Excel installed during app installation, but
> installs it afterwards. On starting application, detect Excel version
> and launch installation of the correct PIA version "on demand". This
> includes installing matching version of app interop assemblies. That is,
> no need for user to re-install the whole application from scratch to
> enable Excel-integration. Uninstall req 5 still applies.
>
> Questions
> A - Is there a bootstrapper supporting these reqs out there today, or do
> we have to wait for Burn?
> B - How would you "modularize" the app/installation/build to support 3
> and 7 specifically?
>
> * PIA = Ms Office Primary Interop Assemblies, it's a different installer
> package based on Office version.
>
> /Mathias
>
> --
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day t

[WiX-users] Re-evaluating feature conditions

[Jackie Ng]

Hi All,

I am currently writing a wix installer for the MapGuide Open Source project
(http://mapguide.osgeo.org), and I am having some problems with regards to
enabling/disabling features.

I have a feature named "WebExtApacheFeature" (Apache Web Server) which has a
disabling condition (MGWEB_CONFIG = "IIS") (ref:
http://trac.osgeo.org/mapguide/browser/trunk/Installer/Libraries/MapGuide%20Web%20Extensions/MapGuideWebExtensions.wxs#L88
)

In one of my custom dialogs I have a group of radio buttons that sets the
value of MGWEB_CONFIG.  (ref:
http://trac.osgeo.org/mapguide/browser/trunk/Installer/Installers/MapGuide/MapGuide.wxs#L134
)

The radio buttons are:

1. Bundled Configuration: Sets MGWEB_CONFIG = "APACHE"
2. IIS Configuration: Sets MGWEB_CONFIG = "IIS"
3. Manual Configuration: Sets MGWEB_CONFIG = "MANUAL"

When I run this installer, if I pick "Bundled Configuration" or "Manual
Configuration", when I get to the feature selection dialog, the Apache Web
Server feature is still enabled when I would have expected it to be disabled
because I changed the value of MGWEB_CONFIG.

Is there a way that I can force a re-evaluation of feature conditions before
I get to the feature selection dialog?

Regards,

- Jackie

-- 
Blog: http://themapguyde.blogspot.com
LinkedIn: http://www.linkedin.com/in/jackieng
Twitter: http://twitter.com/jumpinjackie

"A SQL query walks into a bar and sees two tables. He walks up to them and
says 'Can I join you?'"
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Bootstrapper selection & questions - Specific scenario requirements

[Holmgren Mathias]

I've read up a bit on bootstrappers, but can't figure out yet which path
to take on this.
 
- We got an application MSI built using WiX 3, works great
- Application uses Office PIA* to integrate real time with Excel (data
update, app->excel)
- Depending on the Excel version, our app MSI installs a different
version of app DLL for excel-integration (refs matching PIA assembly
version)
 
Now we want to streamline pre-requisite installation since distribution
through partners to private end users (ie day traders, etc) is expected
to expand (previously, pro financial institutions w their own
IT-departments was dominant customer segment).
 
Primary Scenario Requirements
1 - Bootstrapper should detect pre-requisites, inform user when missing
and install on demand if allowed.
1.1   - Detect OS, download and install required service pack X for this
OS as needed
1.2   - If .NET FW 2.0 SP1 is missing, download and install
1.3.1 - Detect Excel version, download and install corresponding PIA
version.
1.3.2 - If no Excel, skip PIA install (see 7 below).
1.4   - Install app MSI
2 - Bootstrapper and app MSI should be one single downloadable file
(exe/msi or equiv, not zip).
3 - Some app MSI properties should be pre-set w different values based
on partner (server url, etc)
4 - Works painless in a modern CI environment (rel paths, text source
format, build script friendly, etc)
5 - Seamless and painless full uninstall no matter what (local copy of
all necessary MSIs, etc)
6 - Bootstrapper supports all modern Windows platforms: XP, Win Server
, Vista, Win7, etc
 
Note that we have different pre-reqs & app install depending on which
Excel-version the user has installed, if any.
 
Secondary Scenario Requirement
7 - User did not have Excel installed during app installation, but
installs it afterwards. On starting application, detect Excel version
and launch installation of the correct PIA version "on demand". This
includes installing matching version of app interop assemblies. That is,
no need for user to re-install the whole application from scratch to
enable Excel-integration. Uninstall req 5 still applies.
 
Questions
A - Is there a bootstrapper supporting these reqs out there today, or do
we have to wait for Burn? 
B - How would you "modularize" the app/installation/build to support 3
and 7 specifically?
 
* PIA = Ms Office Primary Interop Assemblies, it's a different installer
package based on Office version.
 
/Mathias
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] creatind DB and running SQL script

[Don Benson]

If you use SQL Profiler to monitor the RPC calls to the database server, you
should be able to capture the full SQL statement that is being used to
create the database. Knowing the statement that was sent to the SQL Server
will help with figuring out what is going wrong.

- Don Benson -
On Thu, Mar 12, 2009 at 8:21 AM, akash bhatia <911ak...@gmail.com> wrote:

> hi Michael,
>
> thanks for your reply.
> that is wat i got from Event viewer and same from verbose log, which is as
> below
>
> CreateDatabase:  Error 0x80040e14: failed to create to database: Akash_DB,
> error: CREATE DATABASE failed. Some file names listed could not be created.
> Check related errors.
> Error 26201. Error -2147217900: failed to create SQL database: Akash_DB,
> error detail: CREATE DATABASE failed. Some file names listed could not be
> created. Check related errors..
> MSI (s) (8C!84) [20:01:24:015]: Product: Akash_WixProject -- Error 26201.
> Error -2147217900: failed to create SQL database: Akash_DB, error detail:
> CREATE DATABASE failed. Some file names listed could not be created. Check
> related errors..
>
> Action ended 20:01:24: InstallFinalize. Return value 3.
>
> this is exact what i got from verbose
>
> i am not gettin anything to support this... there is no info more than this
> in eventvwr.
>
> Please suggest me any other way to tackle this.
> or else i would be left to last option of using DTF CA for executing
> sqlscripts.
>
> regards,
> Akash
>
>
>
> On Thu, Mar 12, 2009 at 11:04 AM, Michael Osmond  >wrote:
>
> > 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 Server
> > default data folders with the same name as the database you are trying
> > to create.  (Did you detach this database some time but not delete the
> > files).
> >
> > Can you try creating the database using a script not the installer.  Do
> > you get the same error?
> >
> > Finally, use the SQL Profiler to trace what is going on.
> >
> > Michael
> >
> > -Original Message-
> > From: akash bhatia [mailto:911ak...@gmail.com]
> > Sent: Thursday, 12 March 2009 3:16 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] creatind DB and running SQL script
> >
> > 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  wrote:
> >
> > > 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 at 10:34 AM, akash bhatia <911ak...@gmail.com>
> > wrote:
> > >
> > > > 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
> > > >
> > > >
> > > > 
> > > >
> > > >  > > > ="[SERVER]"
> > > > CreateOnInstall="yes" DropOnUninstall="no" ContinueOnError="no">
> > > >
> > > >  > > > ExecuteOnInstall ="yes" RollbackOnInstall ="yes" ContinueOnError
> > > > ="no"/>
> > > >
> > > > 
> > > >
> > > > 
> > > > am not able to locate the cause of this error, can any one help me
> > > > on
> > > this
> > > > ?
> > > >
> > > > in sql script i am adding few tables into my database
> > "[ORGANIZATIONDB]"
> > > >
> > > > i am not using "USE [ORGANIZATIONDB]" insode sql script, which i
> > > > guess it takes automatically as its inside sql:SqlDatabase element
> > > >
> > > >
> > > > any help will be appreciated.
> > > >
> > > > thanks!
> > > > Akash
> > > >  On Wed, Mar 11, 2009 at 7:06 PM, Don Benson 
> > > wrote:
> > > >
> > > > > 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 scripts to
> > > > > not reference a database at all. Instead of MyDB.dbo.MyTable, use
> > > > dbo.MyTable.
> > > > > The osql command has a command-line parameter to define the
> > > > > database to use.
> > > > > If you use this parameter inside the custom action, your script
> > > > > will be applied to the correct database.
> > > > >
> > > > > - Don Benson -
> > > > >  On Wed, Mar 11, 2009 at 8:09 AM, akash bhatia
> > > > > <911ak...@gmail.com>
> > 

[WiX-users] Pyro system requirements

[Alexander Schulz]

Hello everyone,

I want to build patches (binary-diff) using the "Purely WiX" method. In 
my installation are some *.exe-files, every file is about 30 MB.

I just have a Pentium 4 with 512 MB RAM and wait for every patch more 
than 2 hours.
What could be a good hardware to do such a job? Or is there another way ?


Thanks for helping,

Alexander Schulz



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] creatind DB and running SQL script

[akash bhatia]

hi Michael,

thanks for your reply.
that is wat i got from Event viewer and same from verbose log, which is as
below

CreateDatabase:  Error 0x80040e14: failed to create to database: Akash_DB,
error: CREATE DATABASE failed. Some file names listed could not be created.
Check related errors.
Error 26201. Error -2147217900: failed to create SQL database: Akash_DB,
error detail: CREATE DATABASE failed. Some file names listed could not be
created. Check related errors..
MSI (s) (8C!84) [20:01:24:015]: Product: Akash_WixProject -- Error 26201.
Error -2147217900: failed to create SQL database: Akash_DB, error detail:
CREATE DATABASE failed. Some file names listed could not be created. Check
related errors..

Action ended 20:01:24: InstallFinalize. Return value 3.

this is exact what i got from verbose

i am not gettin anything to support this... there is no info more than this
in eventvwr.

Please suggest me any other way to tackle this.
or else i would be left to last option of using DTF CA for executing
sqlscripts.

regards,
Akash



On Thu, Mar 12, 2009 at 11:04 AM, Michael Osmond wrote:

> 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 Server
> default data folders with the same name as the database you are trying
> to create.  (Did you detach this database some time but not delete the
> files).
>
> Can you try creating the database using a script not the installer.  Do
> you get the same error?
>
> Finally, use the SQL Profiler to trace what is going on.
>
> Michael
>
> -Original Message-
> From: akash bhatia [mailto:911ak...@gmail.com]
> Sent: Thursday, 12 March 2009 3:16 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] creatind DB and running SQL script
>
> 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  wrote:
>
> > 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 at 10:34 AM, akash bhatia <911ak...@gmail.com>
> wrote:
> >
> > > 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
> > >
> > >
> > > 
> > >
> > >  > > ="[SERVER]"
> > > CreateOnInstall="yes" DropOnUninstall="no" ContinueOnError="no">
> > >
> > >  > > ExecuteOnInstall ="yes" RollbackOnInstall ="yes" ContinueOnError
> > > ="no"/>
> > >
> > > 
> > >
> > > 
> > > am not able to locate the cause of this error, can any one help me
> > > on
> > this
> > > ?
> > >
> > > in sql script i am adding few tables into my database
> "[ORGANIZATIONDB]"
> > >
> > > i am not using "USE [ORGANIZATIONDB]" insode sql script, which i
> > > guess it takes automatically as its inside sql:SqlDatabase element
> > >
> > >
> > > any help will be appreciated.
> > >
> > > thanks!
> > > Akash
> > >  On Wed, Mar 11, 2009 at 7:06 PM, Don Benson 
> > wrote:
> > >
> > > > 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 scripts to
> > > > not reference a database at all. Instead of MyDB.dbo.MyTable, use
> > > dbo.MyTable.
> > > > The osql command has a command-line parameter to define the
> > > > database to use.
> > > > If you use this parameter inside the custom action, your script
> > > > will be applied to the correct database.
> > > >
> > > > - Don Benson -
> > > >  On Wed, Mar 11, 2009 at 8:09 AM, akash bhatia
> > > > <911ak...@gmail.com>
> > > wrote:
> > > >
> > > > > 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 facing: how can i update the DBNAME propery
>
> > > > > on
> > the
> > > > fly
> > > > > in my SQL script ?
> > > > >
> > > > > any suggestions will b highly appreciated?
> > > > >
> > > > > Regards,
> > 

[WiX-users] Wix, SQL and Custom Data

[Prabhakaran Paulraj]

Hi Everyone,

I am a newbie to Wix and i am using wix 2.0. I need to get the client machine 
name(all in caps) and pass this as a parameter as my SQL Server name. I got 
this by this following property

<
<
RegistrySearchId="EvsRegistrySearchMachineName1"Root="HKLM"Type="raw"Name="Hostname"Key="SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\"/>Property>
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] xp x64 detection

[Yan Sklyarenko]

This is a condition I use to detect the WinXP 64-bit:

   VersionNT64 = 502 AND MsiNTProductType = 1

Note that you should address VersionNT64 instead of VersionNT for 64-bit
systems. MsiNTProductType = 1 means "workstation", which differentiates
it from "domain controller" (MsiNTProductType = 2) and just "server"
(MsiNTProductType = 3).

Hope this helps.

-- Yan

-Original Message-
From: Calin Iaru [mailto:ca...@dolphinics.com] 
Sent: Thursday, March 12, 2009 12:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] xp x64 detection

Hi,

  I did not test my msi on XP X64 and someone actually came and reported
an error. I see that my installer follows the guidelines at 
http://msdn.microsoft.com/en-us/library/aa370556(VS.85).aspx
  but also that someone reports a documentation bug. Is VersionNt 501 or
502 for XP X64? I don't have a box ready for testing at the moment.

Thanks,
Calin

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based
development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] xp x64 detection

[Calin Iaru]

Hi,

  I did not test my msi on XP X64 and someone actually came and reported an 
error. I see that my installer follows the guidelines at 
http://msdn.microsoft.com/en-us/library/aa370556(VS.85).aspx
  but also that someone reports a documentation bug. Is VersionNt 501 or 502 
for XP X64? I don't have a box ready for testing at the moment.

Thanks,
Calin
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WixToolPath variable

[Kim Gybels]

Instead of using the WixToolPath variable I found that I can use the
WIX environment variable.

I set my additional linker options to:
-ext WixDifxAppExtension -ext WixUIExtension "$(WIX)bin\difxapp_x86.wixlib"

This works like a charm.

- Kim

--

*Kim Gybels
Software Developer
* kim.gyb...@metris.com 
Tel: +32 16 74 01 01
Fax: +32 16 74 01 02



* Metris Europe
* Interleuvenlaan 86
3001 Leuven
Belgium
www.metris.com 




This message and any attachment are privileged, confidential and contain 
private information. If you are not the addressee named above any disclosure, 
reproduction, copying, distribution, or other dissemination or use of this 
communication is prohibited. If you have received this transmission in error, 
please notify the sender immediately and destroy this e-mail. Metris does not 
guarantee that the integrity of this communication has been maintained or that
this communication is free of viruses, interceptions or interference, and shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system. Incoming and outgoing email communications may be monitored by 
Metris, as permitted by applicable law and regulations.

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Major Upgrades without version change

[Neil Sleightholm]

I don't think that is that case as my RemoveExistingProducts is scheduled at 
the beginning (if it wasn't I think you are correct). As you say major upgrades 
are the best solution but that just doesn't work with automated builds that use 
4 part version numbers.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  
 



From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
Sent: Thu 12/03/2009 00:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Major Upgrades without version change



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 and you will end up keeping component 21 with
ver 1.2.0

Major upgrades keep proving to be the safest method for us

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, March 11, 2009 12:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Major Upgrades without version change

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 without version change

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/




--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based
development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based
development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Enable logging inside MSI package

[Jacek Dudziak]

Is it possible to turn on verbose logging from inside the MSI package itself? 
Today my customers can do it by running 'msiexec /l*v' but the problem is that 
they do not know that command, as they usually double click on the MSI file 
itself. 
 
I know I can make it work by creating setup.exe which internally can call 
msiexec command, but I would hope to avoid that as there are some issues with 
VS 2008 and setup.exe produced by.
 
Thanks
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Own UI-File

[Bahn Thomas]

Thanks, this helped.

The next problem i have, is to specify the ErrorText-Control to appear in 
Control_First field of the dialog table. Which Attribute let me set this in WiX?

Von: Bob Arnson [...@joyofsetup.com]
Gesendet: Mittwoch, 11. März 2009 18:14
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Own UI-File

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 Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users