Re: [WiX-users] Two Entries in Add or Remove Programs

[Alex Shevchuk]

Hi Charles,

Could you share your , , , , and
 elements? Also, context in which upgrade is
installed is the same as 1.0 version was installed, no changes in ALLUSER
property, right?

Alex




-Original Message-
From: Chuck [mailto:electroch...@att.net] 
Sent: Wednesday, May 13, 2009 9:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

Alex Shevchuk wrote:
> Well, if per-user/per-machine context did not change, I can only
> suggest comparing your upgrade steps to steps in here:
> ...from-msi-to-wix-part-8-major-upgrade.aspx

I worked through that page of instructions. That resulted in a few changes. 
In the Package element I added SummaryCodepage="1252", a few Keywords, 
ShortNames="no" AdminImage="no" and ReadOnly="no".

Apparently I still have problems with FindRelatedProducts. Next I'm going to

analyze the installation log.

-- 
Charles



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Chuck]

Alex Shevchuk wrote:
> Well, if per-user/per-machine context did not change, I can only
> suggest comparing your upgrade steps to steps in here:
> ...from-msi-to-wix-part-8-major-upgrade.aspx

I worked through that page of instructions. That resulted in a few changes. 
In the Package element I added SummaryCodepage="1252", a few Keywords, 
ShortNames="no" AdminImage="no" and ReadOnly="no".

Apparently I still have problems with FindRelatedProducts. Next I'm going to 
analyze the installation log.

-- 
Charles


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Command line property passing to old msi during upgrade

[Alex Shevchuk]

>If I pass a property to my msi via command line, it seems like it is only
>reflected in the current msi context but not when removeexistingproducts is
>called to uninstall the old product. Is tehre any way to make this public
>property pass to old msi as well? 

You need to preserve value of property in registry:
http://blogs.technet.com/alexshev/archive/2009/05/13/preserving-properties-u
sed-during-install.aspx 


Alex



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

[Brian Rogers]

Hey Roy,

This is great news! Thank you for providing all the information to resolve
the bugs. I hope that this version will get you through until the next
version . All further bugs will be held until feature works starts
then.

I appreciate your feedback and support while we addressed these issues.

Thanks,

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


On Wed, May 13, 2009 at 3:19 PM, Roy Abou Assaly wrote:

>
> Yes it does.  I had to wait to update the build with the latest version due
> to other technical reasons, but after installing the latest version,
> everything worked right off the bat.  I tested with several modules and all
> the DLLs were registered.
>
> I also made a test installation package where I install 1 DLL and I
> monitored my application to see if the DLL was indeed registered.  It
> worked.  I did a before scenario where I basically unregistered the DLL,
> ran
> the application and saw that it complained about the missing the DLL, then
> I
> installed the test package with the DLL in question, and the application
> worked.
>
> So yeah...I tried to be as thorough as possible as releasing a non-working
> package is out of the question for me.  I definitely have a lot of
> confidence in Heat.
>
> Roy
>
>
> Brian Rogers wrote:
> >
> > Hey Roy,
> >
> > Thanks for the positive feedback and metric data!
> >
> > I am curious, does your installation package, once installed, work
> > correctly?
> >
> > Thanks,
> >
> > Brian Rogers
> > "Intelligence removes complexity." - Me
> > http://icumove.spaces.live.com
> >
> >
> > On Wed, May 13, 2009 at 8:30 AM, Roy Abou Assaly
> > wrote:
> >
> >>
> >> Great Work Brian!!
> >>
> >> I just incorporated WiX 3.0.5308 into our build and harvested all 128
> VB6
> >> COM DLLs.  Your fix works like a charm:
> >>
> >> [exec] heat.exe : warning HEAT5156 : Ignoring the registry key
> >> 'Interface\{F3DB7AC0-A581-48C6-A973-8860578A77E1}\ProxyStubClsid/', it
> >> has
> >> already been added to the component 'EstimationEngine.dll'. The registry
> >> key
> >> value '{00020424---C000-0046}' will not be harvested.
> >>
> >> Also, here are some statistics for Heat when I harvested my 128 files:
> >>
> >> Version 3.0.4923:  WiX file produced is 25540 lines, 4.7 MB
> >> Version 3.0.5308:  WiX file produced is 3794 lines, 601 KB
> >>
> >> That's a great performance improvement!
> >>
> >> Thanks again for all the help.  Heat is definitely a rock solid tool.
> >>
> >> Roy
> >>
> >>
> >>
> >> Roy Abou Assaly wrote:
> >> >
> >>  > I have filed the following bug:
> >> >
> >>
> https://sourceforge.net/tracker/?func=detail&atid=642714&aid=2783049&group_id=105970
> >> > and included test cases and the binary where you can reproduce how
> >> light
> >> > is broken on the COM VB6 WiX output from Heat from version 3.0.4923 to
> >> > 3.0.5224.
> >> >
> >> > Please let me know if I can be of any help at all.
> >> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2886906.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
> i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Rollback Custom Action during Upgrade

[Richard]

In article <1242193011087-2879162.p...@n2.nabble.com>,
achandrapano   writes:

> What should I look for in the log file?

Call MsiProcessMessage immediately from your rollback CA to write
something into the log to confirm that your CA was indeed called.

> effect. Is there any way to test a rollback CA execution? Like maybe instead
> of calling a binary file or DLL file, to just pop up a box?

You can either do standard unit testing on your CA code (see design
patterns for unit testing at ), or you can
add a type 19 CA at the end of your install transaction, just before
InstallFinalize to force a rollback of your transaction.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problems building WIX 2.0585 on a network drive - getting namespace name 'Extensions' does not exist in the class or namespace 'Microsoft.Tools.WindowsInstallerXml'

[Rob Mensching]

Not something we really support but did you make sure you trusted all of 
the assemblies? Maybe that is the issue since it looks like the MMC 
extension is failing to load.

Steven Chin wrote:
> I have installed WIX to a network drive and am trying to build it.  I took 
> care of the System.Security.Permissions already by configuring .NET Framework 
> 1.1  zone security for the local intranet to full trust but now I am running 
> into this error:
>
> [loadtasks] Scanning assembly "Microsoft.Tools.WindowsInstallerXml.NAntTasks" 
> for extensions.
>   [csc] Compiling 3 files to 
> 'S:\workspaces\schin.3rdparty\tmw\wix-src\Release\debug\WixMMCExtension.dll'.
>   [csc] 
> s:\workspaces\schin.3rdparty\tmw\wix-src\src\ext\MMCExtension\wixext\AssemblyInfo.cs(25,43):
>  error CS0234: The type or namespace name 'Extensions' does not exist in the 
> class or namespace 'Microsoft.Tools.WindowsInstallerXml' (are you missing an 
> assembly reference?)
>
> BUILD FAILED - 1 non-fatal error(s), 1 warning(s)
>
> S:\workspaces\schin.3rdparty\tmw\wix-src\src\ext\mmcextension\mmcextension.build(71,6):
> External Program Failed: c:\WINNT\Microsoft.NET\Framework\v1.1.4322\csc.exe 
> (return code was 1)
>
> I do not have this problem building WIX on the local drive.  Does anybody 
> know why this is happening?  Thanks.
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cross-Feature dependencies

[Rob Mensching]

Yes. Features are a "tree" but Components can be duplicated throughout 
as leaves as you want. In the end, a Component is installed as long as 
one of its Features is installed.

Chris Ridd wrote:
> Hi,
>
> I've been working on properly supporting feature selection (Custom
> installs) in our packages. So far so good, except I've got a slight
> conceptual problem.
>
> I install into 2 different directories, both of which are user-
> configurable. So my WXS looks kind of like:
>
> Directory "INSTALLDIR" [...]
>Components n + m
> Directory "DATADIR" [...]
>Components x + y
> Feature Id="Software" ConfigurableDirectory="INSTALLDIR" [...]
>Feature Id="A"
>  ComponentRefs n
>Feature Id="B"
>  ComponentRefs m
> Feature Id="Data" ConfigurableDirectory="DATADIR" [...]
>Feature Id="Adata"
>  ComponentRefs x
>Feature Id="Bdata"
>  ComponentRefs y
>
> (and so on). Apologies if I've got the XML attribute names wrong, I'm
> at home and this is from memory.
>
> Now feature "A" requires components installed in DATADIR, say "x". Can
> I just include those ComponentRefs under Feature "A", even though they
> refer to things installed under a different Directory? Or will that
> stop the "x" components from being installed in the user-specified
> DATADIR?
>
> Cheers,
>
> Chris
>
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] UI Dialog on uninstallation

[Rob Mensching]

There was a thread about this recently. Think the summary was that this 
is not possible.

Hukumchand Shah wrote:
> Hi All,
>
> I want to show one UI dialog when user tries to uninstall the application
> from add/remove panel.
> How can I do this in WIX?
> Does any one know this?
>
> Thanks,
> Hukum
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] inconsistent progressbar

[Rob Mensching]

You could write an External UI handler. MSI SDK shows how.

Hukumchand Shah wrote:
> Hi All,
>
> I have created the WIX installer. In this problem is installer progress bar
> is inconsistent.
> So How I can make it consistent or move it according to my need?
>
> Thanks,
> Hukum
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Command line property passing to old msi during upgrade

[achandrapano]

If I pass a property to my msi via command line, it seems like it is only
reflected in the current msi context but not when removeexistingproducts is
called to uninstall the old product. Is tehre any way to make this public
property pass to old msi as well? 
-- 
View this message in context: 
http://n2.nabble.com/Command-line-property-passing-to-old-msi-during-upgrade-tp2887222p2887222.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] (no subject)

[Schaff, Stephen]

I have a wix project that creates a website.  The certificate that that
website uses is already be present on the machine being installed to.
Is there a way to make the installer associate the website with the
existing installer?  (I can do this step manually, but I would rather
have the installer do it).

