date:20110213

Does the same apply to an unmanaged service ( or a managed service with an 
unmanaged reference ) having a dependency on a file in WinSXS?  I'm assuming 
so but haven't had that situation come up.
 
It might not be a problem though.  I know in the case of the GAC, MSI uses 
Fusion which doesn't support transactional installations and hence why the copy 
is delayed until Commit execution  but I'm not sure what MsiPublishAssemblies 
uses under the covers when dealing with WinSXS.

---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me



- Original Message 
From: Neil Sleightholm n...@x2systems.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Sun, February 13, 2011 5:18:46 AM
Subject: Re: [WiX-users] Unmanaged c++ window service installation

There is one thing to watch out for; if a .Net service relies on file in the 
GAC 
then you won't be able to start it in the install as the GAC components aren't 
registered at a point where the start service code runs.

Neil

-Original Message-
From: Mark Turek [mailto:turekm...@hotmail.com] 
Sent: 12 February 2011 23:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

Thank You. That would make sense. If .net service installer is out of the 
picture then SCM is all what matters and then service is a service.

-Original Message-
From: Christopher Painter
Sent: Saturday, February 12, 2011 5:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

That's a bit of a trick question because it assumes one should use custom
actions in the first place.  I always use the built-in standard actions as
encapsulated by the WiX elements ServiceInstall and ServiceControl.

A service is a service is a service.  The Service Control Manager has an API 
and 
it makes no difference if you are using C, C++, C# other then the differences 
in 
how each of those languages interact with that API.  In .NET is't the 
ServiceBase class that helps hide a lot of these details.

I suggest not using the custom action and read the following:

http://blog.deploymentengineering.com/2006/07/msi-vs-net.html 

http://blog.deploymentengineering.com/2011/01/augmenting-installshield-using-windows_19.html
 


---
Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know 
a secret or read a really good thread that deserves attention? E-Mail Me



- Original Message 
From: Mark Turek turekm...@hotmail.com
To: wix-users@lists.sourceforge.net
Sent: Sat, February 12, 2011 5:01:52 PM
Subject: [WiX-users] Unmanaged c++ window service installation

1. Is there any difference between installing managed windows services versus 
unmanaged ones using standard custom actions?
2. If yes then what is the best way to install unmanaged windows service (any
examples?)

I just wanted to get some feedback from you guys to save some time since I am 
not a Wix person. My windows service has it’s own installer which I wrote and I 
could just call it from the custom action dll, which I already have. Is this a 
way to go? There has to be some standard way to do this. What about wix 
utilities?
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users 






8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime 
shortcut.
http://tools.search.yahoo.com/shortcuts/#news 

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users 


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate

Re: [WiX-users] Unmanaged c++ window service installation

2011-02-13 Thread Neil Sleightholm

I'm afraid I have never done any WinSxS to know.

Neil

-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com] 
Sent: 13 February 2011 13:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

Does the same apply to an unmanaged service ( or a managed service with an 
unmanaged reference ) having a dependency on a file in WinSXS?  I'm assuming 
so but haven't had that situation come up.

It might not be a problem though.  I know in the case of the GAC, MSI uses 
Fusion which doesn't support transactional installations and hence why the copy 
is delayed until Commit execution  but I'm not sure what MsiPublishAssemblies 
uses under the covers when dealing with WinSXS.

---
Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know 
a secret or read a really good thread that deserves attention? E-Mail Me

- Original Message 
From: Neil Sleightholm n...@x2systems.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Sun, February 13, 2011 5:18:46 AM
Subject: Re: [WiX-users] Unmanaged c++ window service installation

There is one thing to watch out for; if a .Net service relies on file in the 
GAC 
then you won't be able to start it in the install as the GAC components aren't 
registered at a point where the start service code runs.

Neil

-Original Message-
From: Mark Turek [mailto:turekm...@hotmail.com] 
Sent: 12 February 2011 23:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

Thank You. That would make sense. If .net service installer is out of the 
picture then SCM is all what matters and then service is a service.

-Original Message-
From: Christopher Painter
Sent: Saturday, February 12, 2011 5:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

That's a bit of a trick question because it assumes one should use custom
actions in the first place.  I always use the built-in standard actions as
encapsulated by the WiX elements ServiceInstall and ServiceControl.

A service is a service is a service.  The Service Control Manager has an API 
and 
it makes no difference if you are using C, C++, C# other then the differences 
in 
how each of those languages interact with that API.  In .NET is't the 
ServiceBase class that helps hide a lot of these details.

I suggest not using the custom action and read the following:

http://blog.deploymentengineering.com/2006/07/msi-vs-net.html 

http://blog.deploymentengineering.com/2011/01/augmenting-installshield-using-windows_19.html

---
Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know 
a secret or read a really good thread that deserves attention? E-Mail Me

- Original Message 
From: Mark Turek turekm...@hotmail.com
To: wix-users@lists.sourceforge.net
Sent: Sat, February 12, 2011 5:01:52 PM
Subject: [WiX-users] Unmanaged c++ window service installation

1. Is there any difference between installing managed windows services versus 
unmanaged ones using standard custom actions?
2. If yes then what is the best way to install unmanaged windows service (any
examples?)

I just wanted to get some feedback from you guys to save some time since I am 
not a Wix person. My windows service has it’s own installer which I wrote and I 
could just call it from the custom action dll, which I already have. Is this a 
way to go? There has to be some standard way to do this. What about wix 
utilities?
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users 

8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime 
shortcut.
http://tools.search.yahoo.com/shortcuts/#news 

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net

Re: [WiX-users] Unmanaged c++ window service installation

On Vista+ I'm pretty sure WinSxS is the same (the SxS store is the same). I
don't think we see many issues with WinSxS because not many people used it.
CRT was the biggest customer and they pushed their MSI redist of the MSM
redist pretty hard so the issue was generally avoided.

