date:20100420

Re: [WiX-users] Lux: Other tutorials or complete WiX example?

2010-04-20 Thread Rob Mensching

No, that's not the purpose of Lux. There isn't a tool in the WiX toolset
that verifies that the Windows Installer installs the authored stuff
correctly.

On Tue, Apr 20, 2010 at 11:51 AM, jeff00seattle
wrote:

>
> Hi
>
> I all read  http://wix.sourceforge.net/manual-wix3/lux.htm WiX Advanced
> Topics: Unit-testing custom actions with Lux
>
> What is not clear to me if Lux can validate if the sources that were used
> for WiX harvesting match to the installation after MSI installation.
>
> -
> Thanks
> Jeff in Seattle
> --
> View this message in context:
> http://n2.nabble.com/Lux-Other-tutorials-or-complete-WiX-example-tp4932902p4932976.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SQL Extension broken in WIX 3.5 Beta build 1602?

2010-04-20 Thread Asiri Wanigarathne

Hi Rob,

Update on the issue.

I upgraded to WiX 3.5 build 1616. This works fine as it worked in the build
1526. It installs the database and run the SQL scripts.

Comparison of log files shows that “Doing action: InstallSqlData” is missing
in the MSI built with WiX 3.5 Build 1602.

Thank you.
Regards,
Asiri Wanigarathne

http://www.asiri.name


On 19 April 2010 18:08, Asiri Wanigarathne  wrote:

> Hi Rob,
>
> I have attached log files for both builds. On build 1602 installer doesn't
> pop-up the database already exists dialog. Also it doesn't create the
> database or run the scripts.
>
>
> thanks.
>
> Regards,
> Asiri Wanigarathne
>
> http://www.asiri.name
>
>
> On 17 April 2010 10:48, Asiri Wanigarathne  wrote:
>
>> Rob,
>>
>> I didn't inspect the log files. but when installing status doesn't show
>> SQL Extension tasks such as "Configuring SQL Server", "Creating Database"
>> and "Running SQL Scripts" in Build 1602 where as in build 1526 it does. Also
>> when I check the target SQL server instance installer (build with WiX 3.5
>> Beta Build 1602) has not created a database. Also Installer
>> indicates successful installation.
>>
>> On Monday I can provide you the log files. Do you want log files for
>> installers built with both builds or just build 1602 ?
>>
>> thanks.
>>
>> Regards,
>> Asiri Wanigarathne
>>
>> http://www.asiri.name
>>
>>
>> On 17 April 2010 00:12, Rob Mensching  wrote:
>>
>>> Can you be a bit more specific about what is broken? Is there something
>>> in
>>> the log file showing the SQL Custom Action failing?
>>>
>>> On Fri, Apr 16, 2010 at 3:06 AM, Asiri Wanigarathne >> >wrote:
>>>
>>> > Hi Folks,
>>> >
>>> > The database creation doesn’t work in the installer built with WIX 3.5
>>> Beta
>>> > 1602 as it did with WIX 3.5 Beta 1528 build and earlier builds.
>>> >
>>> > I tested it couple of times by going back and forth between WIX 3.5
>>> beta
>>> > build 1526 and build 1602  and I confirmed that database creation and
>>> > running SQL scripts do not work in the installer build with WIX 3.5
>>> Beta
>>> > build 1602. I think SQL Extension is broken in the build 1602.
>>> >
>>> > Anyone else has noticed this issue with WIX 3.5 beta build 1602?
>>> >
>>> > Thanks.
>>> >
>>> >
>>> > Regards,
>>> > Asiri Wanigarathne
>>> >
>>> > http://www.asiri.name
>>> >
>>> >
>>> --
>>> > Download Intel® Parallel Studio Eval
>>> > Try the new software tools for yourself. Speed compiling, find bugs
>>> > proactively, and fine-tune applications for parallel performance.
>>> > See why Intel Parallel Studio got high marks during beta.
>>> > http://p.sf.net/sfu/intel-sw-dev
>>> > ___
>>> > WiX-users mailing list
>>> > WiX-users@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/wix-users
>>> >
>>> >
>>>
>>>
>>> --
>>> virtually, Rob Mensching - http://RobMensching.com LLC
>>>
>>> --
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> ___
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>
>>
>
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64-bit WiX

2010-04-20 Thread Navid Azimi-Garakani

https://sourceforge.net/tracker/?func=detail&aid=2990115&group_id=105970&atid=642714

-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Tuesday, April 20, 2010 8:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX

Please file a bug for this, if you haven't already.

Thanks,
Mike Carlson

-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com]
Sent: Monday, April 19, 2010 4:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX

Thanks Gary. You are spot on! I just figured this out too but now I am stuck 
with HeatProject failing. It looks like the Heat task in Wix.targets does not 
honor the RunWixToolsOutOfProc property. This looks like a very simple fix 
(just pass the property) -- so I hope this gets into WiX 3.5.

HeatFile, HeatProject and HeatDirectory need to add 
RunAsSeparateProcess="$(RunWixToolsOutOfProc)" to their targets.

Thanks,
Navid

-Original Message-
From: Gary Schorer [mailto:thanatoas...@gmail.com]
Sent: Monday, April 19, 2010 3:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX

To be a little more specific, the _SetDefaultPathValues target is likely what's 
causing you grief. It looks at registry keys to try and detect if the 32-bit 
version of Wix is installed. If so, it sets the WixToolPath property 
accordingly. It then checks if the WixToolPath was set, and if not (i.e. no 
32-bit install was found, therefore we must be 64-bit), it sets 
RunWixToolsOutOfProc to true.

