Re: [WiX-users] Text randomly disappearing

[PitMonster]

Hi Blair !
thx for your answer, i tried they same .msi file on my laptop and the text
didnt disappear... but it is the same OS WIN XP Professional but not the
same Service Pack oO
i cant believe this will make something


The error when building from the commandline means you must add "-ext
WixIIsExtension" to the commandlines of both candle and light.

The disappearing text: I have no idea.
-- 
View this message in context: 
http://n2.nabble.com/Text-randomly-disappearing-tp3462381p3971574.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Condition depending on feature didn't work

[Rob Mensching]

I think you need a & or ! before the Feature Id. Take a look at the
"Condition Statement Syntax" topic in the MSI SDK.

On Thu, Nov 5, 2009 at 5:05 AM, SD_GOTH  wrote:

>
> Hello,
> I have an installation package with 2 features. At end of installation I
> want to display a checkbox for further actions only if feature #2 was
> installed.
>
> 
>
>
>
>
>
>
> 
>
> I tried to use the feature #2 in a condition for displaying the checkbox in
> the exit dialog. I’m checking for value 3 which mean that the feature
> should
> be installed locally. This didn’t work, the checkbox isn’t shown
> independent
> if feature #2 was selected or not.
>
> 
>
> Height="10" Property='Prop1'
>  CheckBoxValue='0' Hidden='yes'>
>Feature2=3
>
>
> 
>
> Does anybody know how to do this?
> Thanks in advice.
>
> Thomas
> --
> View this message in context:
> http://n2.nabble.com/Condition-depending-on-feature-didn-t-work-tp3952002p3952002.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Why do I get duplicate symbol found?

[Rob Mensching]

Most likely caused by the duplicate FileSearch elements. There are a couple
scenarios with AppSearch that just aren't handled correctly. The AppSearch
design is a real pain and it always takes me a while to finally sort out how
to make it all work.

On Thu, Nov 5, 2009 at 9:52 AM, Richard  wrote:

> I have the following searches setup to scrape values from an ini file
> into properties
>
> 
>Name="dzInstall.ini" Section="ApplicationPath"
>Key="dzHexagonInstallDir">
>Path="[CommonFilesFolder]">
>
>
>
> 
> 
>Name="dzInstall.ini" Section="ApplicationPath"
>Key="dzHexagonIconGroup">
>
>
>
>
> 
>
> I'm attempting to reuse the existing DirectorySearch with a
> DirectorySearchRef to avoid duplication.  Yet, when I do this, I get
> the following error from WiX 3.0:
>
> Product.wxs(9,0): error LGHT0091: Duplicate symbol
> 'Signature:CommonFilesFolder_dzInstall.ini' found.
> Product.wxs(16,0): error LGHT0092: Location of symbol related to previous
> error.
>
> Line 9 refers to the  and line 16 referes to the
> .
>
> What am I doing wrong?
> --
> "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
>  
>
>  Legalize Adulthood! 
>
>
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Update fails if files have been modified

[Rob Mensching]

That sounds like the correct part of the File Versioning rules. Read the
blog entry and really the "correct" way to update files installed by the
Windows Installer is to use the Windows Installer to update them. However,
since you are dealing with unversioned files your work around will probably
be fine.

On Sun, Nov 8, 2009 at 12:27 PM, Thomas Singer  wrote:

> According to my understanding, I've tried to summarize all information and
> the solution in our blog:
>
>  http://blog.syntevo.net/2009/11/08/125770902.html
>
> If something is wrong, please let me know. Thanks in advance.
>
> Tom
>
>
> Thomas Singer wrote:
> > Thanks for the hint to the File Versioning Rules:
> >
> >  
> > http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx
> >
> > Do I understand it correctly, that file versions and languages solely
> apply
> > to .exe/.dll or similar files, but not to, for example, .jar files which
> are
> > nothing else than .zip files? Then the following paragraph should explain
> my
> > situation well:
> >
> > | Nonversioned Files are User Data—If the Modified date is later than the
> > | Create date for the file on the computer, do not install the file
> because
> > | user customizations would be deleted. If the Modified and Create dates
> > | are the same, install the file. If the Create date is later than the
> > | Modified date, the file is considered unmodified, install the file.
> >
> > Tom
> >
> >
> > Rob Mensching wrote:
> >> You might read through the File Versioning topic in the MSI SDK. It
> talks
> >>  about all the rules. They aren't completely simple.
>
>
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is this a GUID matching problem - how to resolve.

[Rob Mensching]