On Sun, Feb 13, 2011 at 5:43 AM, Christopher Painter
chr...@deploymentengineering.com wrote:

Does the same apply to an unmanaged service ( or a managed service with an
unmanaged reference ) having a dependency on a file in WinSXS? I'm
assuming
so but haven't had that situation come up.

It might not be a problem though. I know in the case of the GAC, MSI uses
Fusion which doesn't support transactional installations and hence why the
copy
is delayed until Commit execution but I'm not sure what
MsiPublishAssemblies
uses under the covers when dealing with WinSXS.

---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me

- Original Message
From: Neil Sleightholm n...@x2systems.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Sun, February 13, 2011 5:18:46 AM
Subject: Re: [WiX-users] Unmanaged c++ window service installation

There is one thing to watch out for; if a .Net service relies on file in
the GAC
then you won't be able to start it in the install as the GAC components
aren't
registered at a point where the start service code runs.

Neil

-Original Message-
From: Mark Turek [mailto:turekm...@hotmail.com]
Sent: 12 February 2011 23:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

Thank You. That would make sense. If .net service installer is out of the
picture then SCM is all what matters and then service is a service.

-Original Message-
From: Christopher Painter
Sent: Saturday, February 12, 2011 5:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unmanaged c++ window service installation

That's a bit of a trick question because it assumes one should use custom
actions in the first place. I always use the built-in standard actions as
encapsulated by the WiX elements ServiceInstall and ServiceControl.

A service is a service is a service. The Service Control Manager has an
API and
it makes no difference if you are using C, C++, C# other then the
differences in
how each of those languages interact with that API. In .NET is't the
ServiceBase class that helps hide a lot of these details.

I suggest not using the custom action and read the following:

http://blog.deploymentengineering.com/2006/07/msi-vs-net.html

http://blog.deploymentengineering.com/2011/01/augmenting-installshield-using-windows_19.html

---
Christopher Painter, Author of Deployment Engineering Blog Have a hot tip,
know
a secret or read a really good thread that deserves attention? E-Mail Me

- Original Message
From: Mark Turek turekm...@hotmail.com
To: wix-users@lists.sourceforge.net
Sent: Sat, February 12, 2011 5:01:52 PM
Subject: [WiX-users] Unmanaged c++ window service installation

1. Is there any difference between installing managed windows services
versus
unmanaged ones using standard custom actions?
2. If yes then what is the best way to install unmanaged windows service
(any
examples?)

I just wanted to get some feedback from you guys to save some time since I
am
not a Wix person. My windows service has it’s own installer which I wrote
and I
could just call it from the custom action dll, which I already have. Is
this a
way to go? There has to be some standard way to do this. What about wix
utilities?

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie
showtime
shortcut.
http://tools.search.yahoo.com/shortcuts/#news

Re: [WiX-users] RemoveFoldersEX error in VS2005

I *think* Bob fixed this in a recent build. Unfortunately, still struggling
with SF servers since they underwent a password attack and reset the whole
system. Apparently they start fixing projects starting at the beginning of
the alphabet.

On Sat, Feb 12, 2011 at 10:29 PM, ERWLive ewhit...@live.com wrote:

 Hi,

 I am trying to use the new RemoveFoldersEx facility in 3.6.1321.0

 Build using VS2005 gives an Error -

 Error4The Component element contains an unhandled extension element
 'util:RemoveFolderEx'.  Please ensure that the extension for elements in the
 'http://schemas.microsoft.com/wix/WixUtilExtension' namespace has been
 provided.C:\Development\Installer
 Projects\ORMWPRunSetup\ORMWPRunSetup\ORMWPRunSetup.wxs2591
  ORMWPRunSetup

 The top of the .wxs file is:-
 ?xml version=1.0 encoding=utf-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
 xmlns:util=http://schemas.microsoft.com/wix/WixUtilExtension;

 The reference is added to the VS solution and points to the correct path to
 the dll.

 The relevant bit of code is:

   DirectoryRef Id=USERAPPDATADIR
  Component Id=CMP_CACHEFLDR
 Guid=270E5C7E-706C-4BB5-95D6-8FFCBBA7F3D9 KeyPath=yes
util:RemoveFolderEx Property=[USERCLIENTCACHE] On=uninstall /
  /Component
/DirectoryRef

 Any assistance will be terribly welcome!

 Eric Whitchurch

 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WriteIIS7ConfigChanges - Stuck with 1603 error codes???