Two things can cause problems with this:

1) Having registry keys from the 32-bit version of Wix on your machine.
2) Manually overriding the WixToolPath property in your build process.

Either one of these will trick the targets into thinking they should be running 
in 32-bit mode. If you're manually setting the WixToolPath property, just set 
RunWixToolsOutOfProc to true in the same place.

On Mon, Apr 19, 2010 at 6:31 PM, Gary Schorer wrote:

> In my case, I just stopped running the Wix tools in process.
> true
>
>
> On Mon, Apr 19, 2010 at 6:21 PM, Navid Azimi-Garakani < 
> naz...@microsoft.com> wrote:
>
>> I am using WiX 3.5.1602.0. If you look at the executables with 
>> corflags, you'll see that they are compiled for the 32-bit architecture.
>>
>> d:\wix\3.5.1602.0>corflags candle.exe
>> Version   : v2.0.50727
>> CLR Header: 2.5
>> PE: PE32
>> CorFlags  : 11
>> ILONLY: 1
>> 32BIT : 1 <-- 32-bit flag
>> Signed: 1
>>
>> d:\wix\3.5.1602.0>corflags light.exe
>> Version   : v2.0.50727
>> CLR Header: 2.5
>> PE: PE32
>> CorFlags  : 11
>> ILONLY: 1
>> 32BIT : 1 <--- 32-bit flag
>> Signed: 1
>>
>> As a result, when loaded from a 64-bit MSBuild process, I am getting 
>> the following exception:
>>
>> 100>Unhandled Exception: System.BadImageFormatException: Could not 
>> 100>load
>> file or assembly 'file:///d:\wix\3.5.1602.0\candle.exe' or one of its 
>> dependencies. An attempt was made to load a program with an incorrect 
>> format.
>> 100>File name: 'file:///d:\wix\3.5.1602.0\candle.exe'
>> 100> at System.Reflection.Assembly._nLoad(AssemblyName fileName, 
>> 100>String
>> codeBase, Evidence assemblySecurity, Assembly locationHint, 
>> StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean
>> forIntrospection)
>> 100> at System.Reflection.Assembly.InternalLoad(AssemblyName
>> 100> assemblyRef,
>> Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean
>> forIntrospection)
>> 100> at System.Reflection.Assembly.LoadFrom(String assemblyFile) at
>> Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteTo
>> olThread(Object
>> parameters)
>> 100> at System.Threading.ExecutionContext.Run(ExecutionContext
>> executionContext, ContextCallback callback, Object state)
>> 100> at System.Threading.ThreadHelper.ThreadStart(Object obj) 
>> 100>Assembly manager loaded from:
>>  C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
>> 100>Running under executable
>> 100>d:\tools\AMD64\managed\urt\v3.5\MSBuild.exe
>> 100>--- A detailed error log follows.
>> 100>=== Pre-bind state information ===
>> 100>LOG: User = ###
>> 100>LOG: Where-ref bind. Location = d:\wix\3.5.1602.0\candle.exe
>> 100>LOG: Appbase = file:///d:/tools/AMD64/managed/urt/v3.5/
>> 100>LOG: Initial PrivatePath = NULL
>> 100>Calling assembly : (Unknown).
>> 100>===
>> 100>LOG: This bind starts in LoadFrom load context.
>> 100>WRN: Native image will not be probed in LoadFrom context. Native 
>> 100>image
>> will only be probed in default load context, like with Assembly.Load().
>> 100>LOG: Using application configuration file:
>> d:\tools\AMD64\managed\urt\v3.5\MSBuild.exe.Config
>> 100>LOG: Using machine configuration file from
>> C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.
>> 100>LOG: Attempting download of new URL
>> file:///d:/wix/3.5.

[WiX-users] Text Field Validation in Wix Custom Dialog

2010-04-20 Thread Vishwajit Walke

Hi,

I've a text box in my custom dialog and I just need  a small validation on it 
and that is I want to restrict it 5 Integers only. Basically I'm entering a 
Port Number through this field. Any Thoughts ?

Here is my control syntax :


Thanks. Vishwajit


READER BEWARE: Unencrypted, unsigned Internet e-mail is inherently insecure.

Internet messages may be corrupted, incomplete, misdirected or may
incorrectly identify the sender. Therefore, nothing in this message or
attachments may be considered legally binding.

THIS MESSAGE IS ONLY INTENDED FOR THE USE OF THE INDIVIDUAL
OR ENTITY TO WHICH IT IS ADDRESSED AND MAY BE PRIVILEGED.

If you are not the intended recipient or their authorized agent, you
may not forward or copy this information and must delete or destroy all
copies of this message and attachments received.

If you have received this communication in error, please notify
Matrikon Inc. by telephone at (780) 448-1010 or emailing ad...@matrikon.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Lux: Other tutorials or complete WiX example?

2010-04-20 Thread jeff00seattle


Hi

I am writting unit tests to validate install of MSI deliverables, and I am
considering to use Lux.

I came across Bob Arnson’s blog 
http://www.joyofsetup.com/2010/02/08/introducing-lux-declarative-unit-testing-for-custom-actions/
Joy of Setup 

I also looked at  http://wix.sourceforge.net/manual-wix3/lux_xsd_index.htm
Lux Schema  and the  http://www.tramontana.co.hu/wix/ WiX tutorial , but
neither cover how to use Lux for unit testing.