Stephen

- --
The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawful. If you
are not the intended recipient, please promptly delete this e-mail
and notify the sender of the delivery error or you may call ARUP
Laboratories Compliance Hot Line in Salt Lake City, Utah USA at (+1
(800) 522-2787 ext. 2100

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Alex Shevchuk]

> The 'two entries' problem continues.

Well, if per-user/per-machine context did not change, I can only suggest
comparing your upgrade steps to steps in here:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-
major-upgrade.aspx 

Alex



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Schaff, Stephen]

Opps, responded to the wrong email
So very sorry...

-Original Message-
From: Schaff, Stephen [mailto:stephen.sch...@aruplab.com] 
Sent: Wednesday, May 13, 2009 4:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

That fixed it!  Thanks!

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com] 
Sent: Wednesday, May 13, 2009 1:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

That means it didn't find the previous version for some reason otherwise
it would mention the ProductCode guid of the discovered product. What's
actually in the Upgrade table in the MSI file? I'm wondering if the
version range is really correct. 

That location for REP is more efficient because the file replacement
rules are such that you have many files that aren't going to be updated.
If a lot are going to be updated anyway the efficiency decreases.
However it's not a safe location because of the rollback issue. There is
a similar efficient location (assuming efficiency is valued more than
safety ;=) ) which is directly before InstallFinalize using
[InstallExecute, RemovePreviousVersions, InstallFinalize ], which is
what the 3rd bullet is saying - the rollback of the new install means
the new product won't be installed, and the older product uninstall is
rolled back leaving it installed, so you're back where you started. 

Phil Wilson 


-Original Message-
From: Chuck [mailto:electroch...@att.net] 
Sent: Wednesday, May 13, 2009 12:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

Wilson, Phil wrote:
> Get an MSI log to see what's going on. Look at all instances of
> FindRelatedProducts to see if it's detecting your older product.

There are two sections of FindRelatedProducts in the log for the 1.1
version 
upgrade installation.

MSI (c) (28:8C) [18:56:27:953]: Doing action: FindRelatedProducts
MSI (c) (28:8C) [18:56:27:968]: Note: 1: 2205 2:  3: ActionText
Action 18:56:27: FindRelatedProducts. Searching for related applications
Action start 18:56:27: FindRelatedProducts.
Action ended 18:56:27: FindRelatedProducts. Return value 1.

and

MSI (s) (C8:34) [18:56:32:968]: Doing action: FindRelatedProducts
MSI (s) (C8:34) [18:56:32:984]: Note: 1: 2205 2:  3: ActionText
Action 18:56:32: FindRelatedProducts. Searching for related applications
Action start 18:56:32: FindRelatedProducts.
MSI (s) (C8:34) [18:56:32:984]: Skipping FindRelatedProducts action:
already 
done on client side
Action ended 18:56:32: FindRelatedProducts. Return value 0.

Does that look right?

> Why is REP after InstallFinalize?

I was following the recommendation in the fourth bullet point of the 
Sequence Restrictions section of 
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx. I've tried
the 
other possibilities too. I still end up with two entries in the Add or 
Remove Programs table.

-- 
Charles



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

- --
The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawful. If you
are not the intended recipient, please promptly delete this e-mail
and notify the sender of the delivery error or you may call ARUP
Lab

Re: [WiX-users] Two Entries in Add or Remove Programs

[Chuck]

Schaff, Stephen wrote:
> That fixed it!  Thanks!

I think you replied to the wrong message, Stephen. The 'two entries' problem 
continues.

-- 
Charles


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Schaff, Stephen]

That fixed it!  Thanks!

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com] 
Sent: Wednesday, May 13, 2009 1:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

That means it didn't find the previous version for some reason otherwise
it would mention the ProductCode guid of the discovered product. What's
actually in the Upgrade table in the MSI file? I'm wondering if the
version range is really correct. 

That location for REP is more efficient because the file replacement
rules are such that you have many files that aren't going to be updated.
If a lot are going to be updated anyway the efficiency decreases.
However it's not a safe location because of the rollback issue. There is
a similar efficient location (assuming efficiency is valued more than
safety ;=) ) which is directly before InstallFinalize using
[InstallExecute, RemovePreviousVersions, InstallFinalize ], which is
what the 3rd bullet is saying - the rollback of the new install means
the new product won't be installed, and the older product uninstall is
rolled back leaving it installed, so you're back where you started. 

Phil Wilson 


-Original Message-
From: Chuck [mailto:electroch...@att.net] 
Sent: Wednesday, May 13, 2009 12:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

Wilson, Phil wrote:
> Get an MSI log to see what's going on. Look at all instances of
> FindRelatedProducts to see if it's detecting your older product.

There are two sections of FindRelatedProducts in the log for the 1.1
version 
upgrade installation.

MSI (c) (28:8C) [18:56:27:953]: Doing action: FindRelatedProducts
MSI (c) (28:8C) [18:56:27:968]: Note: 1: 2205 2:  3: ActionText
Action 18:56:27: FindRelatedProducts. Searching for related applications
Action start 18:56:27: FindRelatedProducts.
Action ended 18:56:27: FindRelatedProducts. Return value 1.

and

MSI (s) (C8:34) [18:56:32:968]: Doing action: FindRelatedProducts
MSI (s) (C8:34) [18:56:32:984]: Note: 1: 2205 2:  3: ActionText
Action 18:56:32: FindRelatedProducts. Searching for related applications
Action start 18:56:32: FindRelatedProducts.
MSI (s) (C8:34) [18:56:32:984]: Skipping FindRelatedProducts action:
already 
done on client side
Action ended 18:56:32: FindRelatedProducts. Return value 0.

Does that look right?

> Why is REP after InstallFinalize?

I was following the recommendation in the fourth bullet point of the 
Sequence Restrictions section of 
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx. I've tried
the 
other possibilities too. I still end up with two entries in the Add or 
Remove Programs table.

-- 
Charles



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

- --
The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawful. If you
are not the intended recipient, please promptly delete this e-mail
and notify the sender of the delivery error or you may call ARUP
Laboratories Compliance Hot Line in Salt Lake City, Utah USA at (+1
(800) 522-2787 ext. 2100

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world -

Re: [WiX-users] Two Entries in Add or Remove Programs

[Chuck]

Alex Shevchuk wrote:
> Product/@Version must be changed as well and whatever is used as a
> value for Product/@Version must be used for UpgradeVesrion/@Minimum
> where Property="NEWERVERSIONDETECTED".

I neglected to show that in my initial message. It uses the same binder as 
the Upgrade elements:

http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] how to patch/bootstrap an old msi that is installed

[achandrapano]

During an upgrade, what is the easiest way to patch the older msi? Can this
be done via the new msi or does a separate patch have to be issued and
installed?
-- 
View this message in context: 
http://n2.nabble.com/how-to-patch-bootstrap-an-old-msi-that-is-installed-tp2886948p2886948.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] RegistrySearch and RegistryValue

[Alex Shevchuk]

>And how about QWORD value?

Looks like Registry table
(http://msdn.microsoft.com/en-us/library/aa371168(VS.85).aspx) supports
only:

- REG_SZ
- REG_MULTI_SZ
- REG_EXPAND_SZ
- REG_BINARY
- REG_DWORD

No REG_QWORD and XXX_LITTLE_ENDIAN (or REG_LINK) support, I think.


Alex



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

[Roy Abou Assaly]

Yes it does.  I had to wait to update the build with the latest version due
to other technical reasons, but after installing the latest version,
everything worked right off the bat.  I tested with several modules and all
the DLLs were registered.

I also made a test installation package where I install 1 DLL and I
monitored my application to see if the DLL was indeed registered.  It
worked.  I did a before scenario where I basically unregistered the DLL, ran
the application and saw that it complained about the missing the DLL, then I
installed the test package with the DLL in question, and the application
worked.

So yeah...I tried to be as thorough as possible as releasing a non-working
package is out of the question for me.  I definitely have a lot of
confidence in Heat.

Roy


Brian Rogers wrote:
> 
> Hey Roy,
> 
> Thanks for the positive feedback and metric data!
> 
> I am curious, does your installation package, once installed, work
> correctly?
> 
> Thanks,
> 
> Brian Rogers
> "Intelligence removes complexity." - Me
> http://icumove.spaces.live.com
> 
> 
> On Wed, May 13, 2009 at 8:30 AM, Roy Abou Assaly
> wrote:
> 
>>
>> Great Work Brian!!
>>
>> I just incorporated WiX 3.0.5308 into our build and harvested all 128 VB6
>> COM DLLs.  Your fix works like a charm:
>>
>> [exec] heat.exe : warning HEAT5156 : Ignoring the registry key
>> 'Interface\{F3DB7AC0-A581-48C6-A973-8860578A77E1}\ProxyStubClsid/', it
>> has
>> already been added to the component 'EstimationEngine.dll'. The registry
>> key
>> value '{00020424---C000-0046}' will not be harvested.
>>
>> Also, here are some statistics for Heat when I harvested my 128 files:
>>
>> Version 3.0.4923:  WiX file produced is 25540 lines, 4.7 MB
>> Version 3.0.5308:  WiX file produced is 3794 lines, 601 KB
>>
>> That's a great performance improvement!
>>
>> Thanks again for all the help.  Heat is definitely a rock solid tool.
>>
>> Roy
>>
>>
>>
>> Roy Abou Assaly wrote:
>> >
>>  > I have filed the following bug:
>> >
>> https://sourceforge.net/tracker/?func=detail&atid=642714&aid=2783049&group_id=105970
>> > and included test cases and the binary where you can reproduce how
>> light
>> > is broken on the COM VB6 WiX output from Heat from version 3.0.4923 to
>> > 3.0.5224.
>> >
>> > Please let me know if I can be of any help at all.
>> >
> 

-- 
View this message in context: 
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2886906.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] RegistrySearch and RegistryValue