WiX v3.5 RTM has been released (http://bit.ly/wix35). You should upgrade
first to make sure this was a bug we fixed in the final months.

On Wed, Feb 9, 2011 at 7:21 AM, kim contactme...@gmail.com wrote:

@Rob, I am using WIX 3.5.2229 (29-Oct-2010)

@Pierson, I did checked, no virtual directory exists initially by the name
that my setup is trying to create.

Any suggestions please on how can I reslove the problem?
Sincere thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WriteIIS7ConfigChanges-Stuck-with-1603-error-codes-tp6001526p6008021.html
Sent from the wix-users mailing list archive at Nabble.com.

--
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Drop database on Uninstall not working

Verbose log file should show what was executed.

On Fri, Feb 11, 2011 at 2:04 PM, kim contactme...@gmail.com wrote:


 I want to drop the database installed by my msi on uninstall. It does drops
 the Db on roll-back but not on uninstall. Following is the code from my
 config file. Since setting DropOnUninstall=yes did not worked, so I added
 other sql string to execute Drop database command.  I am not receiving any
 error on uninstall and verbose log has no errors. It appears to me that the
 script is not executed?

 can someone suggest whats going wrong here? Thanks!

  Component Id=CreateSolutionDB DiskId=1
 Guid={A4957B82-2F6D-44B7-8AD2-44124F69239C} KeyPath=yes
   sql:SqlDatabase Id=dbSolution Server=[SQLSERVERNAME]\[INSTANCENAME]
 Database=[SOLUTIONDATABASENAME]
 CreateOnInstall=yes ConfirmOverwrite=yes DropOnReinstall=no
 DropOnUninstall=no

  sql:SqlScript Id=CreateTablesSqlScriptWindows ContinueOnError=yes
 ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=1
 BinaryKey=CreateSolutionDBBin /

 sql:SqlString Id=AddWebcoreLogin ContinueOnError=no
 ExecuteOnInstall=yes Sequence=2
 SQL=IF NOT EXISTS(SELECT name FROM sys.server_principals WHERE name =
 '[SOLUTIONUSERNAME]')
 BEGIN
   CREATE LOGIN [SOLUTIONUSERNAME] WITH PASSWORD='[SOLUTIONUSERPASSWORD]';
   CREATE USER [SOLUTIONUSERNAME] FOR LOGIN [SOLUTIONUSERNAME];
 END;/

 sql:SqlString Id=AddRoleToWebcoreUser ContinueOnError=no
 ExecuteOnInstall=yes Sequence=3 SQL=EXEC sp_addrolemember
 'db_owner','[SOLUTIONUSERNAME]'/

 sql:SqlString Id=DropSolutionDB ContinueOnError=no
 ExecuteOnUninstall=yes Sequence=2
 SQL=IF EXISTS (SELECT name FROM sys.databases WHERE name =
 '[SOLUTIONDATABASENAME]')
 BEGIN
 ALTER DATABASE [SOLUTIONDATABASENAME]
 SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
 USE MASTER;
 DROP DATABASE [SOLUTIONDATABASENAME];
 END
 /

 sql:SqlString Id=DropWebcoreLogin ContinueOnError=no
 ExecuteOnUninstall=yes  Sequence=3
 SQL=IF EXISTS(SELECT name FROM sys.server_principals WHERE name =
 '[SOLUTIONUSERNAME]')
   BEGIN
   DROP LOGIN [SOLUTIONUSERNAME];
END/
 /sql:SqlDatabase
 /Component


 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Drop-database-on-Uninstall-not-working-tp6017327p6017327.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1939 when using util:ServiceConfig on Windows Server 2008 R2

If there is a problem in the WiX ServiceConfig custom actions then there
should be more information in the log file about the error. If the problem
is in the Windows Installer's service actions then it becomes an annoying
game of hide and seek to track down all the issues because the Windows
Installer error reporting is basically the same for all things that go
wrong.

My recommendation is that since it works on one OS, try to narrow down what
is different on the other OS.

On Fri, Feb 11, 2011 at 4:13 AM, Jerra beddel...@gmail.com wrote:

 Hi all,
 first email to this list. I have no experience of installers, Wix and
 what have you. I have managed so far by getting help by googling and
 also by some helpful individuals but now I am stuck.

 I have a C# Windows Service project. I have a Install Shield 2011
 Express project for installing this Windows Service. Because IS2011 do
 not directly support such installations I have made a Merge Module in
 Wix which I install via the IS2011 project.
 The final IS2011 installer has been working well (Windows 2003, Windows
 2008 R2, Windows XP).

 I have since realized I need to add dependencies and recovery options
 for this Windows service. This I did by adding the elements :
 - ServiceDependency
 - ServiceConfig
 - ServiceConfigFailureActions
 - util:ServiceConfig

 I tried installing on a Windows Server 2003 32-bit and it worked OK. All
 properties were set for the service as expected.
 Installing on a 64-bit Windows Server 2008 R2 I get this error message:
 Error 1939. Service 'xyz' (xyz) could not be configured. This could be
 a problem with the package or your permissions. Verify that you have
 sufficient privileges to configure system services.

 This is the portion of the XML file concerning the Windows Service:
 ServiceInstall Id=installWS Name=xyz DisplayName=xyz
 Description=abc Start=auto Type =ownProcess ErrorControl =normal
 Vital=yes
   ServiceConfig DelayedAutoStart=yes OnInstall=yes/
   util:ServiceConfig FirstFailureActionType=restart
 SecondFailureActionType=restart ThirdFailureActionType=restart
 RestartServiceDelayInSeconds=60 /
   ServiceConfigFailureActions OnInstall=yes
 Failure Action=1 Delay=2/
   /ServiceConfigFailureActions
   ServiceDependency Id=MSSQL$SQLEXPRESS/
 /ServiceInstall
 ServiceControl Id=controlWS Name=xyz Remove=both
 Stop =both Start=install Wait =yes/


 By blocking/removing these elements the installation works fine on the
 Windows Server 2008 R2.
 - ServiceConfig
 - ServiceConfigFailureActions
 - util:ServiceConfig

 After installation if done, I can then open up the Windows service xyz
 and manually set the recovery for the service to restart without any
 error messages.


 Any help greatly appreciated.


 Kind Regards
 Jerra
 ---
 Visual Studio Professional 2010
 Install Shield 2011 Express
 Wix 3.5  Votive
 Windows XP


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WixUI_Mode property in dialog sets WiXUI_*.wxs

On 02-Feb-11 08:43, Tobias S wrote:
 Just did some dialog modifying. When combining WiXUI_FeatureTree.wxs +
 WiXUI_InstallDir.wxs I mentioned the property WixUI_Mode which is set
 accordingly to the name of the dialog theme. Has this property
   Property Id=WixUI_Mode Value=FeatureTree /
 some special function except for UIDecompiler ?

Not any more. It used to, but I got rid of it during WiX v3.0 development.

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


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] RemoveFoldersEX error in VS2005

On 13-Feb-11 01:29, ERWLive wrote:
 Error4The Component element contains an unhandled extension element 
 'util:RemoveFolderEx'.  Please ensure that the extension for elements in the 
 'http://schemas.microsoft.com/wix/WixUtilExtension' namespace has been 
 provided.

