Re: [WiX-users] Future of Votive?

[Justin Rockwood]

Yes, there are plans to add designers to Votive. It's been on my list for a
while, but unfortunately my spare time has been rare the past few months. I
think the first designers will probably be very basic and rudimentary (I'm
thinking of registry and file/directory editors), but eventually more will
come. The challenging part will be to create the architecture for supporting
designer extensions. So, for example, somebody writes a Wix extension to
work with Media Center. They could also write an editor for that same
extension and have it plug into Votive automatically once the extension is
referenced from the wixproj. All sorts of cool ideas, but it'll probably be
a while before they're in at the rate I'm going, unfortunately.

 

Anyway, thanks for your suggestions. It's stuff that's already on my radar,
but it's good to know that other people want it, too.

 

Justin

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jared Ashman
Sent: Friday, June 08, 2007 9:47 PM
To: Christopher Painter
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Future of Votive?

 

Not sure about the Votive information, but if you pass -gg to heat as an
option it will generate guids for you instead of inserting the
"PUT-GUID-HERE" message.

On 6/8/07, Christopher Painter <[EMAIL PROTECTED]> wrote:

I've been playing with Votive and I really like the way it plugs into VS and
uses MSBuild.  My installs are primarily InstallShield based, and they will
remain that way, but I would like to break some of the xcopy type logic out
into seperate merge modules and let developers maintain them. 

 

My developers looked at Votive and basically said that they have no
intention of entering raw xml to maintaing the dir/file trees associated
with these merge modules.

 

Will Votive ever have a Right Click | View Designer feature?   The perfect
tool for me would take the VS features the Votive already has and give a vey
simple drag and drop approach to directory structure creation similar to the
way VDPROJ does it. 

 

The tool would need to automaically generate relative path file links and be
very careful to not let developers do stupid things.  We are trying to
support minor upgrades so features like `deprecate file`  to cause
transitive style puncturing of components would be really good.

 

I tried playing with heat but my developer don't want to have to use the
command line and they want to be able to easily add and remove from the tree
as needed. 

 

Eitherway I have a question about heat I notice that it sets components
to Guid="PUT-GUID-HERE" and uses absolute paths instead of relative paths in
the Source attribute.   When you import a large directory structure, whats
the easiest way to update those?  It seems very annonying to have to go
through hundreds of these to get an WXS file that will properly work. 

 

  _  

Looking for a deal? Find great prices on flights and hotels
  with
Yahoo! FareChase.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take 
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/ 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wix-users

 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Future of Votive?

[Jared Ashman]

Not sure about the Votive information, but if you pass -gg to heat as an
option it will generate guids for you instead of inserting the
"PUT-GUID-HERE" message.

On 6/8/07, Christopher Painter <[EMAIL PROTECTED]> wrote:


I've been playing with Votive and I really like the way it plugs into VS
and uses MSBuild.  My installs are primarily InstallShield based, and they
will remain that way, but I would like to break some of the xcopy type logic
out into seperate merge modules and let developers maintain them.

My developers looked at Votive and basically said that they have no
intention of entering raw xml to maintaing the dir/file trees associated
with these merge modules.

Will Votive ever have a Right Click | View Designer feature?   The perfect
tool for me would take the VS features the Votive already has and give a vey
simple drag and drop approach to directory structure creation similar to the
way VDPROJ does it.

The tool would need to automaically generate relative path file links and
be very careful to not let developers do stupid things.  We are trying to
support minor upgrades so features like `deprecate file`  to cause
transitive style puncturing of components would be really good.

I tried playing with heat but my developer don't want to have to use the
command line and they want to be able to easily add and remove from the tree
as needed.

Eitherway I have a question about heat I notice that it sets
components to Guid="PUT-GUID-HERE" and uses absolute paths instead of
relative paths in the Source attribute.   When you import a large directory
structure, whats the easiest way to update those?  It seems very annonying
to have to go through hundreds of these to get an WXS file that will
properly work.


--
Looking for a deal? Find great prices on flights and 
hotelswith
 Yahoo! FareChase.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Future of Votive?

[Christopher Painter]

I've been playing with Votive and I really like the way it plugs into VS and 
uses MSBuild.  My installs are primarily InstallShield based, and they will 
remain that way, but I would like to break some of the xcopy type logic out 
into seperate merge modules and let developers maintain them.
   
  My developers looked at Votive and basically said that they have no intention 
of entering raw xml to maintaing the dir/file trees associated with these merge 
modules.
   
  Will Votive ever have a Right Click | View Designer feature?   The perfect 
tool for me would take the VS features the Votive already has and give a vey 
simple drag and drop approach to directory structure creation similar to the 
way VDPROJ does it.
   
  The tool would need to automaically generate relative path file links and be 
very careful to not let developers do stupid things.  We are trying to support 
minor upgrades so features like `deprecate file`  to cause transitive style 
puncturing of components would be really good.
   
  I tried playing with heat but my developer don't want to have to use the 
command line and they want to be able to easily add and remove from the tree as 
needed.
   
  Eitherway I have a question about heat I notice that it sets components 
to Guid="PUT-GUID-HERE" and uses absolute paths instead of relative paths in 
the Source attribute.   When you import a large directory structure, whats the 
easiest way to update those?  It seems very annonying to have to go through 
hundreds of these to get an WXS file that will properly work.
   

   
-
Looking for a deal? Find great prices on flights and hotels with Yahoo! 
FareChase.-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Shared files

[Rob Mensching]

Are these files being installed in a shared location?  If so, the Component 
GUIDs need to be the same.  That's what the Component Rules are all about.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roy Riegel
Sent: Friday, June 08, 2007 4:52 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shared files