[Alex Ivanoff]

And how about QWORD value?


-Original Message-
From: Alex Shevchuk [mailto:shevc...@live.com] 
Sent: Tuesday, May 12, 2009 01:04
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] RegistrySearch and RegistryValue

Hi Alex,

Short answer: Yes, maybe, no.  :-)
Detailed answer:
http://blogs.technet.com/alexshev/archive/2009/05/11/is-it-possible-to-u
se-registrysearch-result-in-registryvalue.aspx

Regards,
Alex




-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Monday, May 11, 2009 10:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] RegistrySearch and RegistryValue

Is it possible to use RegistrySearch result in RegistryValue? Something
like this:





...





--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to Kodak, there's a perfect scanner to get the job done! With the NEW
KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all
image processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Alex Shevchuk]

>I go back to Wix Edit and change both the Product GUID and the Package
GUID. 
>The Upgrade ID GUID does not change. I rebuild the MSI setup package.
> ...
>
>
>  Maximum="!(bind.FileVersion.gssta_exe)"   IncludeMinimum="yes" 
>OnlyDetect="no" IncludeMaximum="no" Minimum="0.0.0.0" />
>  Minimum="!(bind.FileVersion.gssta_exe)" OnlyDetect="yes" 
>IncludeMinimum="yes" />
>


Product/@Version must be changed as well and whatever is used as a value for
Product/@Version must be used for UpgradeVesrion/@Minimum where
Property="NEWERVERSIONDETECTED".

Alex



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] UAC prompt on feature modification after installation

[Brooke Philpott]

When I do a fresh install I'm using a bootstrapper to launch the msi
with admin rights so I can perform a LogonUser call in order to validate
the account used during the execution phase for the service. I want to
do that validation up front so I don't get an error during the execution
phase which would roll back the whole install. Everything works fine
except today I noticed if I go to change in Add/Remove programs it
doesn't elevate. So, when I go to the UI page where I enter in the
credentials I get an error that I can't impersonate because I don't have
those privileges with my current token.

 

Is there a way to elevate upon change in add/remove programs? Is there a
better way to do the account validation to begin with?

 

-Brooke 

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Chuck]

Wilson, Phil wrote:
> That means it didn't find the previous version for some reason
> otherwise it would mention the ProductCode guid of the discovered
> product. What's actually in the Upgrade table in the MSI file? I'm
> wondering if the version range is really correct.

>From Orca, here are the two entries in the Upgrade table for the Version 1.1 
package:

UpgradeCode: {49AB249B-C143-412E-B138-6689533DC53A}
VersionMin: 1.1.0.0
VersionMax: [none]
Attributes: 258
ActionProperty: NEWERVERSIONDETECTED

UpgradeCode: {49AB249B-C143-412E-B138-6689533DC53A}
VersionMin: 0.0.0.0
VersionMax: 1.1.0.0
Attributes: 256
ActionProperty: OLDERVERSIONBEINGUPGRADED

> That location for REP is more efficient because the file replacement
> rules are such that you have many files that aren't going to be
> updated. If a lot are going to be updated anyway the efficiency
> decreases. However it's not a safe location because of the rollback
> issue. There is a similar efficient location (assuming efficiency is
> valued more than safety ;=) ) which is directly before
> InstallFinalize using  [InstallExecute, RemovePreviousVersions,
> InstallFinalize ], which is what the 3rd bullet is saying...

I have now moved RemovePreviousVersions to the position after InstallExecute 
and before InstallFinalize.

-- 
Charles


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Preserve registry settings on upgrade

[Alex Ivanoff]

This is what I am doing. I hoped there was a better way.


-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au] 
Sent: Wednesday, May 13, 2009 14:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Preserve registry settings on upgrade

Alex,

Use the Registry Search to read the values into Properties before the
upgrade, and use the Properties to write the registry settings.

Michael  


From: Alex Ivanoff [alex.ivan...@shavlik.com]
Sent: Thursday, 14 May 2009 12:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Preserve registry settings on upgrade

Is it possible to preserver registry settings on major upgrade and only
delete it on uninstall?




--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] IIS6 error-Failed while processing WebVirtualDirs

[Mike Carlson (DEV DIV)]

Your website element is a "website locator" (i.e. it has no parent component). 
That means the CA will look for this website on the local machine to install to 
(and fail the install if it isn't present), rather than create it if it doesn't 
exist. The logs in this case appear consistent with it failing to find the 
website it should install to.

Try either: A) putting your website element inside of a component (so that the 
website will be created if it doesn't exist), or B) making sure the website 
it's searching for exists on the target machine before installation.

Thanks,
Mike Carlson

-Original Message-
From: Schaff, Stephen [mailto:stephen.sch...@aruplab.com] 
Sent: Wednesday, May 13, 2009 12:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] IIS6 error-Failed while processing WebVirtualDirs

I am trying to get a simple wix project to install on IIS 6.  I have WIX 
3.0.5308.0 installed.

 

Here is the Product.wxs:

 



http://schemas.microsoft.com/wix/2006/wi"; 
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";>

  



 



 



  



  



  







   



  



 





  



 







  



 

When I run the install on a machine with IIS 5 installed it works fine.  If I 
run on a machine with IIS 6 Installed I get this error:

 

   Failed while processing WebVirtualDirs: (-2147024894)

 

 

Here is what seems to be the relevant lines in the log file:

--

MSI (s) (60:10) [13:25:01:775]: Executing op: 
CustomActionSchedule(Action=RollbackMetabaseTransaction,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)

MSI (s) (60:10) [13:25:01:775]: Executing op: 
ActionStart(Name=CommitMetabaseTransaction,Description=Committing IIS Metabase 
Transaction,)

MSI (s) (60:10) [13:25:01:775]: Executing op: 
CustomActionSchedule(Action=CommitMetabaseTransaction,ActionType=11777,Source=BinaryData,Target=**,CustomActionData=**)

MSI (s) (60:10) [13:25:01:775]: Executing op: 
ActionStart(Name=ConfigureIIsExec,,)

MSI (s) (60:10) [13:25:01:791]: Executing op: 
CustomActionSchedule(Action=ConfigureIIsExec,ActionType=3073,Source=BinaryData,Target=ConfigureIIsExec,CustomActionData=ConfigureIIs€1€0€0€2€1€0€0€2€1€16€1€AppPool€1€Name€1€Component_€1€Attributes€2€User_€1€RecycleMinutes€2€RecycleRequests€2€RecycleTimes€1€VirtualMemory€2€PrivateMemory€2€IdleTimeout€2€QueueLimit€2€CPUMon€1€MaxProc€2€ISInstalled€2€ISAction€2€3€WebAppPool€sbsite€ProductComponent€0€€-2147483648€-2147483648€€-2147483648€-2147483648€-2147483648€-2147483648€0€-2147483648€2€3€4€2€1€0€0€2€1€0€0€2€1€0€0€2€1€15€1€DirProperties€1€Access€2€Authorization€2€AnonymousUser_€1€IIsControlledPassword€2€LogVisits€2€Index€2€DefaultDoc€1€AspDetailedError€2€HttpExpires€1€CacheControlMaxAge€2€CacheControlCustom€1€NoCustomError€2€AccessSSLFlags€2€AuthenticationProviders€1€3€WebDir€-2147483648€-2147483648€€0€-2147483648€-2147483648€Default.aspx€-2147483648€€-2147483648€€-2147483648€-2147483648€€4€2€1€0€0€2€1€0€0€2€1€12€1€Name€1€Isolation€2€AllowSessions€2€SessionTimeout€2€Buffer€2€ParentPaths€2€DefaultScript€1€ScriptTimeout€2€ServerDebugging€2€Cl

MSI (s) (60:50) [13:25:01:822]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI40A5.tmp, Entrypoint: ConfigureIIsExec

ConfigureIIsExec:  Skipping ScaWebSvcExtRead() because IIsWebServiceExtension 
data not present

ConfigureIIsExec:  Skipping ScaMimeMapRead() - required table not present

ConfigureIIsExec:  Skipping ScaHttpHeaderRead() - required tables not present.

ConfigureIIsExec:  Skipping ScaWebErrorRead() - required tables not present.

ConfigureIIsExec:  Skipping ScaInstallWebDirs() because IIsWebDir table not 
present

ConfigureIIsExec:  A matching web object in memory was found, but the web 
object in memory has no associated base

ConfigureIIsExec:  Error 0x80070002: Failed to find Web base

ConfigureIIsExec:  Error 0x80070002: Failed to get base of web: 
InstallToWebsite for VirtualDir

ConfigureIIsExec:  Error 0x80070002: failed while processing WebVirtualDirs

--

 

I could not find anything about this on Google.

Any help is greatly appreciated.

 

Stephen

 

 

 


- --
The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawfu

Re: [WiX-users] Two Entries in Add or Remove Programs

[Wilson, Phil]

That means it didn't find the previous version for some reason otherwise it 
would mention the ProductCode guid of the discovered product. What's actually 
in the Upgrade table in the MSI file? I'm wondering if the version range is 
really correct. 

That location for REP is more efficient because the file replacement rules are 
such that you have many files that aren't going to be updated. If a lot are 
going to be updated anyway the efficiency decreases. However it's not a safe 
location because of the rollback issue. There is a similar efficient location 
(assuming efficiency is valued more than safety ;=) ) which is directly before 
InstallFinalize using  [InstallExecute, RemovePreviousVersions, InstallFinalize 
], which is what the 3rd bullet is saying - the rollback of the new install 
means the new product won't be installed, and the older product uninstall is 
rolled back leaving it installed, so you're back where you started. 

Phil Wilson 


-Original Message-
From: Chuck [mailto:electroch...@att.net] 
Sent: Wednesday, May 13, 2009 12:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs

Wilson, Phil wrote:
> Get an MSI log to see what's going on. Look at all instances of
> FindRelatedProducts to see if it's detecting your older product.

There are two sections of FindRelatedProducts in the log for the 1.1 version 
upgrade installation.

MSI (c) (28:8C) [18:56:27:953]: Doing action: FindRelatedProducts
MSI (c) (28:8C) [18:56:27:968]: Note: 1: 2205 2:  3: ActionText
Action 18:56:27: FindRelatedProducts. Searching for related applications
Action start 18:56:27: FindRelatedProducts.
Action ended 18:56:27: FindRelatedProducts. Return value 1.

and

MSI (s) (C8:34) [18:56:32:968]: Doing action: FindRelatedProducts
MSI (s) (C8:34) [18:56:32:984]: Note: 1: 2205 2:  3: ActionText
Action 18:56:32: FindRelatedProducts. Searching for related applications
Action start 18:56:32: FindRelatedProducts.
MSI (s) (C8:34) [18:56:32:984]: Skipping FindRelatedProducts action: already 
done on client side
Action ended 18:56:32: FindRelatedProducts. Return value 0.

Does that look right?

> Why is REP after InstallFinalize?

I was following the recommendation in the fourth bullet point of the 
Sequence Restrictions section of 
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx. I've tried the 
other possibilities too. I still end up with two entries in the Add or 
Remove Programs table.

-- 
Charles


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] IIS6 error-Failed while processing WebVirtualDirs

[Schaff, Stephen]

I am trying to get a simple wix project to install on IIS 6.  I have WIX 
3.0.5308.0 installed.

 

Here is the Product.wxs:

 



http://schemas.microsoft.com/wix/2006/wi"; 
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";>

  



 



 



  



  



  







   



  



 





  



 







  



 

When I run the install on a machine with IIS 5 installed it works fine.  If I 
run on a machine with IIS 6 Installed I get this error:

 

   Failed while processing WebVirtualDirs: (-2147024894)

 

 

Here is what seems to be the relevant lines in the log file:

--

MSI (s) (60:10) [13:25:01:775]: Executing op: 
CustomActionSchedule(Action=RollbackMetabaseTransaction,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)

MSI (s) (60:10) [13:25:01:775]: Executing op: 
ActionStart(Name=CommitMetabaseTransaction,Description=Committing IIS Metabase 
Transaction,)

MSI (s) (60:10) [13:25:01:775]: Executing op: 
CustomActionSchedule(Action=CommitMetabaseTransaction,ActionType=11777,Source=BinaryData,Target=**,CustomActionData=**)

MSI (s) (60:10) [13:25:01:775]: Executing op: 
ActionStart(Name=ConfigureIIsExec,,)

MSI (s) (60:10) [13:25:01:791]: Executing op: 
CustomActionSchedule(Action=ConfigureIIsExec,ActionType=3073,Source=BinaryData,Target=ConfigureIIsExec,CustomActionData=ConfigureIIs€1€0€0€2€1€0€0€2€1€16€1€AppPool€1€Name€1€Component_€1€Attributes€2€User_€1€RecycleMinutes€2€RecycleRequests€2€RecycleTimes€1€VirtualMemory€2€PrivateMemory€2€IdleTimeout€2€QueueLimit€2€CPUMon€1€MaxProc€2€ISInstalled€2€ISAction€2€3€WebAppPool€sbsite€ProductComponent€0€€-2147483648€-2147483648€€-2147483648€-2147483648€-2147483648€-2147483648€0€-2147483648€2€3€4€2€1€0€0€2€1€0€0€2€1€0€0€2€1€15€1€DirProperties€1€Access€2€Authorization€2€AnonymousUser_€1€IIsControlledPassword€2€LogVisits€2€Index€2€DefaultDoc€1€AspDetailedError€2€HttpExpires€1€CacheControlMaxAge€2€CacheControlCustom€1€NoCustomError€2€AccessSSLFlags€2€AuthenticationProviders€1€3€WebDir€-2147483648€-2147483648€€0€-2147483648€-2147483648€Default.aspx€-2147483648€€-2147483648€€-2147483648€-2147483648€€4€2€1€0€0€2€1€0€0€2€1€12€1€Name€1€Isolation€2€AllowSessions€2€SessionTimeout€2€Buffer€2€ParentPaths€2€DefaultScript€1€ScriptTimeout€2€ServerDebugging€2€Cl

MSI (s) (60:50) [13:25:01:822]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI40A5.tmp, Entrypoint: ConfigureIIsExec

ConfigureIIsExec:  Skipping ScaWebSvcExtRead() because IIsWebServiceExtension 
data not present

ConfigureIIsExec:  Skipping ScaMimeMapRead() - required table not present

ConfigureIIsExec:  Skipping ScaHttpHeaderRead() - required tables not present.

ConfigureIIsExec:  Skipping ScaWebErrorRead() - required tables not present.

ConfigureIIsExec:  Skipping ScaInstallWebDirs() because IIsWebDir table not 
present

ConfigureIIsExec:  A matching web object in memory was found, but the web 
object in memory has no associated base

ConfigureIIsExec:  Error 0x80070002: Failed to find Web base

ConfigureIIsExec:  Error 0x80070002: Failed to get base of web: 
InstallToWebsite for VirtualDir

ConfigureIIsExec:  Error 0x80070002: failed while processing WebVirtualDirs

--

 

I could not find anything about this on Google.

Any help is greatly appreciated.

 

Stephen

 

 

 


- --
The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawful. If you
are not the intended recipient, please promptly delete this e-mail
and notify the sender of the delivery error or you may call ARUP
Laboratories Compliance Hot Line in Salt Lake City, Utah USA at (+1
(800) 522-2787 ext. 2100
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Preserve registry settings on upgrade

[Michael Osmond]

Alex,

Use the Registry Search to read the values into Properties before the upgrade, 
and use the Properties to write the registry settings.

Michael  


From: Alex Ivanoff [alex.ivan...@shavlik.com]
Sent: Thursday, 14 May 2009 12:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Preserve registry settings on upgrade

Is it possible to preserver registry settings on major upgrade and only
delete it on uninstall?



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Chuck]

Wilson, Phil wrote:
> Get an MSI log to see what's going on. Look at all instances of
> FindRelatedProducts to see if it's detecting your older product.

There are two sections of FindRelatedProducts in the log for the 1.1 version 
upgrade installation.

MSI (c) (28:8C) [18:56:27:953]: Doing action: FindRelatedProducts
MSI (c) (28:8C) [18:56:27:968]: Note: 1: 2205 2:  3: ActionText
Action 18:56:27: FindRelatedProducts. Searching for related applications
Action start 18:56:27: FindRelatedProducts.
Action ended 18:56:27: FindRelatedProducts. Return value 1.

and

MSI (s) (C8:34) [18:56:32:968]: Doing action: FindRelatedProducts
MSI (s) (C8:34) [18:56:32:984]: Note: 1: 2205 2:  3: ActionText
Action 18:56:32: FindRelatedProducts. Searching for related applications
Action start 18:56:32: FindRelatedProducts.
MSI (s) (C8:34) [18:56:32:984]: Skipping FindRelatedProducts action: already 
done on client side
Action ended 18:56:32: FindRelatedProducts. Return value 0.

Does that look right?

> Why is REP after InstallFinalize?

I was following the recommendation in the fourth bullet point of the 
Sequence Restrictions section of 
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx. I've tried the 
other possibilities too. I still end up with two entries in the Add or 
Remove Programs table.

-- 
Charles


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Two Entries in Add or Remove Programs

[Wilson, Phil]

Get an MSI log to see what's going on. Look at all instances of 
FindRelatedProducts to see if it's detecting your older product. 

Why is REP after InstallFinalize? This is outside the audited actions, and one 
of the consequences is that if the uninstall of the older product fails it will 
attempt to roll back and reinstall, leaving you with two entries in ARP. 


Phil Wilson 


-Original Message-
From: Chuck [mailto:electroch...@att.net] 
Sent: Tuesday, May 12, 2009 7:25 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Two Entries in Add or Remove Programs

I have been testing the major upgrade procedure under WiX Version 3.0.5217.0 
and Windows XP. I install version 1.0 of my application successfully. (It has 
the required Upgrade element.) To prepare for the next version of my 
application I increment the FILEVERSION, PRODUCTVERSION and FileVersion values 
in resource file from 1.0 to 1.1 and rebuild the executable. (WiX Edit reads 
the File Version--see below.)

I go back to Wix Edit and change both the Product GUID and the Package GUID. 
The Upgrade ID GUID does not change. I rebuild the MSI setup package.

Then I use this new package to install version 1.1 of my application. 
Version 1.1 of the program installs successfully but I am left with two entries 
in Control Panel > Add or Remove Programs. One points to version 1.0; the other 
points to version 1.1.


  
  



   

In the Add or Remove Programs table, if I select Remove for version 1.0 (after 
version 1.1 is installed) the application is not removed. (The table entry does 
go away.) If I select Remove for version 1.1, the application is removed.

What can I do to ensure that only the latest version is shown in the Add or 
Remove Programs table?

--
Charles




--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] signing output of setupbld

[Brooke Philpott]

I'm currently using setupbld to generate a setup wrapper. However when I
sign the output using signtool it corrupts the executable. Trying to run
the resultant exe post signing yields an error:

Activation context generation failed for "...\badsetup.exe".Error in
manifest or policy file "...\badsetup.exe" on line 0. Invalid Xml
syntax.

 

Has anyone see this before?

-Brooke

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Problems building WIX 2.0585 on a network drive - getting namespace name 'Extensions' does not exist in the class or namespace 'Microsoft.Tools.WindowsInstallerXml'

[Steven Chin]

