Re: [WiX-users] Several doubts on Upgrades

2006-09-13 Thread Tiago Silva
> If you use major
> upgrades, you can supply just one .msi -- it both does a fresh
> installation and upgrades an existing installation. The MSI major
> upgrade support sets a property during upgrading, so you can use the
> presence of that property to suppress components and custom actions you
> want to be skipped during upgrade.

I Know that I am already pushing my luck :) , but can you provide me a
snippet or an example for it? Especially the use of the Upgrade and
UpgradeVersion tags.


On 9/12/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Tiago Silva wrote:
> > We will produce in our weekly builds two setups. One that is the full
> > installation and other that have almost the same components that the
> > full install except files that the user changes (settings files), the
> > application database and customs actions that setup the server
> > environment on the clean install.
> >
> That works but is more complicated than necessary. If you use major
> upgrades, you can supply just one .msi -- it both does a fresh
> installation and upgrades an existing installation. The MSI major
> upgrade support sets a property during upgrading, so you can use the
> presence of that property to suppress components and custom actions you
> want to be skipped during upgrade.
> > The idea is to create the
> > upgrade as minor upgrades to avoid the change of ProductCode. What do
> > you think of this ?
> >
> The downside to minor upgrades is that they can't do a fresh
> installation and you need a chainer/bootstrapper to apply them.
> Double-clicking the .msi file doesn't install a minor upgrade.
> > My boss wants to keep track of the upgrades that has been installed.
> > The idea is to do something like MS style to keep track of the dates
> > and versions that were installed.
> >
> > In MS office for example we can see in add and remove programs the
> > entry to the application and if we check the "Show Updates" checkboxs
> > a list of updates to the application are showed. I was wondering what
> > kind of upgrades are it? Patches? Minor upgrades?
> >
> Add/Remove Programs shows that info only for patches. Upgrades of any
> kind replace the existing version of the product.
>
> --
> sig://boB
> http://bobs.org
>
>

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Several doubts on Upgrades

2006-09-12 Thread Tiago Silva
Thanks Bob for your rapid response.

As I told I am new to Wix upgrades and my knowledge on windows
installer is very limited.

I was wondering if the approach that i having is the right one.Let me
explain the main propose of it:

We will produce in our weekly builds two setups. One that is the full
installation and other that have almost the same components that the
full install except files that the user changes (settings files), the
application database and customs actions that setup the server
environment on the clean install.
If a new customer buy our application the full install will be
delivered. In meanwhile the upgrade will be distributed to the current
customers. With this approach we will have the latest source code
always on the upgrade msi. I know that this strategy will produce big
upgrade msi and if a critical bug is fixed the customer will receive
the all application files, but is a compromise to avoid the management
of several patches and several wix files. The idea is to create the
upgrade as minor upgrades to avoid the change of ProductCode. What do
you think of this ?

My boss wants to keep track of the upgrades that has been installed.
The idea is to do something like MS style to keep track of the dates
and versions that were installed.

In MS office for example we can see in add and remove programs the
entry to the application and if we check the "Show Updates" checkboxs
a list of updates to the application are showed. I was wondering what
kind of upgrades are it? Patches? Minor upgrades?

Thanks

Tiago

On 9/12/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Tiago Silva wrote:
> > I have the main setup of the application that is generated by a nant
> > task. At the same time a upgrade is generated to the current version.
> > Let's consider the version 1.0.0.40 on both.
> >
> MSI doesn't differentiate between product versions in the fourth field
> so you won't be able to do major upgrades between 1.0.0.40 and 1.0.0.41.
> See the MSI doc for details on ProductVersion.
> > 2. It is possible to see the history of all upgrades in the add and
> > remove programs of by checking the "Show Updates" Check boxes?
> >
> ARP shows only products and patches.
> > 3. Does anybody knows a good source of snippets regarding this
> > subject. I think that the wix documentation lacks a little bit on
> > upgrades.
> >
> See http://www.tramontana.co.hu/wix/lesson4.php.
>
> --
> sig://boB
> http://bobs.org
>
>

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Several doubts on Upgrades

2006-09-12 Thread Tiago Silva
I am new to upgrades in Wix and i would like to ask a few questions to
more experienced users.

My scenario is:

I have the main setup of the application that is generated by a nant
task. At the same time a upgrade is generated to the current version.
Let's consider the version 1.0.0.40 on both.
The idea is that new customers, install the setup and current
customers upgrade the to the newer version.


My questions are:

1. How do I produce a double click install to install the upgrade? The
upgrade that i've playing in tutorial gives me a "Product already
installed" message when I install it by double clicking the msi file.
I'm using a minor upgrade, i.e., the same ProductID and different
version.
I was able to install it only by runing the command msiexec /i
SampleUpgrade.msi REINSTALL=ALL REINSTALLMODE=vomus


2. It is possible to see the history of all upgrades in the add and
remove programs of by checking the "Show Updates" Check boxes?

3. Does anybody knows a good source of snippets regarding this
subject. I think that the wix documentation lacks a little bit on
upgrades.

Best regards to all.

Tiago

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Tuturial Doubt

2006-09-12 Thread Tiago Silva
Please ignore the doubt.
I was using two versions of wix the lastest compiler but a older wixLibs.

Thanks

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Tutorial Doubt