Hello All,
This has got to be a common problem with a known solution.
We are installing 35 -> 40  files into a \system\bin directory in an XP Windows 
environment with two separate but similar module WIX/MSI installers.

By design, it is possible for the user to install this file list once or twice 
(if BOTH modules are installed) and the SAME *.DLLs are installed both times.
The problem comes of course when the user wishes to uninstall one of the 
modules without removing the files that are still needed/used by the 2nd module.
This situation was easily handled in InstallShield 11.5 with a "share" flag for 
the directory of files to be installed.
The uninstaller would check a reference count for the file and not remove it if 
there was still a non-zero count for the file.
And of course, at the uninstall of the 2nd module, the ref. count now allowed 
the files to (correctly) be removed.

How is this same process accomplished in WIX?

I've looked at the Tutorial and there is a "bit" on shared files but it does 
not seem to be this situation.

If this is a "Read the Manual" situation, please just point to the appropriate 
place; if not, an example would be most appreciated.

Thanks in advance,

Roy @ Scientific Monitoring  [EMAIL PROTECTED]
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Shared files

[Roy Riegel]

Hello All,  

This has got to be a common problem with a known solution.

We are installing 35 -> 40  files into a \system\bin directory in an XP
Windows environment with two separate but similar module WIX/MSI
installers.

 

By design, it is possible for the user to install this file list once or
twice (if BOTH modules are installed) and the SAME *.DLLs are installed
both times.

The problem comes of course when the user wishes to uninstall one of the
modules without removing the files that are still needed/used by the 2nd
module.

This situation was easily handled in InstallShield 11.5 with a "share"
flag for the directory of files to be installed.

The uninstaller would check a reference count for the file and not
remove it if there was still a non-zero count for the file.

And of course, at the uninstall of the 2nd module, the ref. count now
allowed the files to (correctly) be removed.

 

How is this same process accomplished in WIX?

 

I've looked at the Tutorial and there is a "bit" on shared files but it
does not seem to be this situation.

 

If this is a "Read the Manual" situation, please just point to the
appropriate place; if not, an example would be most appreciated.

 

Thanks in advance,

 

Roy @ Scientific Monitoring  [EMAIL PROTECTED]   

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] x64 and x86 both use same data files

[Magus]

My company really wants it to only be 1 installer, is there any dangerous
reasons not to do it that way.

John Vottero wrote:
> 
> It sounds like you're trying to create a single MSI that installs either
> 32 bit or 64 bit executables, is that correct?  If so, you shouldn't,
> you need one MSI for 32 bit and one for 64 bit.  I don't think you want
> to reference ProgramFiles64Folder either.  Use ProgramFilesFolder and
> Windows Installer will put things in the correct directory based upon
> the Component's Win64 setting.
> 
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:wix-users-
>> [EMAIL PROTECTED] On Behalf Of Magus
>> Sent: Wednesday, June 06, 2007 4:51 PM
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] x64 and x86 both use same data files
>> 
>> 
>> The problem:
>> Currently I have a data component that installes to
> ProgramFilesFolder,
>> but
>> on a x64 machine it will install my executable to ProgramFiles64Folder
>> and
>> the data needs to be in relation to it.  On X64 the x86 program files
>> will
>> not install.  Is there a way to accomplish this task.
>> 
>> 
>> ...
>> 
>> 
>> 
> ...
>> 
>> > 
>> 
>> 
>> What I want is on X64 the DataFolder points to
>> \\Program Files\\DataFolder\\
>> instead of
>> \\Program Files (x86)\\DataFolder\\
>> Is there a conditional way to do this or do I need a custom action
> that
>> sets
>> the Data Folder Directory according if the system is x64
>> --
>> View this message in context: http://www.nabble.com/x64-and-x86-both-
>> use-same-data-files-tf3880360.html#a10997038
>> Sent from the wix-users mailing list archive at Nabble.com.
>> 
>> 
>>
> ---
>> --
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/x64-and-x86-both-use-same-data-files-tf3880360.html#a11035156
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Check for 'power user' in Condition

[Mike Dimmick]

You can register COM information in either
HKEY_LOCAL_MACHINE\Software\Classes or in
HKEY_CURRENT_USER\Software\Classes. HKEY_CLASSES_ROOT is a merged view of
those keys. If you specify HKCR in your Registry elements Windows Installer
places them in HKLM for a per-machine install and HKCU for a per-user
install. That applies to Windows 2000 onward.

 

If you use the Class table the keys are placed as above - HKLM per-machine,
HKCU per-user. The 'non-advertised' Class element (with @Advertise='no',
recommended, see Rob Mensching's blog at
http://robmensching.com/blog/archive/2007/03/12/RobMens-Recommendation-Do-no
t-advertise-COM-information-in-MSI.aspx) in WiX does the same thing.

 

If you're relying on self-registration then the code could do anything. You
are strongly advised to avoid self-reg. To avoid problems in your build, you
need your COM GUIDs to be stable. Look into Binary Compatibility in VB6. The
interface GUIDs will change if you change the interface, but otherwise will
be unchanged. The class and type library GUIDs remain the same.

 

The reference for built-in properties is the Windows Installer SDK under
"Property Reference", online at
http://msdn2.microsoft.com/en-us/library/aa370905.aspx. I don't think
there's any built-in property that does what you want. If you really want to
do this you'll need to build a custom action.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cheyne, Mark A
- DNR
Sent: 08 June 2007 22:37
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Check for 'power user' in Condition

 

All - Starting from the Condition element schema documentation at
http://wix.sourceforge.net/manual-wix2/wix_xsd_condition.htm, and also
trying this list's archives, I'm failing to find documentation on what inner
text values are allowed in a Product Condition (e.g. LaunchCondition). 

The excellent tutorial describes the 'Privileged' value, which seems to
check for Administrator status.  Is there a value that indicates 'Power
User' status?