I have installed WIX to a network drive and am trying to build it.  I took care 
of the System.Security.Permissions already by configuring .NET Framework 1.1  
zone security for the local intranet to full trust but now I am running into 
this error:

[loadtasks] Scanning assembly "Microsoft.Tools.WindowsInstallerXml.NAntTasks" 
for extensions.
  [csc] Compiling 3 files to 
'S:\workspaces\schin.3rdparty\tmw\wix-src\Release\debug\WixMMCExtension.dll'.
  [csc] 
s:\workspaces\schin.3rdparty\tmw\wix-src\src\ext\MMCExtension\wixext\AssemblyInfo.cs(25,43):
 error CS0234: The type or namespace name 'Extensions' does not exist in the 
class or namespace 'Microsoft.Tools.WindowsInstallerXml' (are you missing an 
assembly reference?)

BUILD FAILED - 1 non-fatal error(s), 1 warning(s)

S:\workspaces\schin.3rdparty\tmw\wix-src\src\ext\mmcextension\mmcextension.build(71,6):
External Program Failed: c:\WINNT\Microsoft.NET\Framework\v1.1.4322\csc.exe 
(return code was 1)

I do not have this problem building WIX on the local drive.  Does anybody know 
why this is happening?  Thanks.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to check for installed package in WiX 3.0 ?

[Wilson, Phil]

If you look at the Upgrade element in WiX you can use OnlyDetect - "yes" and a 
property. That property will be set if the range of versions in the Upgrade 
element is detected. 

Alex Shevchuk has a type 19 example in his MSI->Wix blog, 

http://blogs.technet.com/alexshev/archive/2008/02/21/from-msi-to-wix-part-5-custom-actions.aspx
 

and that goes in your UI and execute sequences after FindRelatedProducts. 

Phil Wilson 


-Original Message-
From: Mathieu Cartoixa [mailto:mathieu.carto...@hotmail.com] 
Sent: Wednesday, May 13, 2009 4:43 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to check for installed package in WiX 3.0 ?

Wilson, Phil a écrit :
> If the UpgradeCode for Crystal is reliable you could make an Upgrade table 
> entry for it with "only search" for the range of versions you expect - 
> that'll set a property you can use in a type 19 custom action. 

Mmmh... I have to admit I am far from being an expert in Windows 
Installer concepts. Do you have any links, or could you translate this 
in WiX tags that allow to achieve this (especially the "type 19 custom 
action" which is cryptic to me, to say the least) ? Pseudo WiX code 
would be more than enough.

Anyway, as I learned not to rely on anything concerning Crystal Reports, 
I'll probably stick with Eric's method for the time being.

Thanks for your help.

Mathieu Cartoixa


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Collecting info for multiple SQL Servers

[Jeff Reed]

Hi all,

I have an install where it may need to run SQL scripts on up to 2 different SQL 
servers.  I feel pretty comfortable collecting the information for one of those 
four with a UI screen, but I'm hoping to reuse the screen for all SQL Servers.  
From what little I know about UI development in an MSI, this seems to be pretty 
difficult, because you're essentially hardcoding property names for your 
various UI screens to push data to, and the installer uses the data from there. 
 How can I use the same screen to push to a different set of properties?

I was looking for suggestions on the cleanest way to approach this so that 
maintenance down the road is easy (should we add a 3rd or 4th SQL server, for 
example).  Is there a dynamic way to do it, or is it better to statically code?

Thanks,

-Jeff
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Error running selectiontree control

[David Bartmess]

I'm using a modified featuretree.wxs and keep getting this error. But I can't 
seem to locate what's causing it. If I comment out the Tree control, it 
continues without an error, although the names of the text controls are shown 
instead of the text..

Can anyone tell me what's causing this error?

MSI (c) (8C:A0) [11:31:07:183]: Note: 1: 2235 2:  3: RuntimeLevel 4: SELECT 
`Feature`, `Feature`.`Directory_`, `Title`, `Description`, `Display`, 
`RuntimeLevel`, `Select`, `Action`, `Installed`, `Handle` FROM `Feature` WHERE 
`Feature_Parent`=? ORDER BY `Display`
DEBUG: Error 2235:  Database: . Column 'RuntimeLevel' not present or ambiguous 
in SQL query: SELECT `Feature`, `Feature`.`Directory_`, `Title`, `Description`, 
`Display`, `RuntimeLevel`, `Select`, `Action`, `Installed`, `Handle` FROM 
`Feature` WHERE `Feature_Parent`=? ORDER BY `Display`
DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
The installer has encountered an unexpected error installing this package. This 
may indicate a problem with this package. The error code is 2835. The arguments 
are: ErrorIcon, ErrorDialog,
The installer has encountered an unexpected error installing this package. This 
may indicate a problem with this package. The error code is 2235. The arguments 
are: , RuntimeLevel, SELECT `Feature`, `Feature`.`Directory_`, `Title`, 
`Description`, `Display`, `RuntimeLevel`, `Select`, `Action`, `Installed`, 
`Handle` FROM `Feature` WHERE `Feature_Parent`=? ORDER BY `Display`
MSI (c) (8C:A0) [11:31:08:542]: Product: MaestroLink Client 1.0.0.2 -- The 
installer has encountered an unexpected error installing this package. This may 
indicate a problem with this package. The error code is 2235. The arguments 
are: , RuntimeLevel, SELECT `Feature`, `Feature`.`Directory_`, `Title`, 
`Description`, `Display`, `RuntimeLevel`, `Select`, `Action`, `Installed`, 
`Handle` FROM `Feature` WHERE `Feature_Parent`=? ORDER BY `Display`











1

Installed

Installed





1







1







1



































Installed







Installed





ENTITLED = "1"

ENTITLED = "0"







1









David Bartmess
Wall Street On Demand
david.bartm...@wallst.com
direct: 303.417. x585
cell: 303.883-9117
fax: 303.444.2586

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uninstall Assembly from GAC when Wix MSI Uninstalled

[Wilson, Phil]

Assuming there are no sharing issues keeping it installed, the typical reason 
for this is that the actual assembly name details do not match the description 
that ends up in the MsiAssemblyName table in the MSI file. This means that the 
identity must be fully specified with name, publickeytoken, processor 
architecture, version, culture. I thought something in WiX added all this to 
the MsiAssemblyName table. 

Phil Wilson 

-Original Message-
From: nickheppleston [mailto:n...@modhul.com] 
Sent: Wednesday, May 13, 2009 8:05 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Uninstall Assembly from GAC when Wix MSI Uninstalled


My WiX project installs a .Net 2.0 assembly into the GAC on install, however
when I uninstall, the assembly remains in the GAC. Anyone have any pointers
to how I go about removing the assembly from the GAC on uninstall? Is there
an option similar to the RegistryKey 'createAndRemoveOnUninstall' action?

I am using the following WiX entry to add the assembly to the GAC:





Rgds, Nick.

-- 
View this message in context: 
http://n2.nabble.com/Uninstall-Assembly-from-GAC-when-Wix-MSI-Uninstalled-tp2884391p2884391.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing fonts

[Phil Sayers]

Have you seen the "RegisterFonts" element?


-Original Message-
From: Kim Gybels [mailto:kim.gyb...@metris.com] 
Sent: Wednesday, May 13, 2009 12:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing fonts

Hi,

What is the correct way to install fonts using Wix?
I always get the "is a Font and must be installed to the
FontsFolder"-warnings.

Best regards,
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.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Installing fonts

[Kim Gybels]

Hi,

What is the correct way to install fonts using Wix?
I always get the "is a Font and must be installed to the
FontsFolder"-warnings.

Best regards,
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.

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization file

[MacDiarmid, James D]

Thanks :)   I'm actually very new to VS 2008 and I just discovered that
I can add my localization file to my project solution.  I'm not sure if
that is the right way to do it, but it seems to work nicely. 

-Original Message-
From: Eric St.John [mailto:eric.st.j...@hotmail.com] 
Sent: Wednesday, May 13, 2009 12:15 PM
To: wix-users
Subject: Re: [WiX-users] Localization file


I assumed you were using a WXL file because you mentioned "that my
project isn't loading my localization file."
A localization file (WXL) is required if you use loc variables in your
setup source: IE !(loc.xx).
A localization file is also required if you use an extension (like
WixUIExtension) that uses loc variables and are building a language that
is not included with the extension.  en-US is included with
WixUIExtension.
-Eric
> Date: Wed, 13 May 2009 11:55:54 -0400
> From: james.macdiar...@eds.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Localization file
> 
> 
> Do I have to have a localization file if this is only going to do 
> en-US and inhouse?  When I do a search for localization I'm not seeing

> information on how to include the wxl file.
> 
> 
> 
> -Original Message-
> From: Eric St.John [mailto:eric.st.j...@hotmail.com]
> Sent: Tuesday, May 12, 2009 8:44 PM
> To: wix-users
> Subject: Re: [WiX-users] Localization file
> 
> 
> Have you set wixlocalizati...@culture to en-US for the localization 
> files you expect to be used when specifying Cultures=en-US?
> 
>  
> 
> -Eric
> 
>  
>> Date: Tue, 12 May 2009 18:44:46 -0400
>> From: james.macdiar...@eds.com
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] Localization file
>> 
>> 
>> I've got the en-US parameter set in the cultures box in votive. Is 
>> there something else I'm missing? I'm getting a lot of errors now 
>> that
> 
>> seem to indicate that my project isn't loading my localization file.
>> 
>> Jim
>> -
>> -
>>  The NEW KODAK i700 Series Scanners deliver under ANY 
>> circumstances! Your production scanning environment may not be a 
>> perfect world - but thanks to Kodak, there's a perfect scanner to get