That almost always means that WixUtilExtension wasn't loaded. Check the 
candle.exe command line in the Output window.

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


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] -reusecab doesn't work on dynamic views

On 07-Feb-11 09:44, maksim.vazhe...@emc.com wrote:
 Robocopy to a temp directory is not a very good solution for it... There can 
 be problems, if many people will build package at one time on a build server, 
 there can be not enough space in %temp% directory.

Use hard links. They take up no space other than the directory entry.

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


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Incorrect ICE81 when using PackageCertificates

On 08-Feb-11 13:23, Mike Edenfield wrote:
 Since I am referencing the MsiDigitalCertificate record in
 MsiPackageCertificate, I shouldn't be getting this warning.  I'm
 assuming that the ICE validation routines run by WiX aren't updated for
 Windows Installer 4.5; is there a way to get them updated?

Check out WiX v3.5 and Orca from the latest Windows SDK, both of which 
have the latest CUBs.

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


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] RemoveFoldersEX error in VS2005

On 13-Feb-11 10:55, Rob Mensching wrote:
 I *think* Bob fixed this in a recent build.

That was just a schema fix.

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


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] -reusecab doesn't work on dynamic views

With a -forcereusecab switch, you would want the Binder to always use cabs
if it finds them even if the cabs are out of date with the content that goes
in them? I suppose the intention is that you are going to manage deletion of
the cab cache then?

On Mon, Feb 7, 2011 at 7:29 AM, maksim.vazhe...@emc.com wrote:

 The main point is to reduce the time of nightly builds which run on dynamic
 views. So I don't argue that snapshots are good, but I also want to make
 dynamic views better:)

 Rob, will an option '-forcereusecab' (or something like that) be considered
 as an improvement for light.exe (so I will write a feature request) or
 rebuild of wix.dll with some hack is the only way?:)

 Thanks,
 Maksim.

 -Original Message-
 From: Christopher Painter [mailto:chr...@deploymentengineering.com]
 Sent: Monday, February 07, 2011 5:38 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] -reusecab doesn't work on dynamic views

 How does a dynamic view save you time?  A well crafted config spec should
 load
 only what is needed to do the build.  Whether you load it all up front or
 whether you load it when WiX needs it should be about the same cost, no?
  If
 WiX is going to go off validating things repeatedly then I'd think the cost
 should be less.


 PS-  While we are constantly refining, we've already optimized and
 parallelized.   :-)   I won't go into the details but basically our product
 is
 really massive and we run 100,000+ builds a year.



 ---
 Christopher Painter, Author of Deployment Engineering Blog
 Have a hot tip, know a secret or read a really good thread that deserves
 attention? E-Mail Me



 - Original Message 
 From: maksim.vazhe...@emc.com maksim.vazhe...@emc.com
 To: wix-users@lists.sourceforge.net
 Sent: Mon, February 7, 2011 8:00:25 AM
 Subject: Re: [WiX-users] -reusecab doesn't work on dynamic views

 It was just a little block of build log, maybe it was confusing. Build is
 ok.
 Snapshot views are certainly good for it, but I also want to make it faster
 on
 dynamic views.

 Is it possible to introduce something like '-forcesreusecab' command line
 option
 for light.exe to skip files' validation (so if there is no .cab in the
 directory
 it will be created, if .cab already exists, it won't be checked)?

 Thanks,
 Maksim

 PS- 6 minutes - it is only installer build (when all binaries were already
 built). Maybe you should try to optimize\parallelize your build... :)

 -Original Message-
 From: Christopher Painter [mailto:chr...@deploymentengineering.com]
 Sent: Monday, February 07, 2011 4:38 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] -reusecab doesn't work on dynamic views

 Really?  It seems like your build is broken to me. I already provided a
 work
 around, use a snapshot view.  Use a dynamic view to robocopy to a temp
 directory
 on NTFS.


 There was a discussion on StackOverflow that Light in v3.5 has been updated
 to
 look at md5 checksums and time date stamps.  I can't think of any better
 reason
 to get your build off of a dynamic view because if  light starts hashing
 your
 files over and over that's going to be really slow over the wire back to
 the
 clearcase server.

 PS- I wish my builds were 6 minutes.  One branch of our product line takes
 as
 much as 18 hours to build all the way up.
 ---
 Christopher Painter, Author of Deployment Engineering Blog
 Have a hot tip, know a secret or read a really good thread that deserves
 attention? E-Mail Me



 - Original Message 
 From: maksim.vazhe...@emc.com maksim.vazhe...@emc.com
 To: wix-users@lists.sourceforge.net
 Sent: Mon, February 7, 2011 1:03:37 AM
 Subject: Re: [WiX-users] -reusecab doesn't work on dynamic views

 Chris, I have no problem with the build itself. But now it takes ~6 min for
 one
 package instead of ~2 (when the build runs for 3 platforms for 2 build
 types, it
 is a big delay..).
 Rob, I think the problem here is that light.exe validates the timestamps
 for all
 files each time, and on clearcase dynamic view it is updated continuously.
 I
 have one set of files for all cultures, so I want to reuse .cab during the
 build
 of the package for each culture (I do not need to reuse .cab between the
 builds). Could you provide any workaround for this problem?

 Thanks,
 Maksim.

 -Original Message-
 From: Christopher Painter [mailto:chr...@deploymentengineering.com]
 Sent: Saturday, February 05, 2011 2:38 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] -reusecab doesn't work on dynamic views

 Dynamic views are a clearcase concept.  Basically it's a virtual file
 system
 that uses a config spec to represent a particular branch in source control.
 They can be very useful in certain circumstances ( as the build/install
 lead
 I'm in dozens of vobs and branches daily and I wouldn't want to have to
 always
 be loading snapshot views locally to touch a file here

Re: [WiX-users] WCF server cannot connect to the remote database.

The Installer class is an anti-pattern in setup. You shouldn't use it for
anything.

On Mon, Feb 7, 2011 at 11:49 PM, Rune Moberg jjfl...@gmail.com wrote:

 On Tue, Feb 8, 2011 at 8:26 AM, Thai-Hoa Nguyen taiwa...@hotmail.com
 wrote:
  A way to solve this, I no longer use Wix / ServiceInstall.  I used
 InstallUtil.exe instead.  Then the database connection issue goes away.
  I'm wondering if there is another way to register the WCF service hosted
 by the windows service in Wix--equivalent to InstallUtil.exe.

 Does your setup configure the service identically? Runs as the same
 user? If using named pipes to connect to the SQL Server, then your
 service probably have to run as a domain user.

 One thing that is easy to miss is that the ServiceInstaller class in
 .Net also uses an EventLogInstaller. I don't think that accounts for
 the problem you're seeing, but that is one difference worth paying
 attention to. (plus checking the event log itself might reveal some
 log entries explaining why you struggle hooking up to the database)

 (It would be nice if WiX offered a custom action that would simply
 invoke the Installer class in a given assembly)

 --
 Rune


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] ReserveCost Problem

