Having read this request probably makes that I qualify for the position
;-)
Now only find out how bad the commute is from Gouda
-Original Message-
From: Nathan Stohlmann [mailto:nathan.stohlm...@gmail.com]
Sent: maandag 25 januari 2010 18:49
To: [Wix Users]
Subject: [WiX-users]
The msvcp71.dll is in my registry as shared dll and looks like it is
refcounted. Magic happens when your uninstall decreases the counter to 0 based
on your rollback. (i do assume your are installing msvcp71.dll). Somehow msi
feels it needs the original installer to properly uninstall it? Not a
In darice.cub there is some vbscript for ICE61:
Function VersionStringToLong(strng)
Dim i, iPos, sAccum, sTemp
On Error Resume Next
sTemp = strng
iPos = InStr(sTemp ., .)
sAccum = H Right(00 Hex(CInt(Left(sTemp, iPos - 1))), 2)
If Err.Number 0 Then VersionStringToLong = 0: Exit
smoke.exe - cub myCub.cub myMSI.msi smoke.log
(use two to redirect output, that will open the file for append, instead of
create)
Van: nagaram.c [mailto:nagara...@symphony.cc]
Verzonden: do 24-12-2009 6:46
Aan: 'General discussion for Windows Installer XML
Rahul,
WIX_TEMP only works for candle, light etc, not for your msi. If you want your
msi to use another location as 'temporary' changing the TempFolder property
might work... (might...)... not sure if the msi internals actual honor that
property.
Rene
Van:
Are you installing on Vista? Does running as admin help? Is this single
component not depending on anything else? You can use dependency walker and/or
ildasm to find out what dependencies you have.
RegistrationHelper.InstallAssembly does Demand/Assert UnmanagedCode permission.
1. use a bootstrapper
2. depends on the bootstrapper
3. dark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of siegfried
Sent: zondag 8 juni 2008 6:01
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to revere compile exe into msi?
How do I
I just verified build 4130 on win xp sp 2, vsts2005 8.0.50727.762 and it
works for me.
Did you also install the ProjectAggregator2.msi?
Van: [EMAIL PROTECTED] namens carlldev
Verzonden: wo 4-6-2008 12:35
Aan: wix-users@lists.sourceforge.net
Onderwerp: Re:
Or use this property
SHORTFILENAMES
and set it to true
(never tried it though)
http://msdn.microsoft.com/en-us/library/aa371851(VS.85).aspx
Van: [EMAIL PROTECTED] namens Simon Dahlbacka
Verzonden: wo 14-5-2008 11:17
Aan: WiX Users
Onderwerp: [WiX-users]
You cannot chain dotnetfx.exe in this way. Use a bootstrapper instead:
http://wix.mindcapers.com/wiki/Bootstrapper
Van: [EMAIL PROTECTED] namens mounir mds
Verzonden: do 8-5-2008 17:51
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] Problem when
I guess msiexec runs the msi as LocalSystem? (just to verify try -U
[sqluser] -P [sqlpwd] instead of -E? or check the sqllog for failed
login attempts )
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sajo Jacob
Sent: vrijdag 15 februari 2008 21:56
To:
I add the wix tools, tasks and scripts to source control to prevent just that
kind of fuzzy-ness
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brendan
Crosser-McGay
Sent: vrijdag 15 februari 2008 22:17
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re:
It looks like you're using Wix 2.0/Votive 2.0. Votive 2.0 does not have
an msbuild compatibale format. Switch to Votive 3.0 and your trick
should work.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fgc
Sent: dinsdag 12 februari 2008 9:34
To:
From a few days ago... thanks to Karim
Michal Peled wrote:
I need to get my installation to register a .NET assembly in the way
that regasm /tlb does.
I saw an example for such a thing in Rob's blog, using the
[EMAIL PROTECTED] attribute (set to yes).
Hi Michal,
You can use heat
If you want to be absolute sure that no breaking changes will occur
between today and the release of your MSI and you can live with the
missing features go for Wix V2 stable.
But if you need features only offered by v3 go for that release because
those features will never make it into v2. I would
Not sure, but If you add this:
Property Id=NetFxVersion Value=v2.0.50727 /
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew V.
Bezmenov
Sent: vrijdag 8 februari 2008 9:35
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Ngen.exe
Hi.
It fails because the Custom action expects the InstallService.cmd to be
an executable (it tries to call CreateProcess )
See http://wix.mindcapers.com/wiki/Category:Custom_Actions
In the section Relevant Examples : Call a CMD Example
-Original Message-
From: [EMAIL PROTECTED]
Use [#OpenVPNTapINF]
see also http://msdn2.microsoft.com/en-us/library/aa368609(VS.85).aspx
Van: [EMAIL PROTECTED] namens Vincent Privat
Verzonden: za 1/26/2008 15:40
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] Reference a BinaryKey in
I'm wondering why Light fails, as probably Candle did run. Just a guess: might
the view-private files be the issue?
If latency is the issue you will experience more problems not just with
light.exe
Van: [EMAIL PROTECTED] namens martin lavelle
Verzonden: vr
I assume you found this technote:
http://www-1.ibm.com/support/docview.wss?ratlid=cctocbodyrs=984uid=swg21222178
Van: [EMAIL PROTECTED] namens martin lavelle
Verzonden: vr 1/25/2008 14:37
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] ClearCase
Maybe elaborate a little bit more on 'working fine in some OS's' (which
do work?) and what the Custom Action is trying to do?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of SaiTeja
Sent: donderdag 24 januari 2008 11:20
To: wix-users@lists.sourceforge.net
There has been a previous thread on this which I copied for your
convenience
Subject: Re: [WiX-users] Make User Run exe when the msi is run
If the issue is that your Launch Condition prevents an uninstall, then
you probably need your LaunchConditions to be
performed only on an install.
Did you try opening it in Notepad? Did you try to output to a different
filename (instead of the same as the input file)?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anidil
Sent: maandag 14 januari 2008 9:58
To: wix-users@lists.sourceforge.net
If you are targeting win2k or above, try this:
Property Id=BROWSER Value=start /
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Srinivas
Tirupati
Sent: Saturday, November 03, 2007 7:28 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
If you're having trouble with the 260 char limit, it is not a wix thing
but a System.IO 'feature'. I reflectored System.IO.File to understand
why it won't accept paths of 32000 chars. The winapi is capable of doing
that by putting \\?\ in front of your path/file. Unfortunately the
managed code
).
From: Peter Wone [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 26, 2007 12:06 AM
To: Schrieken, Rene
Subject: RE: Re: [WiX-users] Issue packaging EntLib Assemblies with WiX
Ss far as I know, there is no way to preserve component GUIDs between
runs of heat. From
Something like this?
Property Id=sc
FileSearch LongName=name of shortcut.lnk /
/Property
Component
RemoveFile Id=rf_sc On=install Property=sc LongName=name of
shortcut.lnk /
/Component
Never tried it...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Try for [EMAIL PROTECTED]yoursqlserver,8080 where 8080 is the non-default
portnumber for your sqlserver
AFAIK the customaction is not doing any magic with the servername so the
SqlOleDb connect should receive the alternative port.
http://www.sqlmanager.net/en/articles/1209
Hope this
Have a look at using a bootstrapper.
http://wix.mindcapers.com/wiki/Bootstrapper
The real answer to your question is: you can't, because MSI will not
allow to run another MSI.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
First of all, I'm trying to register and .OCX that is already in the computer,
and not included on the package itself.
Is that possible?
I see no reason why that wouldn't be possible, but you might want to use a
FileSearch to get the path to the OCX
Second of all, I'm trying to register
Maybe this helps:
http://wix.mindcapers.com/wiki/ICE57
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of V K
Gangwar
Sent: Friday, September 21, 2007 11:46 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ICE57 Warning...
Hello
Do you merge the html_help_registration found in the VSSDK?
Merge DiskId=1 Id=msm Language=1033
SourceFile=Merge\HTML_Help_Registration__RTL_X86_---.msm /
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve
Maillet
Sent: Friday,
Did you try ExeCommand=//setup ?
Rene
From: [EMAIL PROTECTED] on behalf of Xin Liu (Intl Vendor)
Sent: Fri 9/14/2007 11:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Devenv /setup does half of the work
At the end of our installation, an
to be missing something, but it's not clear to me what that could
be...
From: Schrieken, Rene [mailto:[EMAIL PROTECTED]
Sent: Friday, September 14, 2007 5:11 AM
To: Steve Maillet; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] install integrated MSHelp2 with WixVSExtensions.dll
AFAIK Julie Campbell is doing the same (with almost the same rationale)
at http://wix.mindcapers.com/wiki/Main_Page
Which can be updated without too much struggle...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas
Leigh
Sent: Wednesday,
Otherwise just disable validation.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ratula
Das, HCL-Industry Solutions
Sent: Friday, September 07, 2007 12:16 PM
To: Frank Mayer-Potschak; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Main problem with Votive 2.0 is its use of a native project file format
(not msbuild compatible).
You could however use the Votive 3.0 stuff to have an msbuild compatible
project file and change the Import files in the wixproj file to use wix
v2.0 msbuild targets.
It sounds like you first need to obtain the *.msm files. You really do
need those files. Just ask the devs who handed over the project to you.
From: V K Gangwar [mailto:[EMAIL PROTECTED]
Sent: Monday, September 03, 2007 7:28 AM
To: Schrieken, Rene; wix-users
And I guess you still didn't find the time to re-implement that :-)
From: Christopher Painter [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 02, 2007 8:15 PM
To: Schrieken, Rene; Werner, Harvey D; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users
http://msdn2.microsoft.com/en-us/library/Aa369752.aspx
says: You cannot guarantee the order..
They suggest to author a CustomAction type 19, in wix that would be a custom
action with the Error attribute set, but I have never done that.
Rene
From: [EMAIL
The .msm files are merge files. They contain prepackaged components and add
stuff needed by your msi.
From: [EMAIL PROTECTED] on behalf of V K Gangwar
Sent: Fri 8/31/2007 17:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSI building problem...
'...in the wix source file...' would indicate that you now have only one wxs
file? You can have more than one wxs file.
From: [EMAIL PROTECTED] on behalf of Pierson Lee (Volt)
Sent: Fri 8/31/2007 17:49
To: Anidil; wix-users@lists.sourceforge.net
Subject: Re:
There isn't.
From: [EMAIL PROTECTED] on behalf of V K Gangwar
Sent: Fri 8/31/2007 16:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Decompiling .msi through MS Visual Studio 2005
Hello,
Is there any way to decompile .msi file in MS Visual Studio
As far as I know only bitmap and jpeg are supported formats in MSI.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, August 28, 2007 11:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Image Transparency
Can
Does anyone know why this is not the case for XP/2000/2003 ?
Wild guess: Vista is Windows Installer 4.0, XP/2000/2003 is Windows
Installer 3.0 or less?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
Topley
Sent: Wednesday, August 29, 2007 9:30
: error CNDL0001 : Cannot have ']]' inside an XML CDATA block.
Any clues?
Best regards.
Schrieken, Rene wrote:
I have no experience with Installshield so I cannot comment on that. And
if you have a working merge module that will`save time but i really wonder
what the benefit
See:http://www.msifaq.com/a/1043.htm
I think you should split your files...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dieter
Oberndorfer
Sent: Tuesday, August 28, 2007 4:46 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Filesize
I think you better off with $(env.SystemDrive) but that is only available in
WinNT or this property:
WindowsVolume Property
The installer sets the WindowsVolume property to the volume of the windows
folder. The property always ends with a backslash. This can be used to set the
default
The CreateProcessW is called with NULL as its currentdirectory parameter.
From the win32 sdk:
If this parameter is NULL, the new process will have the same current drive
and directory as the calling process
As msiexec is in system32...
I'm not sure if this might work:
make your commandline
You could use the SqlExpress package that comes with the .Net 2.0 SDK. (program
files\Microsoft Visual stuido 8\sdk\v2.0\BootStrapper\Packages\SqlExpress). But
to use it with your MSI you need to create a bootstrapper (a setup that checks
for and/or install Sqlexpress and then starts your msi).
Any errors in the log if you run msiexec /x yourmsi.msi /lvx* yourmsi.log?
Is the service also still running?
Rene
From: [EMAIL PROTECTED] on behalf of Wik Carl-Johan
Sent: Fri 8/24/2007 14:04
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Uninstall
Nested MSI's are deprecated.
Use a bootstrapper. There is a VS2005 SetupBootstrapper SDK. Not sure
where it is...:-(
This might help in creating manifest files
http://www.codeplex.com/bmg
Wix 3.0 has also something in the works. Setupbld.exe(?) but I did not
use it yet.
Did you check heat (or tallow for v2.x) to generate wix for the registration of
dll's? Or is the dll doing some magic?
From: [EMAIL PROTECTED] on behalf of Petrut Andrei
Sent: Wed 8/22/2007 15:22
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] how to
PROTECTED]
Sent: Wed 8/22/2007 15:54
To: Schrieken, Rene
Subject: Re: [WiX-users] how to use Use regsvr32 in cmd
No, I haven't. But isn't easier just to execute from the cmd prompt ?
Andrei PETRUT
- Original Message
From: Schrieken, Rene [EMAIL PROTECTED]
To: Petrut Andrei [EMAIL
: Dana Gutride [mailto:[EMAIL PROTECTED]
Sent: Wed 8/22/2007 19:33
To: Schrieken, Rene
Subject: Re: [WiX-users] ConfigureSQL Leaked MSIHANDLE
We are using both sqlfilespec and logfilespec.
Dana
On 8/22/07, Schrieken, Rene [EMAIL PROTECTED] wrote:
Hi Dana,
Just a quick
Can you also check scaexec.cpp (wix2.0):
I believe this should be fixed:(line 610 onwards)
before:
hr = WcaReadStringFromCaData(pwz, pwzTemp);
ExitOnFailure1(hr, failed to read log file spec name from custom action data:
%S, pwz);
hr = StringCchCopyW(sfLog.wzName, countof(sfDb.wzName),
I'm not sure why this happens... but in Wix2.x there is also a
scasched.dll which I can not find in the Wix3.x tree. Maybe this is
related to the issue that not all files are included in either the
binaries and/or the MSI.
The source code still exists...
Did you install Votive that comes with the Wix 3.0 binaries?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, August 17, 2007 9:10 AM
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] SQL-Error
My guess is: your *.wixproj was created with Votive 2.0?
Votive 2.0 and 3.0 project file formats are not compatible.
-Original Message-
From: Chris [mailto:[EMAIL PROTECTED]
Sent: Friday, August 17, 2007 11:13 AM
To: Schrieken, Rene
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED
It should work without any extra effort. Or do you receive errors on
uninstall?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of barbq
Sent: Monday, August 13, 2007 2:56 PM
To: WiX-Users
Subject: [WiX-users] Uninstalling a non-app
Hi,
My
Do not worry about the installed files. Worry about the textfile (re-)
patching... but I'm not an expert on that topic
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
barbq
Sent: Monday, August 13, 2007 4:05 PM
To: Schrieken, Rene; WiX-Users
You can run this xslt sheet to create the ComponentRefs (with your xslt
processor of choice, I use VS2005, :-) )
I did not try it yet with WixV3.0. I changed the stylesheet tag for the
xmlns:wix attribute to match the wixv3.0 namespace but did not test it.
?xml version=1.0 encoding=utf-8?
I would verify your speculation by running sql server profiler during install
From: [EMAIL PROTECTED] on behalf of chetan1983
Sent: Fri 8/10/2007 19:16
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Executing Multiple Sql scripts
Hi All,
I need to
Not sure what you want. Do you want to prevent system shutdown during
install? Or do you want to fiddle with powerscheme's?
Anyway:
http://msdn2.microsoft.com/en-us/library/aa373151.aspx
But no Wix in here. You'll need a CA for that.
-Original Message-
From: [EMAIL PROTECTED]
Does this do what you want? It launches a browser when the install
finishes
http://www.tramontana.co.hu/wix/lesson6.php#6.2
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Line
Sent: Wednesday, August 08, 2007 12:30 PM
To:
If you validate your msi you might find issues quicker.
Add this:
Property Id=net Value=C:\WINDOWS\system32\net.exe
Change the Target attribute of your shortcut to read Target=[net]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Value=C:\WINDOWS\system32\net.exe/
From: Venkatesh Malepati [mailto:[EMAIL PROTECTED]
Sent: Wed 8/8/2007 19:36
To: Schrieken, Rene; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Hi Rob and all
Are there any tools to validate?. I just use Notepad
You're doing it too late indeed. During msbuild (BeforeCompile?) grasp
the build version and write it to a (new?) wxs file. Then add that wxs
file to your Compile itemgroup to get it compiled (and linked) to an
msi.
Although wix and msbuild/nant follow a declarative style of getting
things done,
situation.
Rene
-Original Message-
From: Chandan Koushik [mailto:[EMAIL PROTECTED]
Sent: Monday, August 06, 2007 7:55 AM
To: Schrieken, Rene
Subject: RE: [WiX-users] Web controls of asp.net not visible afterdeployment.
Hi,
Could you please provide the path/name of the assembly
PROTECTED]
Sent: Monday, August 06, 2007 8:26 AM
To: Schrieken, Rene
Subject: RE: [WiX-users] Web controls of asp.net not visible afterdeployment.
Hummm wait hold on I will describe the situation once again.
I developed a simple asp.net web application which has some html controls and a
few web
It depends on your hardware but for common stuff a RegistrySearch in
HKLM\System\CurrentControlSet\Enum might help. But you need information
from the driver manufacturer to understand the meaning of all those keys
and values.
If you need to 'query' your own/special hardware you need a CA.
Hmmm, you are not giving to much details away so I have a wild guess: The
assembly containing you webcontrols is not installed in the correct folder. I
suggest you check if the files (and locations) can be found where you expect
them to be.
René
-Original Message-
From: [EMAIL
Dark probably does what Rob M. claims, it represents the package. That
you rather have it represented differently is either a question of taste
or a lack of time of the maintainer of dark. That you cannot recompile a
darked wxs to a working package is a good sign. It means that the
compiler and
Almost nothing is wrong, but I think it has two issues (one major, one minor):
- explorer.exe is always exiting after launching so asyncWait will behave the
same as asyncNoWait
- you will launch two processes. If you are a performance freak, stay away from
this :-)
ShellExecute does not have
At my box it launches Fire*** after I made it my default browser AND killed the
explorer process via the taskmanager. Explorer is not the MS webbrowser, it is
the Shell (or Programmanager if you're from before win95) hosting your desktop,
startmenu and taskbar. Iexplorer is the webbrowser but
Julie,
If you only have one language resource, you should not have to rely on
sattelites. Did you set the
Assembly::NeutralResourcesLanguage(en-US,
UltimateResourceFallbackLocation.MainAssembly)
Otherwise you could have a sub directory relative to your exe where the
satellite assembly resides.
I think you're missing an InstallUiSequence with a Show
Dialog=SelectLanguageDlg After=someaction /
I'm not sure if this works, never tested it in conjuction with WixUI_Minimal
Rene
From: [EMAIL PROTECTED] on behalf of Ward, Mike (MED US)
Sent: Mon 6/18/2007
for someone who would rather programatically
generate the setup.exe.
Regards,
//aj
On 6/16/07, Schrieken, Rene [EMAIL PROTECTED] wrote:
I'm not sure why you actually created a console app to do that?
If you put this in a file called setup.proj:
Project xmlns=http
I'm not sure why you actually created a console app to do that?
If you put this in a file called setup.proj:
Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
ItemGroup
BootstrapperFile Include=SQL.2005.Backwards.Compatibility
ProductNameSQL 2005
Try:
caspol -ag 1 -url file://Y:\Wix FullTrust
From: [EMAIL PROTECTED] on behalf of dave_c
Sent: Fri 6/15/2007 16:41
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] That assembly does not allow partially trusted callers
And here is the message
Can it be that creating the system restore point takes (extra) time?
At least that is what I see if I run filemon during an install...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: vrijdag 25 mei 2007 14:12
To:
Anthony,
I'm not sure if you want to capture all your functionality in one build
and or wix script, but I would say: Don't
This is what I do:
I determine the layout of all my files and then author several wix files
for each sku. I rely on fragments (I'm still on 2.0) to factor out
common parts
I use this xlst script to do exactly that...
?xml version=1.0 encoding=utf-8?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:wix=http://schemas.microsoft.com/wix/2003/01/wi;
xsl:output indent=no method=xml/
xsl:strip-space elements=*/
xsl:template
for
suggestions.
Regards,
Richard
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schrieken, Rene
Sent: Friday, May 04, 2007 4:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Q: Nested Installation (CA 7, 23, 39)
Hi all
84 matches
Mail list logo