>> the job done! With the NEW KODAK i700 Series Scanner you'll get full 
>> speed at 300 dpi even with all image processing features enabled.
>> http://p.sf.net/sfu/kodak-com
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> _
> Windows Live(tm): Keep your life in sync.
> http://windowslive.com/explore?ocid=TXT_TAGLM_BR_life_in_synch_052009
> --
> --
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! 
> Your production scanning environment may not be a perfect world - but 
> thanks to Kodak, there's a perfect scanner to get the job done! With 
> the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi 
> even with all image processing features enabled. 
> http://p.sf.net/sfu/kodak-com 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
>  The NEW KODAK i700 Series Scanners deliver under ANY 
> circumstances! Your production scanning environment may not be a 
> perfect world - but thanks to Kodak, there's a perfect scanner to get 
> the job done! With the NEW KODAK i700 Series Scanner you'll get full 
> speed at 300 dpi even with all image processing features enabled. 
> http://p.sf.net/sfu/kodak-com 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

_
Hotmail(r) has a new way to see what's up with your friends.
http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tu
torial_WhatsNew1_052009

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to Kodak, there's a perfect scanner to get the job done! With the NEW
KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all
image processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may

Re: [WiX-users] Localization file

[Eric St . John]

I assumed you were using a WXL file because you mentioned "that my project 
isn't loading my localization file."
A localization file (WXL) is required if you use loc variables in your setup 
source: IE !(loc.xx).
A localization file is also required if you use an extension (like 
WixUIExtension) that uses loc variables and are building a language that is not 
included with the extension.  en-US is included with WixUIExtension.
-Eric
> Date: Wed, 13 May 2009 11:55:54 -0400
> From: james.macdiar...@eds.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Localization file
> 
> 
> Do I have to have a localization file if this is only going to do en-US
> and inhouse?  When I do a search for localization I'm not seeing
> information on how to include the wxl file. 
> 
> 
> 
> -Original Message-
> From: Eric St.John [mailto:eric.st.j...@hotmail.com] 
> Sent: Tuesday, May 12, 2009 8:44 PM
> To: wix-users
> Subject: Re: [WiX-users] Localization file
> 
> 
> Have you set wixlocalizati...@culture to en-US for the localization
> files you expect to be used when specifying Cultures=en-US?
> 
>  
> 
> -Eric
> 
>  
>> Date: Tue, 12 May 2009 18:44:46 -0400
>> From: james.macdiar...@eds.com
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] Localization file
>> 
>> 
>> I've got the en-US parameter set in the cultures box in votive. Is 
>> there something else I'm missing? I'm getting a lot of errors now that
> 
>> seem to indicate that my project isn't loading my localization file.
>> 
>> Jim
>> --
>>  The NEW KODAK i700 Series Scanners deliver under ANY 
>> circumstances! Your production scanning environment may not be a 
>> perfect world - but thanks to Kodak, there's a perfect scanner to get 
>> the job done! With the NEW KODAK i700 Series Scanner you'll get full 
>> speed at 300 dpi even with all image processing features enabled. 
>> http://p.sf.net/sfu/kodak-com 
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> _
> Windows Live(tm): Keep your life in sync.
> http://windowslive.com/explore?ocid=TXT_TAGLM_BR_life_in_synch_052009
> 
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks
> to Kodak, there's a perfect scanner to get the job done! With the NEW
> KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all
> image processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

_
Hotmail® has a new way to see what's up with your friends.
http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat'ing TypeLib difficulties and difference between wix versions

[Brian Rogers]

Hey Jesper,

Can you file a bug for this? Tomorrow is the last night to fix bugs on
heat.exe. Please give me the full  element or better yet the
.tlb itself so I can duplicate.

Thanks,

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


On Wed, May 13, 2009 at 8:22 AM, Neil Sleightholm wrote:

> I don't think this is the problem, try navigating to the keys in the
> registry to confirm what I am saying. Having said that there is some
> redirection on 64 bit OSs, which OS are you seeing this in.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com 
>
>
> 
>
> From: jballe [mailto:j...@visionpeople.dk]
> Sent: Wed 13/05/2009 14:30
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Heat'ing TypeLib difficulties and difference
> between wix versions
>
>
>
>
> Well you are probably right that it *should* be the same.
> However when the other system (MS Dynamics NAV) tries to use the COM
> component it can find a non-usable component without any name, when the
> registries are written to HKCR and the things are working when the
> registries are written to HKLM.
>
>
>
> Neil Sleightholm wrote:
> >
> > HKLM\Software\Classes is the same as HKCR.
> >
> > Neil
> >
> > Neil Sleightholm
> > X2 Systems Limited
> >
>
>
> --
> View this message in context:
> http://n2.nabble.com/Heat%27ing-TypeLib-difficulties-and-difference-between-wix-versions-tp2880427p2883748.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
> i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
> i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization file

[Eric St . John]

Open up your WXL file and look for the line like this:http://schemas.microsoft.com/wix/2006/localization"; 
Codepage="1252">
Replace "foo" with "en-US".
> Date: Wed, 13 May 2009 10:23:02 -0400
> From: james.macdiar...@eds.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Localization file
> 
> 
> I don't know where to do that. 
> 
> -Original Message-
> From: Eric St.John [mailto:eric.st.j...@hotmail.com] 
> Sent: Tuesday, May 12, 2009 8:44 PM
> To: wix-users
> Subject: Re: [WiX-users] Localization file
> 
> 
> Have you set wixlocalizati...@culture to en-US for the localization
> files you expect to be used when specifying Cultures=en-US?
> 
>  
> 
> -Eric
> 
>  
>> Date: Tue, 12 May 2009 18:44:46 -0400
>> From: james.macdiar...@eds.com
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] Localization file
>> 
>> 
>> I've got the en-US parameter set in the cultures box in votive. Is 
>> there something else I'm missing? I'm getting a lot of errors now that
> 
>> seem to indicate that my project isn't loading my localization file.
>> 
>> Jim
>> --
>>  The NEW KODAK i700 Series Scanners deliver under ANY 
>> circumstances! Your production scanning environment may not be a 
>> perfect world - but thanks to Kodak, there's a perfect scanner to get 
>> the job done! With the NEW KODAK i700 Series Scanner you'll get full 
>> speed at 300 dpi even with all image processing features enabled. 
>> http://p.sf.net/sfu/kodak-com 
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> _
> Windows Live(tm): Keep your life in sync.
> http://windowslive.com/explore?ocid=TXT_TAGLM_BR_life_in_synch_052009
> 
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks
> to Kodak, there's a perfect scanner to get the job done! With the NEW
> KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all
> image processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

_
Hotmail® goes with you. 
http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

[Brian Rogers]

Hey Roy,

Thanks for the positive feedback and metric data!

I am curious, does your installation package, once installed, work
correctly?

Thanks,

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


On Wed, May 13, 2009 at 8:30 AM, Roy Abou Assaly wrote:

>
> Great Work Brian!!
>
> I just incorporated WiX 3.0.5308 into our build and harvested all 128 VB6
> COM DLLs.  Your fix works like a charm:
>
> [exec] heat.exe : warning HEAT5156 : Ignoring the registry key
> 'Interface\{F3DB7AC0-A581-48C6-A973-8860578A77E1}\ProxyStubClsid/', it has
> already been added to the component 'EstimationEngine.dll'. The registry
> key
> value '{00020424---C000-0046}' will not be harvested.
>
> Also, here are some statistics for Heat when I harvested my 128 files:
>
> Version 3.0.4923:  WiX file produced is 25540 lines, 4.7 MB
> Version 3.0.5308:  WiX file produced is 3794 lines, 601 KB
>
> That's a great performance improvement!
>
> Thanks again for all the help.  Heat is definitely a rock solid tool.
>
> Roy
>
>
>
> Roy Abou Assaly wrote:
> >
>  > I have filed the following bug:
> >
> https://sourceforge.net/tracker/?func=detail&atid=642714&aid=2783049&group_id=105970
> > and included test cases and the binary where you can reproduce how light
> > is broken on the COM VB6 WiX output from Heat from version 3.0.4923 to
> > 3.0.5224.
> >
> > Please let me know if I can be of any help at all.
> >
> >
> > Roy Abou Assaly wrote:
> >>
> >> Sorry.  I'll explain the situation.  I sort of cried "wolf" in the
> >> beginning since I used an XSLT to massage my XML after Heat produced the
> >> XML.  At that point Candle wouldn't compile.  That was my mistake as
> >> confirmed by Brian and yourself.  I fixed that error.  When it came to
> >> running Light to produce my merge module, these were my findings:
> >>
> >> In 3.0.4923 (my current build setup)
> >>
> >> 1. Run Heat : OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
> >> PrismShell.wxs)
> >> 2. Run Candle: ERROR:
> >> [exec] D:\Builds\PRISM XP\Build
> >> 11.51.\Bin\PrismShell.wxs(180) : error CNDL0010 : The Class/@Server
> >> attribute was not found; it is required.
> >>
> >> Fixed by running a custom XSLT that added the Class/@Server attribute.
> >>
> >> 3. Run Light:  OK (PrismShell.msm produced and later incorporated into
> an
> >> MSI).
> >>
> >> In 3.0.5217 and in 3.0.5224 (I'm trying to upgrade to the latest version
> >> of WiX)
> >>
> >> 1. Run Heat: OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
> >> PrismShell.wxs)
> >> 2. Run Candle: OK
> >> 3. Run Light:  Error:
> >>
> >>  [exec] Microsoft (R) Windows Installer Xml Linker version
> 3.0.5217.0
> >>  [exec] Copyright (C) Microsoft Corporation. All rights reserved.
> >>  [exec]
> >>  [exec] Updating file information.
> >>  [exec] Creating cabinet files.
> >>  [exec] Creating cabinet
> >> 'C:\Users\assalr\AppData\Local\Temp\fkjhmoud\#MergeModule.CABinet'.
> >>  [exec] Generating database.
> >>  [exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(19) :
> >> error LGHT0130 : The primary key
> >>
> 'reg0387C011F3F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918'
> >> is duplicated in table 'Registry'.  Please remove one of the entries or
> >> rename a part of the primary key to avoid the collision.
> >>
> >> The WiX XML that is generating the above error looks like the same that
> >> you had generated before:
> >>
> >>  >> Guid="{821C19F9-E65C-48D5-BF11-07F593D7839B}">
> >>   >> Source="SourceDir\DisplayFridayListUI.dll">
> >>   >> Description="DisplayFridayListUI" HelpDirectory="PRISMMsi" Language="0"
> >> MajorVersion="1" MinorVersion="0">
> >>   >> Context="InprocServer32"
> >> Description="DisplayFridayListUI.CDisplayFridayList"
> >> ThreadingModel="apartment" Version="1.0" Programmable="yes">
> >>   Id="DisplayFridayListUI.CDisplayFridayList"
> >> Description="DisplayFridayListUI.CDisplayFridayList" />
> >>  
> >>   Id="{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}"
> >> Name="CDisplayFridayList"
> >> ProxyStubClassId="{00020424---C000-0046}"
> >> ProxyStubClassId32="{00020424---C000-0046}" />
> >>  
> >>  
> >>   >> Key="CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
> >> Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502}" Value=""
> Type="string"
> >> Action="write" />
> >>   >> Key="Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid"
> >> Value="{00020424---C000-0046}" Type="string"
> >> Action="write" />
> >>   >> Key="Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32"
> >> Value="{00020424---C000-0046}" Type="string"
> >> Action="write" />
> >>   >> Key="Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}"
> >> Value="_CDisplayFridayList" Type="string" Action="write" />
> >