Might take a look at:
http://msdn.microsoft.com/en-us/library/aa368093(VS.85).aspx. IIRC, changing
directory paths after costing is quirky... and can be quite slow.
On Tue, Feb 8, 2011 at 5:11 AM, Neil Sleightholm n...@x2systems.com wrote:

 I have an install that has 2 install paths, the application and the
 data. I am using a modified WixUI_InstallDir based UI and have created a
 replacement InstallDirDlg.wxs that supports both install paths. For the
 data path I want reserve and extra 5Gb to ensure there is enough disk
 space once the application is running and have added appropriate
 ReserveCost elements to my data path. If I run this on a VM with only
 1Gb free on drive C: and change the data path drive D: it works ok and
 doesn't error due to insufficient disk space.



 If I run the install and leave the data path on C: and let the UI error
 due to insufficient disk space then go back and change the data path to
 D: the file cost doesn't seem to be recalculated and it still fails due
 to insufficient disk space on drive C. If I do the same thing with the
 application folder the file cost is recalculated.



 Is there some magic I need to do to make my install re-run file cost
 after changing the data path? I have looked at the WiX UI source and
 can't see it doing anything special but I am sure if does.



 Thanks in advance.



 Neil



 Neil Sleightholm
 X2 Systems Limited
 n...@x2systems.com mailto:n...@x2systems.com




 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] CAQuietEXEc

Seems reasonable. Does it not work?

On Wed, Feb 9, 2011 at 4:22 AM, Umeshj umesh_jogle...@hotmail.com wrote:


 Hi,

 I am converting the setup to conditionally build for 32 or 64 bit platform.
 Would the following code suffice to make sure that 64 bit WIXCA is used for
 64 bit platform?


 Code snippet:


  ?if $(var.Platform) = x64 ?
  ?define Win64 = yes ?
  ?define PlatformProgramFilesFolder = ProgramFiles64Folder ?
  ?define PlatformCAQuietExecDLLEntry = CAQuietExec64?
  ?define PlatformQtExecCmdLine = QtExec64CmdLine?
  ?else ?
  ?define Win64 = no ?
  ?define PlatformProgramFilesFolder = ProgramFilesFolder ?
  ?define PlatformCAQuietExecDLLEntry = CAQuietExec?
  ?define PlatformQtExecCmdLine = QtExecCmdLine?
  ?endif ?

 
 

 CustomAction Id=QtRestartMyProgramCmd Property=QtRestartMyProgram
Value =[INSTALLLOCATION]MyProgram.exe
 Return=check Execute=immediate /

 CustomAction Id=QtRestartMyProgram BinaryKey=WixCA
 DllEntry=$(var.PlatformCAQuietExecDLLEntry)
Execute=deferred  Impersonate=no/

 .
 ...

 Similarly writing code for immediate QuietcExec command

 Thanks

 Umesh
 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CAQuietEXEc-tp6007460p6007460.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] CAQuietEXEc

BTW, why does  CAQueietExec require the command to be wrapped in Quotes?   I 
was 
wiring up a simple IISRESET.EXE into an internal installer the other day and I 
found that out.   On the other hand, from a paternalistic point of view, it 
might be cool if it forced you to fully qualify the path to the EXE to make 
sure 
you don't have man in the middle attacks.   I ended up doing this and wrapping 
it in quotes.
 
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me



- Original Message 
From: Rob Mensching r...@robmensching.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Sun, February 13, 2011 10:53:56 AM
Subject: Re: [WiX-users] CAQuietEXEc

Seems reasonable. Does it not work?

On Wed, Feb 9, 2011 at 4:22 AM, Umeshj umesh_jogle...@hotmail.com wrote:


 Hi,

 I am converting the setup to conditionally build for 32 or 64 bit platform.
 Would the following code suffice to make sure that 64 bit WIXCA is used for
 64 bit platform?


 Code snippet:


  ?if $(var.Platform) = x64 ?
  ?define Win64 = yes ?
  ?define PlatformProgramFilesFolder = ProgramFiles64Folder ?
  ?define PlatformCAQuietExecDLLEntry = CAQuietExec64?
  ?define PlatformQtExecCmdLine = QtExec64CmdLine?
  ?else ?
  ?define Win64 = no ?
  ?define PlatformProgramFilesFolder = ProgramFilesFolder ?
  ?define PlatformCAQuietExecDLLEntry = CAQuietExec?
  ?define PlatformQtExecCmdLine = QtExecCmdLine?
  ?endif ?

 
 

 CustomAction Id=QtRestartMyProgramCmd Property=QtRestartMyProgram
            Value =[INSTALLLOCATION]MyProgram.exe
            Return=check Execute=immediate /

 CustomAction Id=QtRestartMyProgram BinaryKey=WixCA
 DllEntry=$(var.PlatformCAQuietExecDLLEntry)
            Execute=deferred  Impersonate=no/

 .
 ...

 Similarly writing code for immediate QuietcExec command

 Thanks

 Umesh
 --
 View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CAQuietEXEc-tp6007460p6007460.html