I appreciate that Mr. Arnson had written this posting, but I am still not
clear how to use Lux to test an MSI installation.

Are there any other Lux tutorials or even an example usage of Lux to test an
example WiX created MSI installation?

Thanks

-
Thanks
Jeff in Seattle
-- 
View this message in context: 
http://n2.nabble.com/Lux-Other-tutorials-or-complete-WiX-example-tp4932902p4932902.html
Sent from the wix-users mailing list archive at Nabble.com.

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

Re: [WiX-users] Lux: Other tutorials or complete WiX example?

2010-04-20 Thread jeff00seattle


Hi 

I all read  http://wix.sourceforge.net/manual-wix3/lux.htm WiX Advanced
Topics: Unit-testing custom actions with Lux 

What is not clear to me if Lux can validate if the sources that were used
for WiX harvesting match to the installation after MSI installation.

-
Thanks
Jeff in Seattle
-- 
View this message in context: 
http://n2.nabble.com/Lux-Other-tutorials-or-complete-WiX-example-tp4932902p4932976.html
Sent from the wix-users mailing list archive at Nabble.com.

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

Re: [WiX-users] Conditionals: Host OS Version and Host Processor Type?

2010-04-20 Thread Wilson, Phil

This is done with the standard Windows Installer properties, whether you use 
WiX or any other tool to build an MSI file. For OS versions, look at the 
VersionNT property values, and for 64-bit systems the corresponding VersionNT64 
values. 

Phil Wilson 

-Original Message-
From: jeff00seattle [mailto:jeff_tan...@earthlink.net] 
Sent: Tuesday, April 20, 2010 8:45 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditionals: Host OS Version and Host Processor Type?


Hi

Does WiX provide conditionals for restricting install to 
a. Specific Host OS Version, for example: Can install on Win7, Win2008,
WinXP, Win2003, etc...
b. Specific Host Processor type, for example: Can only install on 32-Bit,
64-Bi, x86, x64, etc...

Thanks

-
Thanks
Jeff in Seattle
-- 
View this message in context: 
http://n2.nabble.com/Conditionals-Host-OS-Version-and-Host-Processor-Type-tp4931859p4931859.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
affiliates).



--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] A couple of Wix 2.0 questions

2010-04-20 Thread Rob Mensching

0. Nothing wrong with WiX v2.0. Now InstallUtil, that's a big problem.


1. Assemblies are not committed to the GAC until InstallFinalize. Thus, you
cannot depend on them during your install.

2. Nothing built into the Preprocessor about MSBuild or VS. You need to push
the values down from VS or MSBuild into candle.exe. My MSBuild-fu isn't that
strong so others may be of more use yere.

On Tue, Apr 20, 2010 at 9:56 AM, Mark Modrall  wrote:

> I know I know...  I shouldn't even be using it...  But I inherited this old
> hairball when I got here and no one has wanted to spend the time to upgrade.
>
> I tried to make a quick new installer using our already-written merge
> modules but I ran into a couple of odd quirks...
>
>
> 1)  One merge module installs a few .net assemblies in the GAC.  The
> last, custom step of the new installer is to run InstallUtil.exe on an
> assembly *using* one of the gac components.  But InstallUtil fails because
> trying to run up the assembly - bind failures, saying the gac components
> aren't there.  I've tried a number of things  (declaring InstallFiles
> explicitly, trying to explicitly set the sequence numbers, moving all the
> actions to AdminExecuteSequence) and nothing has worked.  Oddly, moving
> everything to AdminExecuteSequence ran to completion just fine - it just
> didn't execute the  custom actions.  Anyone out there contended with this?
>  Trying to put some pieces in the gac with the installer yet still have them
> available to run InstallUtil.exe on something consuming them?
>
> 2)  In my wxs, I tried to default the platform to the setting from the
> VS Configuration Manager, but none of the methods I found with Google
> appeared to work.  None of the supposed pre-defined variables existed, and I
> couldn't put a  group in a 2.0 wix project.  Are there any
> preprocessor variables in 2.0 that will tell you what configuration you're
> running in?
>
> Thanks
> mark
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] A couple of Wix 2.0 questions

2010-04-20 Thread Mark Modrall

I know I know...  I shouldn't even be using it...  But I inherited this old 
hairball when I got here and no one has wanted to spend the time to upgrade.

I tried to make a quick new installer using our already-written merge modules 
but I ran into a couple of odd quirks...


1)  One merge module installs a few .net assemblies in the GAC.  The last, 
custom step of the new installer is to run InstallUtil.exe on an assembly 
*using* one of the gac components.  But InstallUtil fails because trying to run 
up the assembly - bind failures, saying the gac components aren't there.  I've 
tried a number of things  (declaring InstallFiles explicitly, trying to 
explicitly set the sequence numbers, moving all the actions to 
AdminExecuteSequence) and nothing has worked.  Oddly, moving everything to 
AdminExecuteSequence ran to completion just fine - it just didn't execute the  
custom actions.  Anyone out there contended with this?  Trying to put some 
pieces in the gac with the installer yet still have them available to run 
InstallUtil.exe on something consuming them?

2)  In my wxs, I tried to default the platform to the setting from the VS 
Configuration Manager, but none of the methods I found with Google appeared to 
work.  None of the supposed pre-defined variables existed, and I couldn't put a 
 group in a 2.0 wix project.  Are there any preprocessor 