Re: [WiX-users] Heat and Directory Harvesting - Design Rationale

[Eric St . John]

You need a component to have an individually serviceable element because the 
decision MSI makes on whether or not to update/repair a file is based on a 
component's keypath.  If you have more than one file in a component and you 
want to patch the file that is not the keypath you will be forced to include an 
update to the keypath file.  If you have more than one file in a component and 
the file that is not the keypath needs repairing (user deleted, corrupted, etc) 
there is no way to do it.  
In addition, if you ever want to ship the file in a separate installer you must 
ship the component in its entirety; not doing so breaks component reference 
counting.  If, for instance, you took a file out of a component that wasn't the 
keypath, shipped it in another product (using a different GUID since the 
keypath changed), uninstalling the new product would remove the file, leaving 
the original product broken.
See Organizing Applications into 
Components:http://msdn.microsoft.com/en-us/library/aa370561(VS.85).aspxand 
Defining Installer Components: 
http://msdn.microsoft.com/en-us/library/aa368269(VS.85).aspx
-Eric
> From: ree...@duckcreektech.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 13 May 2009 08:06:22 -0500
> Subject: [WiX-users]  Heat and Directory Harvesting - Design Rationale
> 
> Hi everyone,
> 
> I have noticed that heat will harvest a folder and all subfolders and put the 
> files in individual components.  While following the tutorials, I had learned 
> that generally you put all files that reside in the same folder into a 
> component together, as long as they're your "atomic unit of setup".  Is there 
> an advantage to having a 1-1 relationship between my .dll files and 
> components, as opposed to having several .dll files in the same folder be 
> represented as one component?
> 
> The assumption here is that heat does it this way for a reason, and I'm 
> trying to learn what that is.  I'm open to other lessons learned on this 
> topic as well.
> 
> Thanks,
> -Jeff
> 
> --
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

_
Hotmail® has ever-growing storage! Don’t worry about storage limits.
http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage1_052009
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization file

[MacDiarmid, James D]

Do I have to have a localization file if this is only going to do en-US
and inhouse?  When I do a search for localization I'm not seeing
information on how to include the wxl file. 



-Original Message-
From: Eric St.John [mailto:eric.st.j...@hotmail.com] 
Sent: Tuesday, May 12, 2009 8:44 PM
To: wix-users
Subject: Re: [WiX-users] Localization file


Have you set wixlocalizati...@culture to en-US for the localization
files you expect to be used when specifying Cultures=en-US?

 

-Eric

 
> Date: Tue, 12 May 2009 18:44:46 -0400
> From: james.macdiar...@eds.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Localization file
> 
> 
> I've got the en-US parameter set in the cultures box in votive. Is 
> there something else I'm missing? I'm getting a lot of errors now that

> seem to indicate that my project isn't loading my localization file.
> 
> Jim
> --
>  The NEW KODAK i700 Series Scanners deliver under ANY 
> circumstances! Your production scanning environment may not be a 
> perfect world - but thanks to Kodak, there's a perfect scanner to get 
> the job done! With the NEW KODAK i700 Series Scanner you'll get full 
> speed at 300 dpi even with all image processing features enabled. 
> http://p.sf.net/sfu/kodak-com 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

_
Windows Live(tm): Keep your life in sync.
http://windowslive.com/explore?ocid=TXT_TAGLM_BR_life_in_synch_052009

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to Kodak, there's a perfect scanner to get the job done! With the NEW
KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all
image processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Cross-Feature dependencies

[Chris Ridd]

Hi,

I've been working on properly supporting feature selection (Custom  
installs) in our packages. So far so good, except I've got a slight  
conceptual problem.

I install into 2 different directories, both of which are user- 
configurable. So my WXS looks kind of like:

Directory "INSTALLDIR" [...]
   Components n + m
Directory "DATADIR" [...]
   Components x + y
Feature Id="Software" ConfigurableDirectory="INSTALLDIR" [...]
   Feature Id="A"
 ComponentRefs n
   Feature Id="B"
 ComponentRefs m
Feature Id="Data" ConfigurableDirectory="DATADIR" [...]
   Feature Id="Adata"
 ComponentRefs x
   Feature Id="Bdata"
 ComponentRefs y

(and so on). Apologies if I've got the XML attribute names wrong, I'm  
at home and this is from memory.

Now feature "A" requires components installed in DATADIR, say "x". Can  
I just include those ComponentRefs under Feature "A", even though they  
refer to things installed under a different Directory? Or will that  
stop the "x" components from being installed in the user-specified  
DATADIR?

Cheers,

Chris

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

[Roy Abou Assaly]

Great Work Brian!!

I just incorporated WiX 3.0.5308 into our build and harvested all 128 VB6
COM DLLs.  Your fix works like a charm:

 [exec] heat.exe : warning HEAT5156 : Ignoring the registry key
'Interface\{F3DB7AC0-A581-48C6-A973-8860578A77E1}\ProxyStubClsid/', it has
already been added to the component 'EstimationEngine.dll'. The registry key
value '{00020424---C000-0046}' will not be harvested.

Also, here are some statistics for Heat when I harvested my 128 files:

Version 3.0.4923:  WiX file produced is 25540 lines, 4.7 MB
Version 3.0.5308:  WiX file produced is 3794 lines, 601 KB

That's a great performance improvement!  

Thanks again for all the help.  Heat is definitely a rock solid tool.

Roy 



Roy Abou Assaly wrote:
> 
> I have filed the following bug: 
> https://sourceforge.net/tracker/?func=detail&atid=642714&aid=2783049&group_id=105970
> and included test cases and the binary where you can reproduce how light
> is broken on the COM VB6 WiX output from Heat from version 3.0.4923 to
> 3.0.5224.
> 
> Please let me know if I can be of any help at all.
> 
> 
> Roy Abou Assaly wrote:
>> 
>> Sorry.  I'll explain the situation.  I sort of cried "wolf" in the
>> beginning since I used an XSLT to massage my XML after Heat produced the
>> XML.  At that point Candle wouldn't compile.  That was my mistake as
>> confirmed by Brian and yourself.  I fixed that error.  When it came to
>> running Light to produce my merge module, these were my findings:
>> 
>> In 3.0.4923 (my current build setup)
>> 
>> 1. Run Heat : OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
>> PrismShell.wxs)
>> 2. Run Candle: ERROR:  
>> [exec] D:\Builds\PRISM XP\Build
>> 11.51.\Bin\PrismShell.wxs(180) : error CNDL0010 : The Class/@Server
>> attribute was not found; it is required.
>> 
>> Fixed by running a custom XSLT that added the Class/@Server attribute.
>> 
>> 3. Run Light:  OK (PrismShell.msm produced and later incorporated into an
>> MSI).
>> 
>> In 3.0.5217 and in 3.0.5224 (I'm trying to upgrade to the latest version
>> of WiX)
>> 
>> 1. Run Heat: OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
>> PrismShell.wxs)
>> 2. Run Candle: OK
>> 3. Run Light:  Error:
>> 
>>  [exec] Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
>>  [exec] Copyright (C) Microsoft Corporation. All rights reserved.
>>  [exec]
>>  [exec] Updating file information.
>>  [exec] Creating cabinet files.
>>  [exec] Creating cabinet
>> 'C:\Users\assalr\AppData\Local\Temp\fkjhmoud\#MergeModule.CABinet'.
>>  [exec] Generating database.
>>  [exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(19) :
>> error LGHT0130 : The primary key
>> 'reg0387C011F3F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918'
>> is duplicated in table 'Registry'.  Please remove one of the entries or
>> rename a part of the primary key to avoid the collision.
>> 
>> The WiX XML that is generating the above error looks like the same that
>> you had generated before:
>> 
>> > Guid="{821C19F9-E65C-48D5-BF11-07F593D7839B}">
>>  > Source="SourceDir\DisplayFridayListUI.dll">
>>  > Description="DisplayFridayListUI" HelpDirectory="PRISMMsi" Language="0"
>> MajorVersion="1" MinorVersion="0">
>>  > Context="InprocServer32"
>> Description="DisplayFridayListUI.CDisplayFridayList"
>> ThreadingModel="apartment" Version="1.0" Programmable="yes">
>>  > Id="DisplayFridayListUI.CDisplayFridayList"
>> Description="DisplayFridayListUI.CDisplayFridayList" />
>>  
>>  > Name="CDisplayFridayList"
>> ProxyStubClassId="{00020424---C000-0046}"
>> ProxyStubClassId32="{00020424---C000-0046}" />
>>  
>>  
>>  > Key="CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
>> Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502}" Value="" Type="string"
>> Action="write" />
>>  > Key="Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid"
>> Value="{00020424---C000-0046}" Type="string"
>> Action="write" />
>>  > Key="Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32"
>> Value="{00020424---C000-0046}" Type="string"
>> Action="write" />
>>  > Key="Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}"
>> Value="_CDisplayFridayList" Type="string" Action="write" />
>> 
>> 
>> Yes, it compiles, but it's not "linking" with Light.
>> 
>> This is where I am right now.  Please note that the XML that Heat
>> produces in 3.0.4923 is much, much bigger than in 3.0.5217 and 3.0.5224. 
>> Let me know if you need me to send you a binary (DisplayFridayListUI.dll)
>> that can reproduce this.
>> 
>> If I can't resolve this issue, I'm afraid I will have to stick with
>> 3.0.4923 as 3.0.5224 has a break that I can't work around.
>> 
>> If anything is unclear, let me know.  Thanks again,
>> 
>> Roy
>> 
>> 
>> Neil Sleightholm w