l
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] RemoveFoldersEX error in VS2005

2011-02-13 Thread ERWLive

Hi,

The output window is included below. -ext looks properly set.
-- Build started: Project: ORMWPRunSetup, Configuration: Debug 
x86 --
C:\Program Files\Windows Installer XML 
v3.6\bin\candle.exe -dDebug -dDevEnvDir=C:\Program Files\Microsoft Visual 
Studio 8\Common7\IDE\\ -dSolutionDir=C:\Development\Installer 
Projects\ORMWPRunSetup\\ -dSolutionExt=.sln 
-dSolutionFileName=ORMWPRunSetup.sln 
 -dSolutionName=ORMWPRunSetup -dSolutionPath=C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup.sln -dConfiguration=Debug 
-dOutDir=bin\Debug\ 
 -dPlatform=x86 -dProjectDir=C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\\ -dProjectExt=.wixproj 
-dProjectFileName=ORMWPRunSetup.wixproj 
 -dProjectName=ORMWPRunSetup -dProjectPath=C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\ORMWPRunSetup.wixproj 
-dTargetDir=C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\bin\Debug\\ -dTargetExt=.msi 
-dTargetFileName=ORMWPRunSetup.msi 
 -dTargetName=ORMWPRunSetup -dTargetPath=C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\bin\Debug\ORMWPRunSetup.msi -out 
obj\Debug\ -arch x86 -ext C:\Program Files\Windows Installer XML 
v3.6\bin\WixUtilExtension.dll ORMWPRunSetup.wxs Product.wxs 
obj\Debug\Product.Generated.wxs
C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\ORMWPRunSetup.wxs(259,0): error 
CNDL0200: The Component element contains an unhandled extension element 
'util:RemoveFolderEx'.  Please ensure that the extension for elements in the 
'http://schemas.microsoft.com/wix/WixUtilExtension' namespace has been 
provided.
C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\ORMWPRunSetup.wxs(312,0): error 
CNDL0006: The Property/@Value attribute's value cannot be an empty string. 
If you want the value to be null or empty, simply remove the entire 
attribute.
C:\Development\Installer 
Projects\ORMWPRunSetup\ORMWPRunSetup\ORMWPRunSetup.wxs(312,0): warning 
CNDL1006: Property 'OR_SERVER_SUFFIX' does not contain a Value attribute and 
is not marked as Admin, Secure, or Hidden.  The Property element is being 
ignored.
Done building project ORMWPRunSetup.wixproj -- FAILED.

-Original Message- 
From: Bob Arnson
Sent: Monday, February 14, 2011 3:14 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] RemoveFoldersEX error in VS2005

On 13-Feb-11 01:29, ERWLive wrote:
 Error4The Component element contains an unhandled extension 
 element 'util:RemoveFolderEx'.  Please ensure that the extension for 
 elements in the 'http://schemas.microsoft.com/wix/WixUtilExtension' 
 namespace has been provided.

That almost always means that WixUtilExtension wasn't loaded. Check the
candle.exe command line in the Output window.

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


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users 


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WCF server cannot connect to the remote database.

2011-02-13 Thread Rune Moberg

On Sun, Feb 13, 2011 at 5:48 PM, Rob Mensching r...@robmensching.com wrote:
 The Installer class is an anti-pattern in setup. You shouldn't use it for
 anything.

Could you expand on this?

Speaking purely as an end-user, I will make the following observations:
 1) Windows services should be able to be installed using -i as a
command line switch (more and more developers seem to ignore this, but
it doesn't make it right)
 2) Putting code to register a service in multiple locations is a
maintenance nightmare
 3) The Installer class allows a fairly OK way to implement a -i
switch, while at the same time being easily accessible from a custom
action in the installer (search for a class with the
RunInstaller(true) attribute would be an elegant solution)
 4) Do not forget to set up the event log... (also neatly provided by
the ServiceInstaller class)

If an old-school network admin accidentally removes the service using
'sc delete', he'd welcome a way to quickly put it back without running
an installer. (5 second fix vs however long it takes to run your
installer -- which can be quite time consuming these days)

-- 
Rune

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Drop database on Uninstall not working

2011-02-13 Thread Michael Osmond

Hi

I'd guess your problem is in the script

BEGIN 
 ALTER DATABASE [SOLUTIONDATABASENAME] 
 SET SINGLE_USER WITH ROLLBACK IMMEDIATE; 
 USE MASTER; 
 DROP DATABASE [SOLUTIONDATABASENAME]; 
 END

Does this work in sql management studio - I would guess you need some go 
statements - especially after the Use Master.

Better option to do this would be create a SqlDatabase entry for Master that is 
located under the Product (so it is not associated with a component).

Then run you alter and drop database scripts as two separate scripts associated 
with the Master SqlDatabase entry (these can be under the component).   Don't 
put the USE statement in at all.

Michael

-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: Saturday, 12 February 2011 8:04 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Drop database on Uninstall not working


I want to drop the database installed by my msi on uninstall. It does drops
the Db on roll-back but not on uninstall. Following is the code from my
config file. Since setting DropOnUninstall=yes did not worked, so I added
other sql string to execute Drop database command.  I am not receiving any
error on uninstall and verbose log has no errors. It appears to me that the
script is not executed? 

can someone suggest whats going wrong here? Thanks! 

 Component Id=CreateSolutionDB DiskId=1