Actually, what I am really trying to check for is the ability to register
VB6 COM DLLs (e.g. edit the registry) which happens in our agency to mean
Power User +. But if there is a direct way to determine it, I'd be happy to
know that instead.

Thanks, Mark 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Check for 'power user' in Condition

[Cheyne, Mark A - DNR]

All - Starting from the Condition element schema documentation at
http://wix.sourceforge.net/manual-wix2/wix_xsd_condition.htm, and also
trying this list's archives, I'm failing to find documentation on what
inner text values are allowed in a Product Condition (e.g.
LaunchCondition). 

The excellent tutorial describes the 'Privileged' value, which seems to
check for Administrator status.  Is there a value that indicates 'Power
User' status?

Actually, what I am really trying to check for is the ability to
register VB6 COM DLLs (e.g. edit the registry) which happens in our
agency to mean Power User +. But if there is a direct way to determine
it, I'd be happy to know that instead.

Thanks, Mark

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error in Installing to GAC

[Mike Dimmick]

Just to note I expect it's failing on Windows 2000 because that operating
system does not support Win32 side-by-side assemblies (which do have an
external manifest file). In both cases the 'manifest' contains a list of all
the files making up the assembly. For example, the Visual C++ 2005 C runtime
assembly consists of the files msvcr80.dll, msvcp80.dll and msvcm80.dll. The
manifest also contains the strong-naming hashes of all the files.

 

If you find you do have to set ApplicationManifest for a .NET assembly (and
I don't think you do - the corresponding column in the MsiAssembly table is
nullable) then set it to the DLL. You would only not do this if you set a
file other than the DLL as being the key path, but again, why would you do
that?

 