Personally, I'd just do the Major Upgrade with a clean install and call it
good. The WiX toolset has 159 files and we do Major Upgrades all the time.
It is easiest way to move from build to build. If the performance seems
reasonable for your application, I'd recommend it. 

On Sun, Nov 8, 2009 at 10:05 AM, Paul Brook  wrote:

> Blair,
>
> Thanks for the explanation. Regarding your last paragraph about matching up
> GUIDs between installs.
>
> "The only way that happens is by making the component guids match. And the
> best way to do that is to not autogenerate them, or if you must
> autogenerate
> them, use "*" as the component guid values so that the binder will produce
> the component guid values in a stable way."
>
> I am using "*" to generate the GUIDS in my WIX file. Obviously these are
> not matching the GUIDs created by Visual Studio in the Deployment Project
> .msi I am replacing, so I dumped the .msi using dark and realize I have a
> lot of typing to do to copy in each GUID.
>
> The question is this. Is it worth the effort to copy all the GUIDs into the
> new installer? Considering that doing uninstall early in the process cleanly
> uninstalls the old version and correctly installs the new one, what
> advantages are gained? I am installing around 80 to 100 files.
>
> At this point I am willing to do the RemoveExistingProducts
> After="InstallInitialize" as long as there are no problems lurking that will
> bite the process down the line.
>
> Thanks for help.
>
> Paul
>
>
>
> -Original Message-
> From: Blair [mailto:os...@live.com]
> Sent: Saturday, November 07, 2009 6:14 PM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Is this a GUID matching problem - how to resolve.
>
> Each of your files that stay in the same directories need to have
> components
> that keep the same guid values. If you don't drastically change your
> installation layouts from build-to-build (which is most of us) it is
> recommended that you write your installation once, and then update it on an
> as-needed basis (instead of autogenerating it each time).
>
> The reason mismatching the component guids causes what you are seeing is as
> follows:
>
> NewProduct (over)writes the files in the installation based on what Windows
> Installer thinks are brand new components (the new guids). Then OldProduct
> erases the files (ignoring what versions or timestamps they may have) when
> removing the old components (since the components don't have any other
> products using them). The repair rewrites the files (since they are
> missing)
> and you are good to go (after the repair).
>
> Here is what happens when you push up the scheduling of
> RemoveExistingProducts:
>
> OldProduct removes its registration of all the components it contains,
> erasing all of the content for those components will no longer exist. Then
> NewProduct registers itself for each component it contains and writes their
> resources out to disk/registry, etc.
>
> Here is what you want to happen:
>
> NewProduct registers itself for each component it contains (making those
> components have two products) and overwrites the files that have newer
> version numbers (and possibly also overwriting those with the same version
> numbers depending on the value of REINSTALLMODE) as well as dealing with
> files that don't have FileVersion values as per the docs on MSDN. Then
> OldProduct removes its registration of all the components it contains,
> erasing the resources associated with any components that disappear as a
> result (along with any keypaths that don't share the same value with
> another
> product, including the one that just installed).
>
> The only way that happens is by making the component guids match. And the
> best way to do that is to not autogenerate them, or if you must
> autogenerate
> them, use "*" as the component guid values so that the binder will produce
> the component guid values in a stable way.
>
> -Original Message-
> From: Paul Brook [mailto:pbr...@vaytek.com]
> Sent: Saturday, November 07, 2009 3:09 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Is this a GUID matching problem - how to resolve.
>
> I am building a WIX installer that will have to upgrade a Visual Studio
> deployment project .msi. When I run the major upgrade installer it replaces
> the entry in the Program and Features list OK but none of the files are
> left
> after the RemoveExistingProducts Before="InstallFinalize" (tried both
> Before
> or After). A repair gets the files installed.
>
> I finally set it to RemoveExistingProducts After="InstallInitialize" and
> that solved the problem but I am still wondering why the update didn't
> work.
> The files in the upgrade all had newer time stamps but some had the same
> version number although some did have newer version numbers.
>
> Is this a component GUID mismatch problem? If so how can I get around it?
> The Visual Studio version of the installer sequences the

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

On Sun, Nov 8, 2009 at 10:39 PM, John Robbins  wrote:
> Hello K,
>
> Glad my blog entry could help. However, I didn't go into the icon stuff as I 
> figured that was common knowledge, but that was a mistake on my part, I'm 
> sorry! You've done everything right so far. :)

Not common knowledge but admittedly outside of working with C#/.NET
for a bit to get my company going I am clearly a neophyte when it
comes to the ins and outs of the Windows Installer.  :-)