Guid={A4957B82-2F6D-44B7-8AD2-44124F69239C} KeyPath=yes 
   sql:SqlDatabase Id=dbSolution Server=[SQLSERVERNAME]\[INSTANCENAME]
Database=[SOLUTIONDATABASENAME] 
CreateOnInstall=yes ConfirmOverwrite=yes DropOnReinstall=no
DropOnUninstall=no 
  
 sql:SqlScript Id=CreateTablesSqlScriptWindows ContinueOnError=yes
ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=1
BinaryKey=CreateSolutionDBBin / 
  
sql:SqlString Id=AddWebcoreLogin ContinueOnError=no
ExecuteOnInstall=yes Sequence=2 
SQL=IF NOT EXISTS(SELECT name FROM sys.server_principals WHERE name =
'[SOLUTIONUSERNAME]') 
BEGIN 
   CREATE LOGIN [SOLUTIONUSERNAME] WITH PASSWORD='[SOLUTIONUSERPASSWORD]'; 
   CREATE USER [SOLUTIONUSERNAME] FOR LOGIN [SOLUTIONUSERNAME]; 
END;/ 

sql:SqlString Id=AddRoleToWebcoreUser ContinueOnError=no
ExecuteOnInstall=yes Sequence=3 SQL=EXEC sp_addrolemember
'db_owner','[SOLUTIONUSERNAME]'/ 

sql:SqlString Id=DropSolutionDB ContinueOnError=no
ExecuteOnUninstall=yes Sequence=2 
SQL=IF EXISTS (SELECT name FROM sys.databases WHERE name =
'[SOLUTIONDATABASENAME]') 
BEGIN 
 ALTER DATABASE [SOLUTIONDATABASENAME] 
 SET SINGLE_USER WITH ROLLBACK IMMEDIATE; 
 USE MASTER; 
 DROP DATABASE [SOLUTIONDATABASENAME]; 
 END 
 / 

sql:SqlString Id=DropWebcoreLogin ContinueOnError=no
ExecuteOnUninstall=yes  Sequence=3 
SQL=IF EXISTS(SELECT name FROM sys.server_principals WHERE name =
'[SOLUTIONUSERNAME]') 
   BEGIN 
   DROP LOGIN [SOLUTIONUSERNAME]; 
END/ 
/sql:SqlDatabase 
/Component  


-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Drop-database-on-Uninstall-not-working-tp6017327p6017327.html
Sent from the wix-users mailing list archive at Nabble.com.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WCF server cannot connect to the remote database.

All of the things you list are essentially SelfReg. SelfReg was deemed a bad
practice for installatin back in the late 1990s. MSI SDK has a list of
reasons why: http://msdn.microsoft.com/en-us/library/aa371608(VS.85).aspx.
It's rather specific to DLLs but the same applies to anything that registers
itself by running code.
On Sun, Feb 13, 2011 at 12:52 PM, Rune Moberg jjfl...@gmail.com wrote:

 On Sun, Feb 13, 2011 at 5:48 PM, Rob Mensching r...@robmensching.com
 wrote:
  The Installer class is an anti-pattern in setup. You shouldn't use it for
  anything.

 Could you expand on this?

 Speaking purely as an end-user, I will make the following observations:
  1) Windows services should be able to be installed using -i as a
 command line switch (more and more developers seem to ignore this, but
 it doesn't make it right)
  2) Putting code to register a service in multiple locations is a
 maintenance nightmare
  3) The Installer class allows a fairly OK way to implement a -i
 switch, while at the same time being easily accessible from a custom
 action in the installer (search for a class with the
 RunInstaller(true) attribute would be an elegant solution)
  4) Do not forget to set up the event log... (also neatly provided by
 the ServiceInstaller class)

 If an old-school network admin accidentally removes the service using
 'sc delete', he'd welcome a way to quickly put it back without running
 an installer. (5 second fix vs however long it takes to run your
 installer -- which can be quite time consuming these days)

 --
 Rune


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WCF server cannot connect to the remote database.

Rune-

 There are two camps of thinking when it comes to installers.  One 
is  imperative scripting using pretty much any framework you want (  NullSoft 
Installer, InstallScript, PowerScript, Wise / SMS,  InnoSetup et al ) and the 
other is a declarative approach that provides a consistent experience with 
such things as transactional installations and upgrades (  Windows Installer ( 
MSI ), WiX, InstallShield, InstallAware, Wise and so on ).  The data driven 
approach also allows administrators to create transforms  to allow the MSI to 
be customized to meet their needs.

 This mailing list ( and myself included ) is clearly in the camp 
of declarative.  I did script installs from 1997 - 2003 and in 2003 I switched 
over to MSI and saw the light.   I can speak from vast experience in saying 
there are really good reasons to not do any of the  things that you 
suggest.  From an MSI perspective they are all anti patterns.

MSI installers that do nothing except copy files and then call out of process 
custom action never end well.   They don't scale and they are brittle as all 
heck. 

For Installer class custom actions, they are horrible because they

1)  Run out of process with no ability to access the MSI handle to query 
tables, 
get/set properties and write to the log.   This means they will never be data 
driven and are useless to debug when ( not if ) they fail.

2)  Tattoo the MSIEXEC process with a specific version of the CLR causing 
subsequent custom actions to fail.  ( Yes, I've witnesssed this. )

3) They throw up a modal dialog when they fail, even when the installer is 
supposed to be running silently.

4) When paired with Visual Studio Deployment Projects they encourage developers 
to reinvent the wheel with fragile out of process custom actions.   MSI already 
has the ability to create services and event logs / sources.  Do you really 
think your code will be better?

PS- If an old school admin is dumb enough to delete a service without first 
recording it's values or creating a snapshot and thinks it's too slow to press 
'repair' to save his neck,  well I think he should just be let go.    Repair is 
meant to be the standardized approach to resolving these problems rather then 
guessing some EXE is a service and what the command line to install it should 
be.
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me