Re: [WiX-users] Heat'ing TypeLib difficulties and difference between wix versions

[Neil Sleightholm]

I don't think this is the problem, try navigating to the keys in the registry 
to confirm what I am saying. Having said that there is some redirection on 64 
bit OSs, which OS are you seeing this in.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  
 



From: jballe [mailto:j...@visionpeople.dk]
Sent: Wed 13/05/2009 14:30
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat'ing TypeLib difficulties and difference between 
wix versions




Well you are probably right that it *should* be the same.
However when the other system (MS Dynamics NAV) tries to use the COM
component it can find a non-usable component without any name, when the
registries are written to HKCR and the things are working when the
registries are written to HKLM.



Neil Sleightholm wrote:
>
> HKLM\Software\Classes is the same as HKCR.
>
> Neil
>  
> Neil Sleightholm
> X2 Systems Limited
>


--
View this message in context: 
http://n2.nabble.com/Heat%27ing-TypeLib-difficulties-and-difference-between-wix-versions-tp2880427p2883748.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Uninstall Assembly from GAC when Wix MSI Uninstalled

[nickheppleston]

My WiX project installs a .Net 2.0 assembly into the GAC on install, however
when I uninstall, the assembly remains in the GAC. Anyone have any pointers
to how I go about removing the assembly from the GAC on uninstall? Is there
an option similar to the RegistryKey 'createAndRemoveOnUninstall' action?

I am using the following WiX entry to add the assembly to the GAC:





Rgds, Nick.

-- 
View this message in context: 
http://n2.nabble.com/Uninstall-Assembly-from-GAC-when-Wix-MSI-Uninstalled-tp2884391p2884391.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Preserve registry settings on upgrade

[Alex Ivanoff]

Is it possible to preserver registry settings on major upgrade and only
delete it on uninstall?



--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Localization file

[MacDiarmid, James D]

I don't know where to do that. 

-Original Message-
From: Eric St.John [mailto:eric.st.j...@hotmail.com] 
Sent: Tuesday, May 12, 2009 8:44 PM
To: wix-users
Subject: Re: [WiX-users] Localization file


Have you set wixlocalizati...@culture to en-US for the localization
files you expect to be used when specifying Cultures=en-US?

 

-Eric

 
> Date: Tue, 12 May 2009 18:44:46 -0400
> From: james.macdiar...@eds.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Localization file
> 
> 
> I've got the en-US parameter set in the cultures box in votive. Is 
> there something else I'm missing? I'm getting a lot of errors now that

> seem to indicate that my project isn't loading my localization file.
> 
> Jim
> --
>  The NEW KODAK i700 Series Scanners deliver under ANY 
> circumstances! Your production scanning environment may not be a 
> perfect world - but thanks to Kodak, there's a perfect scanner to get 
> the job done! With the NEW KODAK i700 Series Scanner you'll get full 
> speed at 300 dpi even with all image processing features enabled. 
> http://p.sf.net/sfu/kodak-com 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

_
Windows Live(tm): Keep your life in sync.
http://windowslive.com/explore?ocid=TXT_TAGLM_BR_life_in_synch_052009

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to Kodak, there's a perfect scanner to get the job done! With the NEW
KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all
image processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat'ing TypeLib difficulties and difference between wix versions

[jballe]

Well you are probably right that it *should* be the same.
However when the other system (MS Dynamics NAV) tries to use the COM
component it can find a non-usable component without any name, when the
registries are written to HKCR and the things are working when the
registries are written to HKLM.



Neil Sleightholm wrote:
> 
> HKLM\Software\Classes is the same as HKCR.
> 
> Neil 
>   
> Neil Sleightholm 
> X2 Systems Limited 
> 


-- 
View this message in context: 
http://n2.nabble.com/Heat%27ing-TypeLib-difficulties-and-difference-between-wix-versions-tp2880427p2883748.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat and Directory Harvesting - Design Rationale

[jballe]

Hi

I think the reason is that by using "one file, one component" you should be
able to upgrade a component with a new release upgrading package and leave
the rest non-changed files, so the installation will be a lot faster as
unnecessary deleting, uncompressing og copying files can be avoided. However
I havn't ever tried this in a real environment.


Just a OT-notice. I think you should be aware of not just replying a
message, because the message will get tracked in systems like Nabble as a
reply to the original message :)

Kind regards,
Jesper


Jeff Reed wrote:
> 
> Hi everyone,
> 
> I have noticed that heat will harvest a folder and all subfolders and put
> the files in individual components.  While following the tutorials, I had
> learned that generally you put all files that reside in the same folder
> into a component together, as long as they're your "atomic unit of setup". 
> Is there an advantage to having a 1-1 relationship between my .dll files
> and components, as opposed to having several .dll files in the same folder
> be represented as one component?
> 
> The assumption here is that heat does it this way for a reason, and I'm
> trying to learn what that is.  I'm open to other lessons learned on this
> topic as well.
> 
> Thanks,
> -Jeff
> 

-- 
View this message in context: 
http://n2.nabble.com/Heat%27ing-TypeLib-difficulties-and-difference-between-wix-versions-tp2880427p2883886.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat'ing TypeLib difficulties and difference between wix versions

[Neil Sleightholm]

HKLM\Software\Classes is the same as HKCR.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  
 



From: jballe [mailto:j...@visionpeople.dk]
Sent: Wed 13/05/2009 10:30
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat'ing TypeLib difficulties and difference between wix 
versions




I will harvest a .Net COM dll and typelibrary (tlb) and had this working
earlier when I understood that I had to use the registration values instead
of Class-tags.

However I now recognize that the recent version of heat creates all the
registry values underneath HKCR while using the older build 4805 creates all
the registrations underneath HKLM.

Why this difference, is it a bug or are there any kind of option available
so I can use the other method?
It is a problem for us, because it seems as Dynamics NAV requires the
registration in HKLM to use a COM component. However I really like the new
switches for cg, dr and var so it is a bit annoying to use the old heat :)

using build 4805:










using build 5207, 5217 and 5308












Thank you all.

Best regards,
Jesper
--
View this message in context: 
http://n2.nabble.com/Heat%27ing-TypeLib-difficulties-and-difference-between-wix-versions-tp2880427p2880427.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Heat and Directory Harvesting - Design Rationale

[Jeff Reed]

Hi everyone,

I have noticed that heat will harvest a folder and all subfolders and put the 
files in individual components.  While following the tutorials, I had learned 
that generally you put all files that reside in the same folder into a 
component together, as long as they're your "atomic unit of setup".  Is there 
an advantage to having a 1-1 relationship between my .dll files and components, 
as opposed to having several .dll files in the same folder be represented as 
one component?

The assumption here is that heat does it this way for a reason, and I'm trying 
to learn what that is.  I'm open to other lessons learned on this topic as well.

Thanks,
-Jeff

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to check for installed package in WiX 3.0 ?

[Mathieu Cartoixa]

Wilson, Phil a écrit :
> If the UpgradeCode for Crystal is reliable you could make an Upgrade table 
> entry for it with "only search" for the range of versions you expect - 
> that'll set a property you can use in a type 19 custom action. 

Mmmh... I have to admit I am far from being an expert in Windows 
Installer concepts. Do you have any links, or could you translate this 
in WiX tags that allow to achieve this (especially the "type 19 custom 
action" which is cryptic to me, to say the least) ? Pseudo WiX code 
would be more than enough.

Anyway, as I learned not to rely on anything concerning Crystal Reports, 
I'll probably stick with Eric's method for the time being.

Thanks for your help.

Mathieu Cartoixa


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Heat'ing TypeLib difficulties and difference between wix versions

[jballe]

I will harvest a .Net COM dll and typelibrary (tlb) and had this working
earlier when I understood that I had to use the registration values instead
of Class-tags.

However I now recognize that the recent version of heat creates all the
registry values underneath HKCR while using the older build 4805 creates all
the registrations underneath HKLM.

Why this difference, is it a bug or are there any kind of option available
so I can use the other method?
It is a problem for us, because it seems as Dynamics NAV requires the
registration in HKLM to use a COM component. However I really like the new
switches for cg, dr and var so it is a bit annoying to use the old heat :)

using build 4805:










using build 5207, 5217 and 5308












Thank you all.

Best regards,
Jesper
-- 
View this message in context: 
http://n2.nabble.com/Heat%27ing-TypeLib-difficulties-and-difference-between-wix-versions-tp2880427p2880427.html
Sent from the wix-users mailing list archive at Nabble.com.


--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users