> The icon for SETUP.EXE is defined in the in a .RC (resource compiler) file. 
> What I copy .\inc\wix.rc to into the same directory as setup.rc and changed 
> the name of the file to Wintellect.rc. Opening up setup.rc in a text editor, 
> I change the #include line from wix.rc to Wintellect.rc. In Wintellect.rc, I 
> changed all the values to reflect my information and added a line:
>
> 1 ICON .\Resources\Wintellect.ico

Perfect advice and now my .exe does exactly what I want.  The only
changes I had to make to the above were for:
  - my company name.
  - removing header files from my.rc that weren't needed or relevant.
  - changing names and versions in winver.h, etc.
  - making sure that 'ICON' was enclosed in quotes to ensure that C++
compiler didn't choke on ".." in its provided location.

Again, thanks!

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[John Robbins]

Hello K,

Glad my blog entry could help. However, I didn't go into the icon stuff as I 
figured that was common knowledge, but that was a mistake on my part, I'm 
sorry! You've done everything right so far. :)

The icon for SETUP.EXE is defined in the in a .RC (resource compiler) file. 
What I copy .\inc\wix.rc to into the same directory as setup.rc and changed the 
name of the file to Wintellect.rc. Opening up setup.rc in a text editor, I 
change the #include line from wix.rc to Wintellect.rc. In Wintellect.rc, I 
changed all the values to reflect my information and added a line:

1 ICON .\Resources\Wintellect.ico

That'll have the .EXE to use your icon. I've attached my setup.rc and 
Wintellect.rc. I didn't include the header files that just define the macro 
values needed by Wintellect.rc as that's just standard C preprocessor stuff. 

Hope it helps! 

John
Wintellect
http://www.wintellect.com
877-968-5528

>-Original Message-
>From: noopy@gmail.com [mailto:noopy@gmail.com] On Behalf Of
>kerbe...@noopy.org
>Sent: Sunday, November 08, 2009 7:26 PM
>To: John Robbins
>Cc: General discussion for Windows Installer XML toolset.
>Subject: Re: [WiX-users] setupbld and -bitmap not supported? -title not
>supported?
>
>On Sun, Nov 8, 2009 at 1:05 PM, John Robbins 
>wrote:
>> K,
>>
>> Here's how I got SetupBld.exe from WiX to behave like you wanted:
>http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-
>a-bootstrap-loader-with-wix-3-0.aspx.
>
>Oh, I think I've got it now, or at least am getting there.  I
>re-reread your blog and managed to create both release and debug
>versions of setupexe.exe per your instructions.  I copied setupexe.exe
>to my stubs directory and ran with an argument of -setup
>Stubs\setupexe.exe to test setupbld against my newly-generated build
>of setupexe.exe.  That worked fine.
>
>Now the question is: per your instructions how do I define a custom
>title and icon?  I'm looking at wixver.h, WixDistribution.h and
>setup.RC and I'm not seeing any #define that would explicitly allow me
>to define an icon or title for my .exe.
>
>What am I missing?  I'm sure it's something trivial.  Thanks again for
>your response and excellent tutorial!
>
>--
>K
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

On Sun, Nov 8, 2009 at 1:05 PM, John Robbins  wrote:
> K,
>
> Here's how I got SetupBld.exe from WiX to behave like you wanted: 
> http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.

Oh, I think I've got it now, or at least am getting there.  I
re-reread your blog and managed to create both release and debug
versions of setupexe.exe per your instructions.  I copied setupexe.exe
to my stubs directory and ran with an argument of -setup
Stubs\setupexe.exe to test setupbld against my newly-generated build
of setupexe.exe.  That worked fine.

Now the question is: per your instructions how do I define a custom
title and icon?  I'm looking at wixver.h, WixDistribution.h and
setup.RC and I'm not seeing any #define that would explicitly allow me
to define an icon or title for my .exe.

What am I missing?  I'm sure it's something trivial.  Thanks again for
your response and excellent tutorial!

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How do to remove shortcuts from older installs

[spsingam]

hi All, 

Problem:

I have installed some files, registry keys, directories and shortcuts from
my CoffeeShop.msi, this was developed using Wise for Windows Installer.

Then i found WIX, and developed and new product and a new MSI. The new msi
is called CoffeeCo.msi.

Now, when i execute my CoffeeCo.msi, i want it to remove all traces of
CoffeeShop from the machine.


1. How do i remove the shortcuts that appear on the Start Menu, Desktop and
program files ?

2. How do i find what registry keys i have to remove? (WISE) 


Anyone with some good examples ?

Thanks.
 