- Original Message 
From: Rune Moberg jjfl...@gmail.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Sun, February 13, 2011 2:52:12 PM
Subject: Re: [WiX-users] WCF server cannot connect to the remote database.

On Sun, Feb 13, 2011 at 5:48 PM, Rob Mensching r...@robmensching.com wrote:
 The Installer class is an anti-pattern in setup. You shouldn't use it for
 anything.

Could you expand on this?

Speaking purely as an end-user, I will make the following observations:
1) Windows services should be able to be installed using -i as a
command line switch (more and more developers seem to ignore this, but
it doesn't make it right)
2) Putting code to register a service in multiple locations is a
maintenance nightmare
3) The Installer class allows a fairly OK way to implement a -i
switch, while at the same time being easily accessible from a custom
action in the installer (search for a class with the
RunInstaller(true) attribute would be an elegant solution)
4) Do not forget to set up the event log... (also neatly provided by
the ServiceInstaller class)

If an old-school network admin accidentally removes the service using
'sc delete', he'd welcome a way to quickly put it back without running
an installer. (5 second fix vs however long it takes to run your
installer -- which can be quite time consuming these days)

If an old school admin is dumb enough to type sc delete without creating a 
snapshot 

-- 
Rune

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



 

Finding fabulous fares is fun.  
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel 
bargains.
http://farechase.yahoo.com/promo-generic-14795097

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and

Re: [WiX-users] Drop database on Uninstall not working

Personally,  I get really nervous exeucting any database scripts during an 
uninstall.   They could fail for any number of reasons and you want to make 
real 
sure this doesn't block you from uninstalling.

Then there is that little matter of a best practice that says you shouldn't 
delete user data.   If the user reinstalls they might expect to still have 
their 
data.   This doesn't hold much water though if your database is actually just 
code tables and lookup data and in that case I'd suggest not using a full blown 
database engine in the first place.
 
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me



- Original Message 
From: Michael Osmond mosm...@baytech.com.au
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Sun, February 13, 2011 4:52:03 PM
Subject: Re: [WiX-users] Drop database on Uninstall not working

Hi

I'd guess your problem is in the script

BEGIN 
    ALTER DATABASE [SOLUTIONDATABASENAME] 
    SET SINGLE_USER WITH ROLLBACK IMMEDIATE; 
    USE MASTER; 
    DROP DATABASE [SOLUTIONDATABASENAME]; 
    END

Does this work in sql management studio - I would guess you need some go 
statements - especially after the Use Master.

Better option to do this would be create a SqlDatabase entry for Master that is 
located under the Product (so it is not associated with a component).

Then run you alter and drop database scripts as two separate scripts associated 
with the Master SqlDatabase entry (these can be under the component).  Don't 
put 
the USE statement in at all.

Michael

-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: Saturday, 12 February 2011 8:04 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Drop database on Uninstall not working


I want to drop the database installed by my msi on uninstall. It does drops
the Db on roll-back but not on uninstall. Following is the code from my
config file. Since setting DropOnUninstall=yes did not worked, so I added
other sql string to execute Drop database command.  I am not receiving any
error on uninstall and verbose log has no errors. It appears to me that the
script is not executed? 

can someone suggest whats going wrong here? Thanks! 

Component Id=CreateSolutionDB DiskId=1
Guid={A4957B82-2F6D-44B7-8AD2-44124F69239C} KeyPath=yes 
  sql:SqlDatabase Id=dbSolution Server=[SQLSERVERNAME]\[INSTANCENAME]
Database=[SOLUTIONDATABASENAME] 
CreateOnInstall=yes ConfirmOverwrite=yes DropOnReinstall=no
DropOnUninstall=no 
                  
sql:SqlScript Id=CreateTablesSqlScriptWindows ContinueOnError=yes
ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=1
BinaryKey=CreateSolutionDBBin / 
                  
sql:SqlString Id=AddWebcoreLogin ContinueOnError=no
ExecuteOnInstall=yes Sequence=2 
SQL=IF NOT EXISTS(SELECT name FROM sys.server_principals WHERE name =
'[SOLUTIONUSERNAME]') 
BEGIN 
  CREATE LOGIN [SOLUTIONUSERNAME] WITH PASSWORD='[SOLUTIONUSERPASSWORD]'; 
  CREATE USER [SOLUTIONUSERNAME] FOR LOGIN [SOLUTIONUSERNAME]; 
END;/ 

sql:SqlString Id=AddRoleToWebcoreUser ContinueOnError=no
ExecuteOnInstall=yes Sequence=3 SQL=EXEC sp_addrolemember
'db_owner','[SOLUTIONUSERNAME]'/ 

sql:SqlString Id=DropSolutionDB ContinueOnError=no
ExecuteOnUninstall=yes Sequence=2 
SQL=IF EXISTS (SELECT name FROM sys.databases WHERE name =
'[SOLUTIONDATABASENAME]') 
BEGIN 
    ALTER DATABASE [SOLUTIONDATABASENAME] 
    SET SINGLE_USER WITH ROLLBACK IMMEDIATE; 
    USE MASTER; 
    DROP DATABASE [SOLUTIONDATABASENAME]; 
    END 
    / 

sql:SqlString Id=DropWebcoreLogin ContinueOnError=no
ExecuteOnUninstall=yes  Sequence=3 
SQL=IF EXISTS(SELECT name FROM sys.server_principals WHERE name =
'[SOLUTIONUSERNAME]') 
  BEGIN 
      DROP LOGIN [SOLUTIONUSERNAME]; 
    END/ 
/sql:SqlDatabase 
/Component  


-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Drop-database-on-Uninstall-not-working-tp6017327p6017327.html

Sent from the wix-users mailing list archive at Nabble.com.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel

Re: [WiX-users] RemoveFoldersEX error in VS2005