This manifest should not be confused with an application manifest which is
either an embedded resource or an external file named
application.exe.manifest. This lists the assemblies that your application
uses (and in Windows Vista, how you want UAC to behave).

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick
Sent: 08 June 2007 22:23
To: 'Julie Campbell'; [EMAIL PROTECTED]; [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error in Installing to GAC

 

I would say that only the DLL file should go in the GAC, the other files
should go elsewhere. AssemblyManifest really only applies to multi-file
assemblies and it should point to the file that contains the assembly's
manifest. For .NET assemblies this is the DLL file, all other files are
typically named .netmodule. Multifile assemblies are really really rare
(especially since the C++ 2005 linker can now actually link multiple modules
into a single file) and I would expect you would never need the
AssemblyManifest attribute. You typically only use .NET modules making up a
multi-file assembly where you want to implement a single logical assembly
using multiple .NET languages.

 

An XML file is never the assembly's manifest for a .NET assembly. That's
probably an XML documentation file if it just happened to be generated in
your build folder.

 

I don't think a separate type library is actually required for marshalling
calls to a .NET COM component. It may be required if you want to write
unmanaged COM clients against the library, for example with VB6. It
shouldn't go in the GAC and I would make it a separate Component of its own.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Julie Campbell
Sent: 08 June 2007 21:47
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error in Installing to GAC

 

I ran across a GAC problem today, did my due Google-ance before bothering
the list, and found an old e-mail chain with the same problem.
Unfortunately, the resolution wasn't posted.  Here is the link to jog your
memory:

 

http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg03509.html

 

My Experience: This works under XP, fails ("cannot write to
KeithleyTSPLib.xml") under Win2K.  That could be a build machine (XP)/test
machine issue, hard to tell.

 

My Wix Snippet:



  



  

  

  



 

If I leave out the KeithleyTSPLib_Manifest file, I get a 1935/0x80131043
error (http://blogs.msdn.com/astebner/archive/2004/08/26/221005.aspx).  

 

If I put in that element, I get a 2350 error, "Error writing tofile:
KeithleyTSPLib.xml.  Verify that you have access to that directory"
(retry/cancel, no luck with retry).

 

KNOWN WORKAROUND:  If I remove all the assembly stuff and just install the
.dll as a plain file then do this manually (or via batch file), it works.
(Well, I am still missing some assembly-esque thing, but I get farther):

 

copy regasm.exe "C:\Program Files\Keithley Instruments\KETSP\bin"

copy sn.exe "C:\Program Files\Keithley Instruments\KETSP\bin"

c:

cd ""\Program Files\Keithley Instruments\KETSP\bin"

regasm KeithleyTSPLib.dll /tlb

gacutil /i KeithleyTSPLib.dll

 

Help?  I am not a GAC expert by any means.  In fact, I can barely spell GAC
.

 

Julie Campbell

[EMAIL PROTECTED]

 



_
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com

_

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error in Installing to GAC

[Mike Dimmick]

I would say that only the DLL file should go in the GAC, the other files
should go elsewhere. AssemblyManifest really only applies to multi-file
assemblies and it should point to the file that contains the assembly's
manifest. For .NET assemblies this is the DLL file, all other files are
typically named .netmodule. Multifile assemblies are really really rare
(especially since the C++ 2005 linker can now actually link multiple modules
into a single file) and I would expect you would never need the
AssemblyManifest attribute. You typically only use .NET modules making up a
multi-file assembly where you want to implement a single logical assembly
using multiple .NET languages.

 

An XML file is never the assembly's manifest for a .NET assembly. That's
probably an XML documentation file if it just happened to be generated in
your build folder.

 

I don't think a separate type library is actually required for marshalling
calls to a .NET COM component. It may be required if you want to write
unmanaged COM clients against the library, for example with VB6. It
shouldn't go in the GAC and I would make it a separate Component of its own.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Julie Campbell
Sent: 08 June 2007 21:47
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error in Installing to GAC

 

I ran across a GAC problem today, did my due Google-ance before bothering
the list, and found an old e-mail chain with the same problem.
Unfortunately, the resolution wasn't posted.  Here is the link to jog your
memory:

 

http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg03509.html

 

My Experience: This works under XP, fails ("cannot write to
KeithleyTSPLib.xml") under Win2K.  That could be a build machine (XP)/test
machine issue, hard to tell.

 

My Wix Snippet:



  



  

  

  



 

If I leave out the KeithleyTSPLib_Manifest file, I get a 1935/0x80131043
error (http://blogs.msdn.com/astebner/archive/2004/08/26/221005.aspx).  

 

If I put in that element, I get a 2350 error, "Error writing tofile:
KeithleyTSPLib.xml.  Verify that you have access to that directory"
(retry/cancel, no luck with retry).

 

KNOWN WORKAROUND:  If I remove all the assembly stuff and just install the
.dll as a plain file then do this manually (or via batch file), it works.
(Well, I am still missing some assembly-esque thing, but I get farther):

 

copy regasm.exe "C:\Program Files\Keithley Instruments\KETSP\bin"

copy sn.exe "C:\Program Files\Keithley Instruments\KETSP\bin"

c:

cd ""\Program Files\Keithley Instruments\KETSP\bin"

regasm KeithleyTSPLib.dll /tlb

gacutil /i KeithleyTSPLib.dll

 

Help?  I am not a GAC expert by any means.  In fact, I can barely spell GAC
.

 

Julie Campbell

[EMAIL PROTECTED]

 



_
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com

_

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Directory in user profile but not in RemoveFile table

[Mike Dimmick]

See Rob Mensching's blog entry "How to create an uninstall shortcut (and
pass all the ICE validation)" for information on how to do this.

 

http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-s
hortcut-and-pass-all-the.aspx

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Hunsaker
Sent: 08 June 2007 21:55
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Directory in user profile but not in RemoveFile table

 


WiX: 3.0.2925

I'm adding a program menu which should be created if it's not there. Other
programs install to this menu so I do not want to delete it at uninstall. My
XML looks like this: 

  

  

   

I'm getting a Light error of: 

error LGHT0204 : ICE64: The directory scmworkbench is in the user profile
but is not listed in the RemoveFile table.

I've tried adding a  element with the  but then I
start receiving other errors. 

Thanks for the assistance. 

Regards, 
Jeff...

-- 
Jeff Hunsaker
[EMAIL PROTECTED]

http://www.TheFreestyleEntrepreneur.com
http://EffectiveThoughts.blogspot.com 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Directory in user profile but not in RemoveFile table

[Jeff Hunsaker]

WiX: 3.0.2925

I'm adding a program menu which should be created if it's not there. Other
programs install to this menu so I do not want to delete it at uninstall. My
XML looks like this:

  
   
 
   
 

I'm getting a Light error of:

error LGHT0204 : ICE64: The directory scmworkbench is in the user profile
but is not listed in the RemoveFile table.

I've tried adding a  element with the  but then I
start receiving other errors.

Thanks for the assistance.

Regards,
Jeff...

--
Jeff Hunsaker
[EMAIL PROTECTED]

http://www.TheFreestyleEntrepreneur.com
http://EffectiveThoughts.blogspot.com
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error in Installing to GAC

[Julie Campbell]

I ran across a GAC problem today, did my due Google-ance before bothering
the list, and found an old e-mail chain with the same problem.
Unfortunately, the resolution wasn't posted.  Here is the link to jog your
memory:

 

http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg03509.html

 

My Experience: This works under XP, fails ("cannot write to
KeithleyTSPLib.xml") under Win2K.  That could be a build machine (XP)/test
machine issue, hard to tell.

 

My Wix Snippet:



  



  

  

  



 

If I leave out the KeithleyTSPLib_Manifest file, I get a 1935/0x80131043
error (http://blogs.msdn.com/astebner/archive/2004/08/26/221005.aspx).  

 

If I put in that element, I get a 2350 error, "Error writing tofile:
KeithleyTSPLib.xml.  Verify that you have access to that directory"
(retry/cancel, no luck with retry).

 

KNOWN WORKAROUND:  If I remove all the assembly stuff and just install the
.dll as a plain file then do this manually (or via batch file), it works.
(Well, I am still missing some assembly-esque thing, but I get farther):

 

copy regasm.exe "C:\Program Files\Keithley Instruments\KETSP\bin"

copy sn.exe "C:\Program Files\Keithley Instruments\KETSP\bin"

c:

cd ""\Program Files\Keithley Instruments\KETSP\bin"

regasm KeithleyTSPLib.dll /tlb

gacutil /i KeithleyTSPLib.dll

 

Help?  I am not a GAC expert by any means.  In fact, I can barely spell GAC
.

 

Julie Campbell

[EMAIL PROTECTED]

 



_
Scanned by IBM Email Security Management Services powered by MessageLabs. For 
more information please visit http://www.ers.ibm.com
_-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

[Wilson, Phil]

If you can locate the cached MSI file in Windows\installer, opening it
with Orca will show the UpgradeCode in the Property table. That might
help see if you're on the right track.  Versions are also another reason
why a major upgrade won't detect an older one. 

Phil Wilson 

 



From: fiordean dacian [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 08, 2007 10:00 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade InstallShield package



Hi Phil,

Looking through IS log I see ALLUSERS with a value of 1.

Running your script displays "Context 4", so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there
is no detection for the product IS created.

A strange thing I saw running your script: the product GUID displayed by
your script next to the product name I'm interested is something like
this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product code displayed by IS within its UI is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think the UpgradeCode on which I base my 
element to detect the previous version installed out there is wrong (I
take it from the same IS UI which displays the "wrong" product code
above). I don't see a property for retrieving the UpgradeCode within the
WindowsInstaller automation interface in order to check if the
UpgradeCode IS installed product has.

Dacian


- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 7:22:22 PM
Subject: Re: [WiX-users] Upgrade InstallShield package


InstallShield has a custom action (ISSetAllUsers) that sets ALLUSERS, so
looking in the raw MSI file won't tell you what's going on. It's mostly
used when it upgrades previous products, but nevertheless I recommend
looking at a log to see what's actually happening to the ALLUSERS value
during the InstallShield MSI install. 
 
This script might help. If it reports a context of 4 if the product is
installed per-machine, 2 if for a user and unmanaged. 
 
Option Explicit
Public installer, fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt,
sid, psorce, pcache, pvers
 
Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("prodex.txt", True)
 
' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on error resume next
For Each prod In installer.ProductsEx("", "", 7)
   pid = prod.ProductCode
   contxt = prod.Context
   sid=prod.usersid
   pname = prod.InstallProperty("InstalledProductName")
   psorce=prod.InstallProperty( "InstallSource")
   ploc =prod.InstallProperty( "InstallLocation")  
   pcache = prod.InstallProperty("LocalPackage") 
  pvers=prod.InstallProperty("VersionString")
   a.writeline (pid & " " & pname & " " & pvers & " installed at <" &
ploc & "> from " & psorce & " Context " & contxt)
Next


Phil Wilson 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Tuesday, June 05, 2007 9:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade InstallShield package



Hi Bob,

ALLUSERS property is not set within the .msi file InstallShield
generates, which means there was a per-user installation (there is
something like ApplicationUsers property with the value ALLUSERS). My
.msi uses ALLUSERS with a value of 1 (so per-machine install). I removed
ALLUSERS property from my .msi.

Also, I switched for a major upgrade now (updated Product & UpgradeCode
GUIDs and Version), here is the Upgrade sequence:








The first Upgrade refers to previous InstallShield package out there,
second is for current version.

Well, I had no success yet.

Dacian




- Original Message 
From: Bob Arnson <[EMAIL PROTECTED]>
To: fiordean dacian <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 5:23:07 PM
Subject: Re: [WiX-users] Upgrade InstallShield package

fiordean dacian wrote: 

That would remove my previous installation, right? I'm not sure
I want that since the user might have configured the product (registry
keys, config files, etc.) and I don't want that to be removed. I just
want an upgrade of what's out there.



Unless you kept all your GUIDs and IDs the same, you need to do a major
upgrade to get to a "clean slate" install.



On top of that, it still doesn't look like the previous
installation was detected (the PREVFOUND property doesn't have a GUID
attached to it and no upgarde is proposed, just normal install).



The most common reason is that you're trying to mix and match values of
ALLUSERS. MSI doesn't support a per-user install upgrading a per-machine
install (or vice versa).

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




Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge

Re: [WiX-users] wix as a wrapper for NSIS

[Ben Greenberg]

You may want to consider writing a bootstrapper that strings together 
your MSI and NSIS packages and installs them sequentially.  You can 
write the bootstrapper in NSIS as well.  Then all you need is a simple 
NSIS uninstall script that calls uninstall on your packages.  This way 
you can avoid all the issues with Custom Actions that you will have by 
shoving everything into an MSI.


bg

Aaron Shurts wrote:
How is that a change to your requirement?  I could tell you how to do 
this, but I don't feel like advocating what I consider to be a 
horrible design.  This should get you the information you need, but I 
guarantee you'll be back on this mailing list in a short period of 
time trying to resolve issues or on a different forum trying to 
resolve deployment problems.


http://msdn2.microsoft.com/en-us/library/aa368012.aspx

Regards,
//aj

On 6/8/07, * carlH* <[EMAIL PROTECTED] 
> wrote:



Slight change to our requirement here as I can see why the other
method would
be unreliable.

1 - Launch the MSI, this launches our NSIS installer which
installs silently
(I've already got this working).  This also installs our NSIS
uninstall exe.
2 - Running the MSI uninstaller should launch our NSIS uninstaller
exe -
this is the bit I'm stuck on

Carl
--
View this message in context:
http://www.nabble.com/wix-as-a-wrapper-for-NSIS-tf3878437.html#a11026568
Sent from the wix-users mailing list archive at Nabble.com
.


-

This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users




-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
  



___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
  


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditionally installing components based on user's locale

[Igor Maslov]

I wrote custom action in a DLL which identifies country (specifically North
America or Europe) and saves result in a WiX property (it uses MSI  API to
store property into the table). Then I use this property in component
conditions



Scott Palmer-3 wrote:
> 
> As part of my setup I would like to write certain registry values
> depending
> on the country setting of the OS.  E.g. for North American users I might
> set
> a registry value to 1, for European users the value would be set to 2.
> 
> Is there an easy way to do this without writing a custom action?
> Failing that, is there a custom action that can be written easily?
> 
> 
> Thanks,
> 
> Scott
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Conditionally-installing-components-based-on-user%27s-locale-tf3875424.html#a11030742
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX 3 and the wixui

[rkm1]

Problem fixed -checking reveals that this was a fossil left in my folder
after 
Wix 2 was replaced by Wix 3. Failure to remove the reference Wixui.wixlib 
in the example command line caused the problem.

-rob




-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-- 
View this message in context: 
http://www.nabble.com/WiX-3-and-the-wixui-tf3890430.html#a11030932
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Problems with Visual Studio Sp Merge Modules

[gboreki]

Hello @All,

I am currently having a weird problem with my setup.

I have a merge module, which is installed successfully if I run the 
vcredist_x86.exe for Visual Studio 2005 SP1. This merge need to install some 
services and run some custom actions.

Now, I tried to add the merge modules for VSSP1 to my setup, and it suddenly 
stopped working. I checked with orca the InstallExecuteSequence, and when i add 
VSSP1 merge modules, some of the lines from my merge are missing. When i remove 
the merge, the sequence is fine.

I have updated my binaries to the last wix v2 release, same results.
Any idea on the subject?

Regards

Guilherme Boreki
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix as a wrapper for NSIS

[Aaron Shurts]

How is that a change to your requirement?  I could tell you how to do this,
but I don't feel like advocating what I consider to be a horrible design.
This should get you the information you need, but I guarantee you'll be back
on this mailing list in a short period of time trying to resolve issues or
on a different forum trying to resolve deployment problems.

http://msdn2.microsoft.com/en-us/library/aa368012.aspx

Regards,
//aj

On 6/8/07, carlH <[EMAIL PROTECTED]> wrote:



Slight change to our requirement here as I can see why the other method
would
be unreliable.

1 - Launch the MSI, this launches our NSIS installer which installs
silently
(I've already got this working).  This also installs our NSIS uninstall
exe.
2 - Running the MSI uninstaller should launch our NSIS uninstaller exe -
this is the bit I'm stuck on

Carl
--
View this message in context:
http://www.nabble.com/wix-as-a-wrapper-for-NSIS-tf3878437.html#a11026568
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

[fiordean dacian]

Hi Phil,

Looking through IS log I see ALLUSERS with a value of 1.

Running your script displays "Context 4", so there is a per-machine install 
done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no 
detection for the product IS created.

A strange thing I saw running your script: the product GUID displayed by your 
script next to the product name I'm interested is something like this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product code displayed by IS within its UI is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think the UpgradeCode on which I base my  element to 
detect the previous version installed out there is wrong (I take it from the 
same IS UI which displays the "wrong" product code above). I don't see a 
property for retrieving the UpgradeCode within the WindowsInstaller automation 
interface in order to check if the UpgradeCode IS installed product has.

Dacian

- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 7:22:22 PM
Subject: Re: [WiX-users] Upgrade InstallShield package



 



InstallShield has a custom action (ISSetAllUsers) that 
sets ALLUSERS, so looking in the raw MSI file won't tell you 
what's going on. It's mostly used when it upgrades previous products, but 
nevertheless I recommend 
looking at a log to see what's actually happening to the ALLUSERS value 
during the InstallShield MSI install. 

 

This script might help. If it reports a 
context of 4 if the product is installed per-machine, 2 if for a user and 
unmanaged. 

 

Option Explicit
Public installer, 
fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt, sid, psorce, pcache, 
pvers

 

Set fso = 
CreateObject("Scripting.FileSystemObject")
Set a = 
fso.CreateTextFile("prodex.txt", True)

 

' Connect to Windows Installer 
object
Set installer = 
CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on 
error resume next
For Each prod In installer.ProductsEx("", "", 
7)
   pid = prod.ProductCode
   contxt = 
prod.Context
   sid=prod.usersid
   pname = 
prod.InstallProperty("InstalledProductName")
   
psorce=prod.InstallProperty( "InstallSource")
   ploc 
=prod.InstallProperty( "InstallLocation")  
   pcache = 
prod.InstallProperty("LocalPackage") 
  
pvers=prod.InstallProperty("VersionString")
   a.writeline (pid 
& " " & pname & " " & pvers & " installed at <" & 
ploc & "> from " & psorce & " Context " & 
contxt)
Next


Phil Wilson 



From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean 
dacian
Sent: Tuesday, June 05, 2007 9:46 AM
To: 
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade 
InstallShield package







Hi 
Bob,

ALLUSERS property is not set within the .msi file InstallShield 
generates, which means there was a per-user installation (there is something 
like ApplicationUsers property with the value ALLUSERS). My .msi uses ALLUSERS 
with a value of 1 (so per-machine install). I removed ALLUSERS property from my 
.msi.

Also, I switched for a major upgrade now (updated Product & 
UpgradeCode GUIDs and Version), here is the Upgrade sequence:










The first Upgrade refers to 
previous InstallShield package out there, second is for current 
version.

Well, I had no success yet.

Dacian




- 
Original Message 
From: Bob Arnson <[EMAIL PROTECTED]>
To: 
fiordean dacian <[EMAIL PROTECTED]>
Cc: 
wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 5:23:07 
PM
Subject: Re: [WiX-users] Upgrade InstallShield package

fiordean 
dacian wrote: 

  
  That 
  would remove my previous installation, right? I'm not sure I want that since 
  the user might have configured the product (registry keys, config files, 
etc.) 
  and I don't want that to be removed. I just want an upgrade of what's out 
  there.



Unless you kept all your GUIDs and IDs 
the same, you need to do a major upgrade to get to a "clean slate" 
install.



  
  On 
  top of that, it still doesn't look like the previous installation was 
detected 
  (the PREVFOUND property doesn't have a GUID attached to it and no upgarde is 
  proposed, just normal install).



The most common 
reason is that you're trying to mix and match values of ALLUSERS. MSI doesn't 
support a per-user install upgrading a per-machine install (or vice versa).
-- 
sig://boB
http://joyofsetup.com/






Sick sense of humor? Visit Yahoo! TV's Comedy 
with an Edge to see what's on, when. 
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users







   
__

Re: [WiX-users] Detectng Windows XP with Service Pack 2.

[Aaron Shurts]

((VersionNT > 501) OR ((VersionNT = 501) AND (ServicePackLevel >= 2))) AND
MsiNTProductType = 1

This will check for all workstation level OSes that are XP SP2 or higher.
If you want to allow servers as well, drop the ' AND MsiNTProductType = 1'
from the condition

Regards,
//aj

On 6/8/07, Richard <[EMAIL PROTECTED]> wrote:



In article <[EMAIL PROTECTED]>,
Sankaranarayanan <[EMAIL PROTECTED]>  writes:

>
> Is there any other property wich will distinguish between the different
Servi
ce Packs.


--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Detectng Windows XP with Service Pack 2.

[Richard]

In article <[EMAIL PROTECTED]>,
Sankaranarayanan <[EMAIL PROTECTED]>  writes:

> 
> Is there any other property wich will distinguish between the different Servi
ce Packs.


-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Detectng Windows XP with Service Pack 2.

[Sankaranarayanan]

Hi,

>From WIX 2 - I would like to detect if the client OS is Windows XP with 
>Service Pack 2.
The "VersionNT" property for all Service Packs is 501.

Is there any other property wich will distinguish between the different Service 
Packs.

Thanks,
Sankaranarayanan MG


  ___ 
Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for
your free account today 
http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Are you really big man?

[Sales]

We are delighted to offer you a great deal!

You have an extremely great chance to improve your sex life and make
yourself twice sexier, because only our clinically tested medicine
can guarantee that YOUR DICK will get TWICE as BIGGER as it used to
be IN only 6 MONHTS!

Check for details: http://www.foleysunlimited.com/ 

And you'll get your money back, if you are not satisfied. 
No bullshit! 

-- 
stotnioirgonosnpnhnhqhouosnlnhnjslnpokntntotoqoolumilkllhplqlimi


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using variable information in WIX tag attributes

[Bob Arnson]

Steve Walch wrote:
> As you can see, I know how to use variable [string] attributes, but I can
> not figure out how convert my user input into variable YesNo attributes,
> Enum attributes, attributes that are references to other tags,  attributes
> that should be omitted in certain cases, and even whole tags that should be
> omitted in certain cases.  Maybe Condition tags are the answer in some
> cases, but I can not quite think it all through.
>   

Usually, those kinds of attributes must be set at build time and can't 
use properties that might change at install time. To do that, you need 
to have multiple components and use conditions or features to make sure 
they're mutually exclusive.

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



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX 3 and the wixui

[Bob Arnson]

Robert McConnell wrote:
> The offending wixui.wixlib version accompanied the Wix 3 download 
> dated 5/25/2007 5:36 AM.
>   

Where did you get this download? Wixui.wixlib isn't part of WiX v3; it's 
been embedded in WixUIExtension.dll for a long time now.

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



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WiX 3 and the wixui

[Robert McConnell]

I too have installed Wix 3 to get around the 8.3 issue.

I've been working through the example SampleWixUI making changes 
where necessary to be compatible with Wix 3. I've now encountered the 
following error:

wixui.wixlib : error LGHT0141 : The library file format version 
2.0.2207.0 is not compatible with the expected library file format 
version 3.0.2002.0.

The offending wixui.wixlib version accompanied the Wix 3 download 
dated 5/25/2007 5:36 AM.

Suggestions for a solution would be appreciated.

Thanks,

-rob


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix as a wrapper for NSIS

[carlH]

Slight change to our requirement here as I can see why the other method would
be unreliable.

1 - Launch the MSI, this launches our NSIS installer which installs silently
(I've already got this working).  This also installs our NSIS uninstall exe.
2 - Running the MSI uninstaller should launch our NSIS uninstaller exe -
this is the bit I'm stuck on

Carl
-- 
View this message in context: 
http://www.nabble.com/wix-as-a-wrapper-for-NSIS-tf3878437.html#a11026568
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Avoiding registry entries being modified with REINSTALL=ALL REINSTALLMODE=vos

[Rob Hamflett]

I think you might have to use a RegistrySearch to get the current values and 
use those as the values 
to write.

Rob

Rennie Petersen wrote:
> No answers. :-(
>  
> Of course, this is not WiX specific, but I'm wondering if someone could 
> help me anyway.
>  
> To elaborate, the situation is that in my MSI I have not written any 
>   
> The  and the same UpgradeCode=guid tag as used when the prior install was done.
>  
> On the msiexec.exe command line I specify REINSTALL=ALL and 
> REINSTALLMODE=vos. I'm not specifying REINSTALLMODE=vomus because I do 
> not want the registry entries to be modified.
>  
> But the registry entries are being modified anyway.
>  
> Any idea of how I can prevent this?
>  
> Thanks.
>  
> Rennie
>  
> 
> 
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of
> *Rennie Petersen
> *Sent:* 6. juni 2007 19:18
> *To:* wix-users@lists.sourceforge.net
> *Subject:* [WiX-users] Avoiding registry entries being modified
> withREINSTALL=ALL REINSTALLMODE=vos
> 
> I'm doing a reinstall, but I don't want the existing registry
> entries to be modified.
> 
> So instead of specifying REINSTALLMODE=vomus I specify
> REINSTALLMODE=vos.
> 
> But the registry entries still get reset to the values in my MSI.
> 
> Is it possible to avoid this?
> 
> Thanks.
> 
> Rennie
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Avoiding registry entries being modified with REINSTALL=ALL REINSTALLMODE=vos

[Rennie Petersen]

No answers. :-(
 
Of course, this is not WiX specific, but I'm wondering if someone could
help me anyway.
 
To elaborate, the situation is that in my MSI I have not written any
mailto:[EMAIL PROTECTED] On Behalf Of Rennie
Petersen
Sent: 6. juni 2007 19:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Avoiding registry entries being modified
withREINSTALL=ALL REINSTALLMODE=vos



I'm doing a reinstall, but I don't want the existing registry
entries to be modified. 

So instead of specifying REINSTALLMODE=vomus I specify
REINSTALLMODE=vos. 

But the registry entries still get reset to the values in my
MSI. 

Is it possible to avoid this? 

Thanks. 

Rennie 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Using variable information in WIX tag attributes

[Steve Walch]

I have built my user interface for prompting users with setup information and
I am having trouble figuring out how to use it all in my WIX tags.  For
example, I prompt for database creation parameters, which might translate to
one of the following, depending on what the user selected:

#1


#2


#3

...



As you can see, I know how to use variable [string] attributes, but I can
not figure out how convert my user input into variable YesNo attributes,
Enum attributes, attributes that are references to other tags,  attributes
that should be omitted in certain cases, and even whole tags that should be
omitted in certain cases.  Maybe Condition tags are the answer in some
cases, but I can not quite think it all through.

Thansk!
-- 
View this message in context: 
http://www.nabble.com/Using-variable-information-in-WIX-tag-attributes-tf346.html#a11023688
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Define constants not working with candle in 3.0.2921.0?

[Rob Mensching]

Send us a patch for changes to the html files in the wix\src\chm\html directory.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Fischer
Sent: Thursday, June 07, 2007 12:56 PM
To: Brian Simoneau; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Define constants not working with candle in 3.0.2921.0?

That worked.

I re-read the documentation and I now see this mentioned, but it's not 
especially clear.  Is there a formal process for updating the documentation?

Thanks,
Kevin

Date: Thu, 7 Jun 2007 15:09:06 -0400
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Define constants not working with candle in 3.0.2921.0?
Your ifdef should look like


-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Fischer
Sent: Thursday, June 07, 2007 2:44 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Define constants not working with candle in 3.0.2921.0?
I have some code like this:








The command line for candle looks like:
candle.exe -dDebug  -out obj\Debug\Base.wixobj -ext 
..\..\..\..\v1_tools\wix\bin\WixUtilExtension.dll Base.wxs

But, I'm seeing $(var.Flavor2) evaluate to "Release".  I would've expected it 
to be Debug based on the -dDebug on the candle command line.

Am I doing something wrong?  Or is there possible a bug in candle?

I've also tried "-dDebug=1", but that didn't help.

Thanks,
Kevin

Change is good. See what's different about Windows Live Hotmail. Check it 
out!


Make every IM count. Download Windows Live Messenger and join the i'm 
Initiative now. It's free.  Make it 
count!
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] IISReset

[Rob Mensching]

When are you doing iisreset?  If you're doing it in the middle of the install 
then it is possible the rollback system is getting confused.

Why are you doing iisreset?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Krishna Kishore
Sent: Thursday, June 07, 2007 2:47 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] IISReset

i created website using WIX, websites are created sucessfully, but once we do 
IISReSet, Websites are deleting fromt the IIS,

Do any one faced the problem


i am using


  


  

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problems with Major Upgrade

[Rob Hamflett]

First of all, did your initial installer have an Upgrade Code specified?  If it 
did then this will 
be fairly straightforward.  To make a Major Upgrade, take your current WiX file 
and:
Change the Product Version
Change the Product Code
Change the Package Code
Leave the Upgrade Code the same

Create an Upgrade table like this:

   
   


Changing YOUR-UPGRADE-GUID and THIS-PRODUCT-VERSION for the appropriate values.

Add RemoveExistingProducts to the InstallExecuteSequence.  There are a few 
places you can add it, 
with differing affects.  See here:
http://msdn2.microsoft.com/en-us/library/aa371197.aspx

The NEWAPPFOUND bit is for stopping downgrade.  If you don't care about this 
you can omit that entry 
in the Upgrade Table and ignore the following.  Otherwise:
Add a custom error like this:

   There is a later version of this product installed


Create a Custom Action like this:


and finally add this to your execute sequences:
NEWAPPFOUND

Hoe that helps,

Rob


Carter Sanders wrote:
> What I'd really like is a pointer to a working example of a Major 
> Upgrade.  The fine tutorial at http://www.tramontana.co.hu/wix/  has a 
> lot of info about patches and minor upgrades, but no explicit working 
> examples of major upgrades. I've been trying for quite some time to get 
> this working.
> 
> What I'm experiencing is this-
> 
> Either I get a double install, or a broken install. If I set OnlyDetect 
> to yes, I get a double install when I try to do an upgrade (two 
> instances of my program in add/remove programs) . If I set OnlyDetect to 
> "no", at the end of my upgrade, the entire installation is deleted and I 
> have a corrupted install.
> 
> 
> Here's my Upgrade table-
> 
>
> 
>   Property="PREVIOUSVERSIONINSTALLED" IncludeMinimum='yes' Minimum='0.0.1'/>
> 
>
> 
> 
> I don't see any suggestion of where the PREVIOUSVERSIONINSTALLED 
> property should be used once it's populated. Do I have to write a custom 
> action, or is there some  mainstream way of using it? I tried adding it 
> as a condition to the  Welcome Maintenance dialog, but that didn't seem 
> to work.
> 
> Thanks for any help.
> 
> 
> 
> -Carter
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] how to do this in wix?

[Rob Hamflett]

You're going to need a Custom Action, but thankfully it's the simple kind which 
can be done in WiX. 
  You want a Property like this:
http://url-prod.com"; />

And a Custom Action like this:
http://url-test.com"; 
/>

Then in your InstallExecuteSequence, and possibly the InstallUISequence if you 
need it in the UI:
SERVERENV = "TEST"

It doesn't have to be after AppSearch; it's a just a good place I thought of 
off the top of my head.

Rob


Paramesh S wrote:
> Hi,
> 
> During MSI install, I want to set values of some property based on other 
> input property value. Something like
> 
>  
> 
> if ("[SERVERENV]" = "TEST")
> 
> http://url-test.com />
> 
> else
> 
> http://url-prod.com />
> 
> Endif
> 
>  
> 
> Can someone tell me how to do this? Can we do this without using custom 
> action?
> 
> Thanks,
> 
> Paramesh
> 
> 
> 
>  
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users