-- 
View this message in context: 
http://n2.nabble.com/How-do-to-remove-shortcuts-from-older-installs-tp3971017p3971017.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

On Sun, Nov 8, 2009 at 1:05 PM, John Robbins  wrote:
> K,
>
> Here's how I got SetupBld.exe from WiX to behave like you wanted: 
> http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.

John, thanks for your response and well-written blog entry.

However, I still don't see my title or bitmap image when I run the
following command:

  C:\My Product>setupbld -title "My Application 1.0.0" -bitmap
Images\some-real.bmp -msu MyInput.msi -out MySetup.exe -setup
Stubs\Setup.exe

Interestingly, it *looks* like setupbld checks that -bitmap (file)
actually exists as setupbld will error out if it doesn't exist.  I
just don't see some-real.bmp appear as the icon for my .exe when I'm
through with setupbld.  I also don't see "My Application 1.0.0" appear
anywhere when I try to install from the .exe.

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Update fails if files have been modified

[Thomas Singer]

According to my understanding, I've tried to summarize all information and
the solution in our blog:

 http://blog.syntevo.net/2009/11/08/125770902.html

If something is wrong, please let me know. Thanks in advance.

Tom


Thomas Singer wrote:
> Thanks for the hint to the File Versioning Rules:
> 
>  http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx
> 
> Do I understand it correctly, that file versions and languages solely apply
> to .exe/.dll or similar files, but not to, for example, .jar files which are
> nothing else than .zip files? Then the following paragraph should explain my
> situation well:
> 
> | Nonversioned Files are User Data—If the Modified date is later than the
> | Create date for the file on the computer, do not install the file because
> | user customizations would be deleted. If the Modified and Create dates
> | are the same, install the file. If the Create date is later than the
> | Modified date, the file is considered unmodified, install the file.
> 
> Tom
> 
> 
> Rob Mensching wrote:
>> You might read through the File Versioning topic in the MSI SDK. It talks
>>  about all the rules. They aren't completely simple.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[John Robbins]

K,

Here's how I got SetupBld.exe from WiX to behave like you wanted: 
http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.

Hope it helps!

John
Wintellect
http://www.wintellect.com
877-968-5528

>-Original Message-
>From: kerbe...@noopy.org [mailto:kerbe...@noopy.org]
>Sent: Sunday, November 08, 2009 9:12 AM
>To: General discussion for Windows Installer XML toolset.
>Subject: [WiX-users] setupbld and -bitmap not supported? -title not
>supported?
>
>Hello,
>
>I am running the most current stable build of Wix 3.0.  I'm delighted
>with the product on the whole but I've reached a sticking point in
>distributing packages of my product.
>
>Basically, I preferred to have "fancy" electronic packaging for my
>product and as such preferred not to use the default icon for .msi.
>To get around this I decided to wrap my .msi in a .exe file -- as I
>assumed this would allow me to use a custom icon for my package.  I
>grabbed the setup stub for setup.exe from my Wix binaries directory
>and put it in a local Stubs directory; I refer to the stub when I run
>setupbld.exe.
>
>Unfortunately when I follow Jon Torresdal's instructions for using
>setupbld.exe I am unable to either specify a -bitmap or -title.  When
>I specify -title, my setup.exe is built but I cannot run it (nothing
>happens).  When I specify -bitmap, my image does not appear next to
>setup.exe in Explorer.  When I omit -title and just specify -bitmap I
>can run my .exe but I still get the default .msi icon.
>
>Does anyone know what might be wrong or if -bitmap is supported at all?
>
>--
>K
>
>
>--
>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-
>Day
>trial. Simplify your report design, integration and deployment - and
>focus on
>what you do best, core application coding. Discover what's new with
>Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>___
>WiX-users mailing list
>WiX-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is this a GUID matching problem - how to resolve.

[Paul Brook]

Blair,

Thanks for the explanation. Regarding your last paragraph about matching up 
GUIDs between installs.

"The only way that happens is by making the component guids match. And the
best way to do that is to not autogenerate them, or if you must autogenerate
them, use "*" as the component guid values so that the binder will produce
the component guid values in a stable way."

I am using "*" to generate the GUIDS in my WIX file. Obviously these are not 
matching the GUIDs created by Visual Studio in the Deployment Project .msi I am 
replacing, so I dumped the .msi using dark and realize I have a lot of typing 
to do to copy in each GUID.

The question is this. Is it worth the effort to copy all the GUIDs into the new 
installer? Considering that doing uninstall early in the process cleanly 
uninstalls the old version and correctly installs the new one, what advantages 
are gained? I am installing around 80 to 100 files.