variables in 2.0 that will tell you what configuration you're running in?

Thanks
mark

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX: Validation after MSI Install?

2010-04-20 Thread Rob Mensching

MSI "validation" translates to "static analysis". Basically, the ICEs verify
many rules by simply looking into your MSI.

On Tue, Apr 20, 2010 at 9:12 AM, jeff00seattle wrote:

>
> Hi
>
> I read Derek Cicerone's excellent article
> http://installing.blogspot.com/2006/04/msi-validation-in-wix.html MSI
> Validation in WiX
>
> Is there a way to WiX script so that MSI will validate installation after
> it
> has completed its install?
>
> Thanks
>
> -
> Thanks
> Jeff in Seattle
> --
> View this message in context:
> http://n2.nabble.com/WiX-Validation-after-MSI-Install-tp4932025p4932025.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Create 32-bit application pool

2010-04-20 Thread Anthony Nelson

I'm creating an app pool using Wix IIsExtension on Windows 7.  I'm
trying to change the app pool to 32 bit using

 







 



...







 

but it fails and I get the following...

 

 

MSI (s) (64:60) [12:23:17:092]: Doing action: CA.ConfigureAppPool

Action 12:23:17: CA.ConfigureAppPool. 

Action start 12:23:17: CA.ConfigureAppPool.

CustomAction CA.ConfigureAppPool returned actual error code 1168 (note
this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (64:60) [12:23:17:373]: Note: 1: 1722 2: CA.ConfigureAppPool 3:
C:\Program Files (x86)\Company\Product\WebSite\ 4:
C:\Windows\SysWOW64\inetsrv\appcmd set apppool
/apppool.name:"ProductAppPool" /enable32BitAppOnWin64:true 

Error 1722. There is a problem with this Windows Installer package. A
program run as part of the setup did not finish as expected. Contact
your support personnel or package vendor.  Action CA.ConfigureAppPool,
location: C:\Program Files (x86)\Company \Product\WebSite\, command:
C:\Windows\SysWOW64\inetsrv\appcmd set apppool
/apppool.name:"ProductAppPool" /enable32BitAppOnWin64:true 

MSI (s) (64:60) [12:23:19:920]: Product: Company Product v1.0.2.0 --
Error 1722. There is a problem with this Windows Installer package. A
program run as part of the setup did not finish as expected. Contact
your support personnel or package vendor.  Action CA.ConfigureAppPool,
location: C:\Program Files (x86)\Company\Product\WebSite\, command:
C:\Windows\SysWOW64\inetsrv\appcmd set apppool
/apppool.name:"ProductAppPool" /enable32BitAppOnWin64:true 

Action ended 12:23:19: CA.ConfigureAppPool. Return value 3.

 

 

If I run the full command as logged it works fine.
(C:\Windows\SysWOW64\inetsrv\appcmd set apppool
/apppool.name:"ProductAppPool" /enable32BitAppOnWin64:true)

 

Anyone have any ideas?  Thanks.

 

--Anthony

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WiX: Validation after MSI Install?

2010-04-20 Thread jeff00seattle


Hi

I read Derek Cicerone's excellent article 
http://installing.blogspot.com/2006/04/msi-validation-in-wix.html MSI
Validation in WiX 

Is there a way to WiX script so that MSI will validate installation after it
has completed its install?

Thanks

-
Thanks
Jeff in Seattle
-- 
View this message in context: 
http://n2.nabble.com/WiX-Validation-after-MSI-Install-tp4932025p4932025.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64-bit WiX

2010-04-20 Thread Mike Carlson (DEV DIV)

Please file a bug for this, if you haven't already.

Thanks,
Mike Carlson

-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com] 
Sent: Monday, April 19, 2010 4:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX

Thanks Gary. You are spot on! I just figured this out too but now I am stuck 
with HeatProject failing. It looks like the Heat task in Wix.targets does not 
honor the RunWixToolsOutOfProc property. This looks like a very simple fix 
(just pass the property) -- so I hope this gets into WiX 3.5.

HeatFile, HeatProject and HeatDirectory need to add 
RunAsSeparateProcess="$(RunWixToolsOutOfProc)" to their targets.

Thanks,
Navid

-Original Message-
From: Gary Schorer [mailto:thanatoas...@gmail.com] 
Sent: Monday, April 19, 2010 3:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX

To be a little more specific, the _SetDefaultPathValues target is likely what's 
causing you grief. It looks at registry keys to try and detect if the 32-bit 
version of Wix is installed. If so, it sets the WixToolPath property 
accordingly. It then checks if the WixToolPath was set, and if not (i.e. no 
32-bit install was found, therefore we must be 64-bit), it sets 
RunWixToolsOutOfProc to true.

Two things can cause problems with this:

1) Having registry keys from the 32-bit version of Wix on your machine.
2) Manually overriding the WixToolPath property in your build process.

Either one of these will trick the targets into thinking they should be running 
in 32-bit mode. If you're manually setting the WixToolPath property, just set 
RunWixToolsOutOfProc to true in the same place.

On Mon, Apr 19, 2010 at 6:31 PM, Gary Schorer wrote:

> In my case, I just stopped running the Wix tools in process.
> true
>
>
> On Mon, Apr 19, 2010 at 6:21 PM, Navid Azimi-Garakani < 
> naz...@microsoft.com> wrote:
>
>> I am using WiX 3.5.1602.0. If you look at the executables with 
>> corflags, you'll see that they are compiled for the 32-bit architecture.
>>
>> d:\wix\3.5.1602.0>corflags candle.exe
>> Version   : v2.0.50727
>> CLR Header: 2.5
>> PE: PE32
>> CorFlags  : 11
>> ILONLY: 1
>> 32BIT : 1 <-- 32-bit flag
>> Signed: 1
>>
>> d:\wix\3.5.1602.0>corflags light.exe
>> Version   : v2.0.50727
>> CLR Header: 2.5
>> PE: PE32
>> CorFlags  : 11
>> ILONLY: 1
>> 32BIT : 1 <--- 32-bit flag
>> Signed: 1
>>
>> As a result, when loaded from a 64-bit MSBuild process, I am getting 
>> the following exception:
>>
>> 100>Unhandled Exception: System.BadImageFormatException: Could not 
>> 100>load
>> file or assembly 'file:///d:\wix\3.5.1602.0\candle.exe' or one of its 
>> dependencies. An attempt was made to load a program with an incorrect 
>> format.
>> 100>File name: 'file:///d:\wix\3.5.1602.0\candle.exe'
>> 100> at System.Reflection.Assembly._nLoad(AssemblyName fileName, 
>> 100>String
>> codeBase, Evidence assemblySecurity, Assembly locationHint, 
>> StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean 
>> forIntrospection)
>> 100> at System.Reflection.Assembly.InternalLoad(AssemblyName 
>> 100> assemblyRef,
>> Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean
>> forIntrospection)
>> 100> at System.Reflection.Assembly.LoadFrom(String assemblyFile) at
>> Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteTo
>> olThread(Object
>> parameters)
>> 100> at System.Threading.ExecutionContext.Run(ExecutionContext
>> executionContext, ContextCallback callback, Object state)
>> 100> at System.Threading.ThreadHelper.ThreadStart(Object obj) 
>> 100>Assembly manager loaded from:
>>  C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
>> 100>Running under executable  
>> 100>d:\tools\AMD64\managed\urt\v3.5\MSBuild.exe
>> 100>--- A detailed error log follows.
>> 100>=== Pre-bind state information ===
>> 100>LOG: User = ###
>> 100>LOG: Where-ref bind. Location = d:\wix\3.5.1602.0\candle.exe
>> 100>LOG: Appbase = file:///d:/tools/AMD64/managed/urt/v3.5/
>> 100>LOG: Initial PrivatePath = NULL
>> 100>Calling assembly : (Unknown).
>> 100>===
>> 100>LOG: This bind starts in LoadFrom load context.
>> 100>WRN: Native image will not be probed in LoadFrom context. Native 
>> 100>image
>> will only be probed in default load context, like with Assembly.Load().
>> 100>LOG: Using application configuration file:
>> d:\tools\AMD64\managed\urt\v3.5\MSBuild.exe.Config
>> 100>LOG: Using machine configuration file from
>> C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.
>> 100>LOG: Attempting download of new URL
>> file:///d:/wix/3.5.1602.0/candle.exe.
>> 100>ERR: Failed to complete setup of assembly (hr = 0x8007000b). 
>> 100>Probing
>> terminated.
>>
>> Do we have a 64-bit compatible version of these executables? I looked 
>> at the assemblies installed when running Wix64.msi but there appears 
>> to be no difference to the ass

[WiX-users] Conditionals: Host OS Version and Host Processor Type?

2010-04-20 Thread jeff00seattle


Hi

Does WiX provide conditionals for restricting install to 
a. Specific Host OS Version, for example: Can install on Win7, Win2008,
WinXP, Win2003, etc...
b. Specific Host Processor type, for example: Can only install on 32-Bit,
64-Bi, x86, x64, etc...

Thanks

-
Thanks
Jeff in Seattle
-- 
View this message in context: 
http://n2.nabble.com/Conditionals-Host-OS-Version-and-Host-Processor-Type-tp4931859p4931859.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

2010-04-20 Thread Rob Mensching

There are several fixes for WiX v3.5 related to IIS coming (this week, I
expect). I'm not sure it will fix all the issues but if you have a problem,
*please* *please* *please* open a bug with all the details you can think of.
Emails get lost we rarely lose bugs.

On Tue, Apr 20, 2010 at 1:53 AM, Igor Paniushkin wrote:

> I just can tell my finding which I came out by looking into history file.
> That using formatted properties for IIS was implemented in 3.5.1519, so you
> can try to use 3.5.1426 build. But I slightly remember that there was
> another issue with creating websites on IIS7, which was fixed in 3.5.1519.
>
> -Original Message-
> From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com]
> Sent: Tuesday, April 20, 2010 10:07 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003
>
> OK, thanks. I said it was an error creating a web site because that is the
> overall goal for the MSI. Does anyone know when this is likely to be fixed,
> or what version I should go back to in order to avoid the regression? If not
> I may have to go back to version 3. NB I also noticed problems creating a
> web application when running this on Windows Server 2008.
>
> Regards
>
> Rob
>
> Robert Jarratt
> Senior Consultant
> Microsoft Consulting Services
> Microsoft Ltd.
> Tel.: +44 (118) 909 4923
> mailto:rjarr...@microsoft.com
>
> This email may contain confidential information. If you are not named on
> the addressee list, please take no action in relation to this email, do not
> open any attachment, and please contact the sender (details above)
> immediately.
> Information in this email is provided in good faith. If you are a customer
> of Microsoft, please refer to the terms and conditions which cover the
> provision of support and consulting services to you/your organization. If
> you are not corresponding in the course of, or in connection with a
> Microsoft contract or programme with its own terms and conditions, please
> note that no liability is accepted by Microsoft for the contents of this
> mail.
> Microsoft Limited (company number 01624297) is a company registered in
> England and Wales whose registered office is at Microsoft Campus, Thames
> Valley Park, Reading. RG6 1WG
>
> -Original Message-
> From: Igor Paniushkin [mailto:ipaniush...@sdl.com]
> Sent: 19 April 2010 20:38
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003
>
> It is not about creating web site, but creating of app pool is failing :(
> It is already in bug database.
>
> -Original Message-
> From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com]
> Sent: Monday, April 19, 2010 6:53 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003
>
> I am trying to create a package that installs a web site on Windows Server
> 2003, using WiX 3.5.1602.0 (the latest I am aware of). No matter what I do I
> get errors like this:
>
> MSI (s) (1C:D4) [16:58:25:165]: Executing op: CacheSizeFlush(,)
> MSI (s) (1C:D4) [16:58:25:165]: Executing op:
> InstallProtectedFiles(AllowUI=1)
> MSI (s) (1C:D4) [16:58:25:165]: Executing op:
> ActionStart(Name=StartMetabaseTransaction,Description=Starting IIS Metabase
> Transaction,)
> MSI (s) (1C:D4) [16:58:25:165]: Executing op:
> CustomActionSchedule(Action=StartMetabaseTransaction,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
> MSI (s) (1C:D4) [16:58:25:165]: Creating MSIHANDLE (412) of type 790536 for
> thread 3028
> MSI (s) (1C:64) [16:58:25:165]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI1E7.tmp, Entrypoint: StartMetabaseTransaction
> MSI (s) (1C!50) [16:58:25:305]: Creating MSIHANDLE (413) of type 790531 for
> thread 848
> MSI (s) (1C!50) [16:58:25:305]: Closing MSIHANDLE (413) of type 790531 for
> thread 848
> MSI (s) (1C:64) [16:58:25:305]: Closing MSIHANDLE (412) of type 790536 for
> thread 3028
> MSI (s) (1C:D4) [16:58:25:305]: Executing op:
> ActionStart(Name=RollbackMetabaseTransaction,Description=Rolling back IIS
> Metabase Transaction,)
> MSI (s) (1C:D4) [16:58:25:305]: Executing op:
> CustomActionSchedule(Action=RollbackMetabaseTransaction,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)
> MSI (s) (1C:D4) [16:58:25:315]: Executing op:
> ActionStart(Name=CommitMetabaseTransaction,Description=Committing IIS
> Metabase Transaction,)
> MSI (s) (1C:D4) [16:58:25:315]: Executing op:
> CustomActionSchedule(Action=CommitMetabaseTransaction,ActionType=11777,Source=BinaryData,Target=**,CustomActionData=**)
> MSI (s) (1C:D4) [16:58:25:315]: Executing op:
> ActionStart(Name=ConfigureIIsExec,Description=Executing IIS Configuration,)
> MSI (s) (1C:D4) [16:58:25:315]: Executing op:
> CustomActionSchedule(Action=ConfigureIIsExec,ActionType=3073,Source=BinaryDat

Re: [WiX-users] Checking for Self install

2010-04-20 Thread Andy Clugston

At the moment I am trying to understand the conditional logic I posted.
Right now, when I attempt to install the condition is evaluating to TRUE and
causing the *first* install to fail.  I am not understanding why it is
evaluating this way.

On Tue, Apr 20, 2010 at 2:02 AM, Sascha Beaumont
wrote:

> So you want to prevent repair, uninstall and upgrades? Ugh.
>
> If the Product ID isn't changing, Windows Installer should bail
> automatically with "Another version of this product is already
> installed" from memory, if you're using an automatically generated
> Product ID you can use the fact that Windows Installer ignores fourth
> version field to detect when none of the first three have changed. See
> my post from last week for more info.
>
> Sascha
>
>
>
>
> On Tue, Apr 20, 2010 at 6:38 AM, Andy Clugston  wrote:
> > I am attempting to determine if a specific version of a product is
> already
> > installed on the system.  I basically want to do this to disallow/bail
> out
> > of an install if the MSI that is being executed is already installed on
> the
> > system.
> >
> > Here is my authoring using 3.0 RTM. I must be missing something simple:
> >
> > Upgrade table.  FWIW, Product and Upgrade GUID is not changing for each
> > build; only GUID that is changing is the Package GUID.  Language
> attribute
> > matches as well.
> >
> > 
> >
> >   >  IncludeMinimum='yes'
> >  Maximum='$(var.ProdVer)'
> >  IncludeMaximum='yes'
> >  OnlyDetect='yes'
> >  Language='1033'
> >  Property='SELFFOUND'/>
> >
> >
> > Check to see if product previously installed *and* is this specific
> version.
> >
> > Installed AND SELFFOUND
> >
> > Thanks.
> >
> --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

2010-04-20 Thread Igor Paniushkin

I just can tell my finding which I came out by looking into history file.
That using formatted properties for IIS was implemented in 3.5.1519, so you can 
try to use 3.5.1426 build. But I slightly remember that there was another issue 
with creating websites on IIS7, which was fixed in 3.5.1519.

-Original Message-
From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com] 
Sent: Tuesday, April 20, 2010 10:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

OK, thanks. I said it was an error creating a web site because that is the 
overall goal for the MSI. Does anyone know when this is likely to be fixed, or 
what version I should go back to in order to avoid the regression? If not I may 
have to go back to version 3. NB I also noticed problems creating a web 
application when running this on Windows Server 2008.

Regards

Rob

Robert Jarratt
Senior Consultant
Microsoft Consulting Services
Microsoft Ltd.
Tel.: +44 (118) 909 4923
mailto:rjarr...@microsoft.com

This email may contain confidential information. If you are not named on the 
addressee list, please take no action in relation to this email, do not open 
any attachment, and please contact the sender (details above) immediately.
Information in this email is provided in good faith. If you are a customer of 
Microsoft, please refer to the terms and conditions which cover the provision 
of support and consulting services to you/your organization. If you are not 
corresponding in the course of, or in connection with a Microsoft contract or 
programme with its own terms and conditions, please note that no liability is 
accepted by Microsoft for the contents of this mail. 
Microsoft Limited (company number 01624297) is a company registered in England 
and Wales whose registered office is at Microsoft Campus, Thames Valley Park, 
Reading. RG6 1WG

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: 19 April 2010 20:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

It is not about creating web site, but creating of app pool is failing :(
It is already in bug database.

-Original Message-
From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com] 
Sent: Monday, April 19, 2010 6:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

I am trying to create a package that installs a web site on Windows Server 
2003, using WiX 3.5.1602.0 (the latest I am aware of). No matter what I do I 
get errors like this:

MSI (s) (1C:D4) [16:58:25:165]: Executing op: CacheSizeFlush(,)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: InstallProtectedFiles(AllowUI=1)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: 
ActionStart(Name=StartMetabaseTransaction,Description=Starting IIS Metabase 
Transaction,)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: 
CustomActionSchedule(Action=StartMetabaseTransaction,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (1C:D4) [16:58:25:165]: Creating MSIHANDLE (412) of type 790536 for 
thread 3028
MSI (s) (1C:64) [16:58:25:165]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI1E7.tmp, Entrypoint: StartMetabaseTransaction
MSI (s) (1C!50) [16:58:25:305]: Creating MSIHANDLE (413) of type 790531 for 
thread 848
MSI (s) (1C!50) [16:58:25:305]: Closing MSIHANDLE (413) of type 790531 for 
thread 848
MSI (s) (1C:64) [16:58:25:305]: Closing MSIHANDLE (412) of type 790536 for 
thread 3028
MSI (s) (1C:D4) [16:58:25:305]: Executing op: 
ActionStart(Name=RollbackMetabaseTransaction,Description=Rolling back IIS 
Metabase Transaction,)
MSI (s) (1C:D4) [16:58:25:305]: Executing op: 
CustomActionSchedule(Action=RollbackMetabaseTransaction,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
ActionStart(Name=CommitMetabaseTransaction,Description=Committing IIS Metabase 
Transaction,)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
CustomActionSchedule(Action=CommitMetabaseTransaction,ActionType=11777,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
ActionStart(Name=ConfigureIIsExec,Description=Executing IIS Configuration,)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
CustomActionSchedule(Action=ConfigureIIsExec,ActionType=3073,Source=BinaryData,Target=ConfigureIIsExec,CustomActionData=ConfigureIIs151User1Component_1Name1Domain1Password13AppPoolUserWebNetworkService4210021161AppPool1Name1Component_1Attributes2User_1RecycleMinutes2RecycleRequests2RecycleTimes1VirtualMemory2PrivateMemory2IdleTimeout2QueueLimit2CPUMon1MaxProc2ISInstalled2ISAction23TestAppPoolTestPoolWeb8AppPoolUser-2147483648-2147483648-2147483648-2147483648-21

Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

2010-04-20 Thread Rob Jarratt (MCS UK)

OK, thanks. I said it was an error creating a web site because that is the 
overall goal for the MSI. Does anyone know when this is likely to be fixed, or 
what version I should go back to in order to avoid the regression? If not I may 
have to go back to version 3. NB I also noticed problems creating a web 
application when running this on Windows Server 2008.

Regards

Rob
 
Robert Jarratt
Senior Consultant
Microsoft Consulting Services
Microsoft Ltd.
Tel.: +44 (118) 909 4923
mailto:rjarr...@microsoft.com

This email may contain confidential information. If you are not named on the 
addressee list, please take no action in relation to this email, do not open 
any attachment, and please contact the sender (details above) immediately.
Information in this email is provided in good faith. If you are a customer of 
Microsoft, please refer to the terms and conditions which cover the provision 
of support and consulting services to you/your organization. If you are not 
corresponding in the course of, or in connection with a Microsoft contract or 
programme with its own terms and conditions, please note that no liability is 
accepted by Microsoft for the contents of this mail. 
Microsoft Limited (company number 01624297) is a company registered in England 
and Wales whose registered office is at Microsoft Campus, Thames Valley Park, 
Reading. RG6 1WG

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: 19 April 2010 20:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

It is not about creating web site, but creating of app pool is failing :(
It is already in bug database.

-Original Message-
From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com] 
Sent: Monday, April 19, 2010 6:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

I am trying to create a package that installs a web site on Windows Server 
2003, using WiX 3.5.1602.0 (the latest I am aware of). No matter what I do I 
get errors like this:

MSI (s) (1C:D4) [16:58:25:165]: Executing op: CacheSizeFlush(,)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: InstallProtectedFiles(AllowUI=1)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: 
ActionStart(Name=StartMetabaseTransaction,Description=Starting IIS Metabase 
Transaction,)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: 
CustomActionSchedule(Action=StartMetabaseTransaction,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (1C:D4) [16:58:25:165]: Creating MSIHANDLE (412) of type 790536 for 
thread 3028
MSI (s) (1C:64) [16:58:25:165]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI1E7.tmp, Entrypoint: StartMetabaseTransaction
MSI (s) (1C!50) [16:58:25:305]: Creating MSIHANDLE (413) of type 790531 for 
thread 848
MSI (s) (1C!50) [16:58:25:305]: Closing MSIHANDLE (413) of type 790531 for 
thread 848
MSI (s) (1C:64) [16:58:25:305]: Closing MSIHANDLE (412) of type 790536 for 
thread 3028
MSI (s) (1C:D4) [16:58:25:305]: Executing op: 
ActionStart(Name=RollbackMetabaseTransaction,Description=Rolling back IIS 
Metabase Transaction,)
MSI (s) (1C:D4) [16:58:25:305]: Executing op: 
CustomActionSchedule(Action=RollbackMetabaseTransaction,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
ActionStart(Name=CommitMetabaseTransaction,Description=Committing IIS Metabase 
Transaction,)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
CustomActionSchedule(Action=CommitMetabaseTransaction,ActionType=11777,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
ActionStart(Name=ConfigureIIsExec,Description=Executing IIS Configuration,)
MSI (s) (1C:D4) [16:58:25:315]: Executing op: 
CustomActionSchedule(Action=ConfigureIIsExec,ActionType=3073,Source=BinaryData,Target=ConfigureIIsExec,CustomActionData=ConfigureIIs151User1Component_1Name1Domain1Password13AppPoolUserWebNetworkService4210021161AppPool1Name1Component_1Attributes2User_1RecycleMinutes2RecycleRequests2RecycleTimes1VirtualMemory2PrivateMemory2IdleTimeout2QueueLimit2CPUMon1MaxProc2ISInstalled2ISAction23TestAppPoolTestPoolWeb8AppPoolUser-2147483648-2147483648-2147483648-2147483648-2147483648-21474836480-21474836482342100210021002100210021002100210021201Web1Component_1Id1Description1ConnectionTimeout2Directory_1State2Attributes2DirProperties_1Application_1Address1IP1Port1Header1Secure2Log_1ISInstalled2ISAction2SourcePath1TargetPath13TestWebSiteWebTestWebSite-2147483648INSTALLLOCATION-2147483648-2147483648AllUnassigned80www.contoso.com023C:\Program
 Files\SetupProject1\42161Address1W
MSI (s) (1C:D4) [16:58:25:315]: Creating

Re: [WiX-users] Problems during upgrade

2010-04-20 Thread Xmun


Hi Bob,

The issue is that no log seems to created in %temp%.  We have had hundreds
of customers performing successful upgrades and this is the first time that
this was reported.

Our MSI does not exists under the C:\Windows\Installer cache location, so
this customer must have deleted it himself.

Thanks,
Simon
-- 
View this message in context: 
http://n2.nabble.com/Problems-during-upgrade-tp4875957p4929892.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WIX v3.5 for VS 2010

2010-04-20 Thread Sachintha Gurudeniya

Here you can find what you want.
http://wix.sourceforge.net/releases/3.5.1616.0/
HTH



On Tue, Apr 20, 2010 at 4:00 PM, itzik kasovitch wrote:

> Hi,
>
> I am using VS 2010 and would like to download WIX 3.5. It seems that the
> link to the download does not work. Can you please send me a link that
> works? Where can I find the appropriate project aggregator for VS 2010?
>
> --
> Best regards,
> Itzik Kasovitch
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WIX v3.5 for VS 2010

2010-04-20 Thread itzik kasovitch

Hi,

I am using VS 2010 and would like to download WIX 3.5. It seems that the
link to the download does not work. Can you please send me a link that
works? Where can I find the appropriate project aggregator for VS 2010?

-- 
Best regards,
Itzik Kasovitch
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Lux: Other tutorials or complete WiX example?

Re: [WiX-users] SQL Extension broken in WIX 3.5 Beta build 1602?

Re: [WiX-users] 64-bit WiX

[WiX-users] Text Field Validation in Wix Custom Dialog

[WiX-users] Lux: Other tutorials or complete WiX example?

Re: [WiX-users] Lux: Other tutorials or complete WiX example?

Re: [WiX-users] Conditionals: Host OS Version and Host Processor Type?

Re: [WiX-users] A couple of Wix 2.0 questions

[WiX-users] A couple of Wix 2.0 questions

Re: [WiX-users] WiX: Validation after MSI Install?

[WiX-users] Create 32-bit application pool

[WiX-users] WiX: Validation after MSI Install?

Re: [WiX-users] 64-bit WiX

[WiX-users] Conditionals: Host OS Version and Host Processor Type?

Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

Re: [WiX-users] Checking for Self install

Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

Re: [WiX-users] Cannot Create Site on IIS 6 on Windows Server 2003

Re: [WiX-users] Problems during upgrade

Re: [WiX-users] WIX v3.5 for VS 2010

[WiX-users] WIX v3.5 for VS 2010

21 matches

Site Navigation

Mail list logo

Footer information