2006-09-12 Thread Tiago Silva
Hi to all,

I saw the following issue in other topics but I don't figure it out
how to handle it.

I downloaded the SampleUpgrade (section4.1) file and can't compile it.
The command that I am doing is:

Starting c:\wix\light.exe "SampleUpgrade.wixobj" -out
"SampleUpgrade.msi" c:\Wix\ca\sca.wixlib c:\wix\ca\wixca.wixlib
c:\wix\UI\wixui_mondo.wixlib

and gives me the following error:

error LGHT0112 : Unresolved reference to symbol 'UI:WixUI_Mondo' in
section 'Product:D2627F04-D1FF-410F-AFE2-0114D4389E5F'.

I am using the last build of wix,i.e., 2.0.4423.0.


What i am doing wrong?

Thanks

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Components and SQL Issues

2006-09-12 Thread Tiago Silva
Hi there Fredrik,

Thanks for sharing your valuable experience.

Answering to your question and after talking to my boss is that the
upgrades on database will be handled by our support team.

We have the current scenario. We have nant tasks that produce two
installers. One is the main installer to be applied on a clean machine
and the other one is the upgrade to the components current version.
The first one will install the database, and never drop it on
uninstall. The idea of the second one is to update only application
components, i.e, Dlls and website pages. The settings files and the
database upgrades will be handled by our support team now.

In a future we can include the upgrades in the upgrade installer, but
this is a little more tricky because it will affect the automatic
process of generating our MSI, because from one version to other we
can apply one or several sql files to change DB structure.

Finally to know the database version as we don't put it under windows
installer we decided that the upgrade sql scripts will write on a log
data table the history of upgrades.

I hope that I've answered your question

Regards,

Tiago

On 9/11/06, Fredrik Grohn <[EMAIL PROTECTED]> wrote:
> 1. You probably don't want to leave the component behind on the system on
> uninstall in any case. It sounds like what you really want to do is make the
> removal of the database conditional. That sounds like a perfectly valid
> feature request to me. Unfortunately I can't think of a way to do it with
> the current implementation though. (You can only hard-code if the database
> should be dropped on uninstall.)
>
> 2. This bug has been puzzling me for a while. I agree that it is a valid
> assumption that a rollback should attempt to leave the system in a state as
> close to the original state as possible. The problem I believe is that the
> assumption when a CA finds an entity that it is meant to install itself
> already present on the system, is that it is the result of a failed
> installation or similar. It will then "tolerate the error" by proceeding
> anyway ignoring the fact that the entity was present on the system. The
> result of cause is that it will behave like it actually installed the given
> entity when performing a rollback and clean the entity up. It could be
> argued that the proper behavior is to fail instead in this situation instead
> of accepting the error.
>
> The problem with making this behavior fully transactional and never delete a
> resource we didn't create in the first place is that it is a lot more
> difficult to implement. Also I think that the general convention used by the
> Windows Installer is the current behavior of the SQL CA's.
>
> User data is handled a bit different by the Windows Installer though. And
> after writing this little essay I have convinced myself that the correct
> thing to do is to make the SQL CA's not drop the database on rollback if it
> was present before the installation.
>
> Just a small question: Have you given any thought to how you want to handle
> upgrade scenarios? Would you ever need to do modifications to a database
> left behind by an older version of your software when you are installing a
> new version?
>
> Fredrik
>
> -----Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
> Sent: Monday, September 11, 2006 6:49 PM
> To: Tiago Silva
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Components and SQL Issues
>
> Tiago Silva wrote:
> > 1. My boss wants that the current setup of our application ask to the
> > user if he wants to keep the application database and settings. I have
> > two separated components and I evaluate if the components are to
> > uninstall or not. The problem is that the Components uninstall run
> > always no mather the Condition values that are set. I saw the property
> > named Permanent but is no good for me because I want to give the
> > choise to the user.
> >
> Component conditions kick in only during installation. They don't affect
> uninstallation. You can make them features so the user has visible
> control over them.
> > 2. This one I think that is a known Bug, but sincerely I don't know
> > the state of it. If I install a database on a server that already have
> > a database with the same name, and after the sql authentication is
> > performed an install error occur, the database is dropped from the
> > server. Any news of it?
> >
> That bug (#1212275) is still open.
>
> --
> sig://boB
> http://bobs.org
>
>
> -
> Using Tomcat but need to do more? Need to support web services, se

[WiX-users] Components and SQL Issues

2006-09-11 Thread Tiago Silva
Hi there to all Wix users.

I have two doubts regarding Wix that I would like to discuss with more
experienced users.

1. My boss wants that the current setup of our application ask to the
user if he wants to keep the application database and settings. I have
two separated components and I evaluate if the components are to
uninstall or not. The problem is that the Components uninstall run
always no mather the Condition values that are set. I saw the property
named Permanent but is no good for me because I want to give the
choise to the user.


  
  
  (INSTALL_DATABASE="1") OR
(UNINSTALL_DATABASE="1")


  
  (INSTALL_SETTINGS="1") OR
(UNINSTALL_SETTINGS="1")


2. This one I think that is a known Bug, but sincerely I don't know
the state of it. If I install a database on a server that already have
a database with the same name, and after the sql authentication is
performed an install error occur, the database is dropped from the
server. Any news of it?


Thanks to all.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users