At this point I am willing to do the RemoveExistingProducts 
After="InstallInitialize" as long as there are no problems lurking that will 
bite the process down the line.

Thanks for help.

Paul



-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Saturday, November 07, 2009 6:14 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Is this a GUID matching problem - how to resolve.

Each of your files that stay in the same directories need to have components
that keep the same guid values. If you don't drastically change your
installation layouts from build-to-build (which is most of us) it is
recommended that you write your installation once, and then update it on an
as-needed basis (instead of autogenerating it each time).

The reason mismatching the component guids causes what you are seeing is as
follows:

NewProduct (over)writes the files in the installation based on what Windows
Installer thinks are brand new components (the new guids). Then OldProduct
erases the files (ignoring what versions or timestamps they may have) when
removing the old components (since the components don't have any other
products using them). The repair rewrites the files (since they are missing)
and you are good to go (after the repair).

Here is what happens when you push up the scheduling of
RemoveExistingProducts:

OldProduct removes its registration of all the components it contains,
erasing all of the content for those components will no longer exist. Then
NewProduct registers itself for each component it contains and writes their
resources out to disk/registry, etc.

Here is what you want to happen:

NewProduct registers itself for each component it contains (making those
components have two products) and overwrites the files that have newer
version numbers (and possibly also overwriting those with the same version
numbers depending on the value of REINSTALLMODE) as well as dealing with
files that don't have FileVersion values as per the docs on MSDN. Then
OldProduct removes its registration of all the components it contains,
erasing the resources associated with any components that disappear as a
result (along with any keypaths that don't share the same value with another
product, including the one that just installed).

The only way that happens is by making the component guids match. And the
best way to do that is to not autogenerate them, or if you must autogenerate
them, use "*" as the component guid values so that the binder will produce
the component guid values in a stable way.

-Original Message-
From: Paul Brook [mailto:pbr...@vaytek.com] 
Sent: Saturday, November 07, 2009 3:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is this a GUID matching problem - how to resolve.

I am building a WIX installer that will have to upgrade a Visual Studio
deployment project .msi. When I run the major upgrade installer it replaces
the entry in the Program and Features list OK but none of the files are left
after the RemoveExistingProducts Before="InstallFinalize" (tried both Before
or After). A repair gets the files installed.

I finally set it to RemoveExistingProducts After="InstallInitialize" and
that solved the problem but I am still wondering why the update didn't work.
The files in the upgrade all had newer time stamps but some had the same
version number although some did have newer version numbers.

Is this a component GUID mismatch problem? If so how can I get around it?
The Visual Studio version of the installer sequences the remove step just
before the finalize step and I wanted to continue to do that. I am
installing VC merge modules and their remove step follows the finalize step.

Best Regards

Paul

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with
Crystal Reports n

[WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

Hello,

I am running the most current stable build of Wix 3.0.  I'm delighted
with the product on the whole but I've reached a sticking point in
distributing packages of my product.

Basically, I preferred to have "fancy" electronic packaging for my
product and as such preferred not to use the default icon for .msi.
To get around this I decided to wrap my .msi in a .exe file -- as I
assumed this would allow me to use a custom icon for my package.  I
grabbed the setup stub for setup.exe from my Wix binaries directory
and put it in a local Stubs directory; I refer to the stub when I run
setupbld.exe.

Unfortunately when I follow Jon Torresdal's instructions for using
setupbld.exe I am unable to either specify a -bitmap or -title.  When
I specify -title, my setup.exe is built but I cannot run it (nothing
happens).  When I specify -bitmap, my image does not appear next to
setup.exe in Explorer.  When I omit -title and just specify -bitmap I
can run my .exe but I still get the default .msi icon.

Does anyone know what might be wrong or if -bitmap is supported at all?

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Update fails if files have been modified

[Thomas Singer]

Thanks for the hint to the File Versioning Rules:

 http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx

Do I understand it correctly, that file versions and languages solely apply
to .exe/.dll or similar files, but not to, for example, .jar files which are
nothing else than .zip files? Then the following paragraph should explain my
situation well:

| Nonversioned Files are User Data—If the Modified date is later than the
| Create date for the file on the computer, do not install the file because
| user customizations would be deleted. If the Modified and Create dates
| are the same, install the file. If the Create date is later than the
| Modified date, the file is considered unmodified, install the file.

Tom


Rob Mensching wrote:
> You might read through the File Versioning topic in the MSI SDK. It talks
>  about all the rules. They aren't completely simple.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users