Re: [WiX-users] Removing files opened by wuauclt.exe

2006-11-22 Thread Bob Arnson
Brent B. Powers wrote:
 Unfortunately, I can't remove a particular 
 DLL because it's opened by wuauclt.exe.
   

As in Windows Update? Which DLL?

 It's possible that this wouldn't occur within the installer, but only 
 when I'm running the CA outside.
   

MSI loads additional DLLs but probably none that the shell doesn't 
already load.

-- 
sig://boB
http://bobs.org



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Error code lookup

2006-11-22 Thread mike-wix-users
[EMAIL PROTECTED] wrote:
 Is there a way to lookup Wix error codes?  I'm getting CNDL0124, and I'd li
 ke to find out more about the error, so I can start debugging it.

As Rob says, look in messages.xml. IIRC in v3 all the Message elements carry a 
Number attribute so you can simply search for Number=124.

I've looked into this problem before and I think that you've actually got 
malformed XML, or after performing the include step the XML is malformed. I 
noted last time that the Component element is not valid under Include in 
the WiX v2 schema.

The catch block in Preprocessor.cs reports SP1ProbablyNotInstalled if *any* 
XmlException occurs, which seems too aggressive to me. No doubt some exception 
is erroneously thrown if SP1 isn't installed and you try to load an XmlDocument 
from a StringReader, but can we not tell the difference between this and an 
actual malformed document?

-- 
Mike Dimmick



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Modifying registry key permissions for new user

2006-11-22 Thread Matthew Moses
We have a WiX (v3.0.2315.0) project in VS2005 to build an installer
for one of our products. The installer makes use of the User element
to create a new user on the target machine for various purposes. I
have recently been instructed to make sure the user is able to
manipulate a registry key as part of the installation process. By
default, the user is only able to read this particular key, nothing
else.

My initial thought was to use the PermissionEx element nested under an
appropriate RegistryKey element. However, this doesn't seem to work as
the user has not been created by the time the installer attempts to
set the permissions on the registry key.

Another custom action run by our installer also relies on the user
being created, and by sequencing it after InstallFinalize, it worked.
It seems that I could write another custom action that sets the
required permissions, sequence it after InstallFinalize, and have
everything work. Am I on the right track? Did I miss something
important? Is there a better way to do this?

Matthew

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Verb question

2006-11-22 Thread Arnette, Bill
Why does Wix.chm say this about Verb/@Target?

Target file to be executed for the verb. The value should be a formatted
Property to refer to the *short path to the file*, for example:
[!TargetFileId]. Only valid for non-Advertised verbs.


I see no such restriction in the Platform SDK docs about the Verb table
Target column referring to the short path of a file.







-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Verb question

2006-11-22 Thread Bob Arnson
Mike Dimmick wrote:
 It may well have problems if you use a long path with
 spaces in it. This might be considered a bug (I'm not sure if Windows
 Installer would properly quote a [#TargetFileId] expansion). 

It doesn't add quotes, whether they're needed or not. Hence the short 
path recommendation.

-- 
sig://boB
http://bobs.org


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Warning message

2006-11-22 Thread Bob Arnson
Mike Dimmick wrote:
 You'd probably want the condition to be NOT Installed AND VersionNT = 502
 so that Windows XP users didn't also get the message. Assuming, of course,
 that you want the message also to appear on Windows Vista. If not, try
 VersionNT = 502.
   

Yes, sorry I didn't clarify -- the condition in that element controls 
when it's shown. So you can use it for any combination of OS conditions. 
The NOT Installed is important so users don't get it again during 
maintenance.

-- 
sig://boB
http://bobs.org


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Uninstalling while application is running

2006-11-22 Thread John Lalande

I guess this thread has got so long that the original problem needs to be
restated.

If a user uninstalls the application while the application is running, and
then clicks 'Ignore' when the FilesInUse dialog is shown, the uninstall
proceeds but never prompts for a reboot.  If a reboot is done anyway, the
files that were in use are still installed.

Apparently a FilesInUse dialog is not needed in the MSI package.  As I
mentioned, I tried to perform the same steps with the installer that the
tutorial at http://www.tramontana.co.hu/wix/ creates.  This installer showed
a FilesInUse dialog when uninstalling while the program was running and its
MSI doesn't even have a Dialog table.

And as I also mentioned, this package also did not prompt for a reboot and
left the files installed after rebooting.  Whatever problem my installers
have, the tutorial sample also has.

If you'd like I can send the log file for the tutorial package directly to
you for your inspection.  It's only 79KB.  Let me know.

Thanks very much for your time thinking about this and trying to help me
solve this problem.

On 11/22/06, Bob Arnson [EMAIL PROTECTED] wrote:


John Lalande wrote:
 MSI (s) (B4:74) [07:21:22:937]: Scheduling file
 'C:\WINDOWS\Installer\1f6f1.msi' for deletion during post-install
 cleanup (not post-reboot).

 and

 MSI (s) (B4:74) [07:21:22:968]: Scheduling file 'C:\Documents and
 Settings\jlalande\Application

Data\Microsoft\Installer\{27DA485E-B001-4C9E-BAC4-F846034E86EF}\Foobar10.exe'
 for deletion during post-install cleanup (not post-reboot).

Those are both normal. They're just noting that private files MSI
controls will be cleaned up and that doing so won't require a reboot.

 MSI (s) (B4:74) [07:21:15:937]: Note: 1: 2205 2:  3: Error
 MSI (s) (B4:74) [07:21:15:937]: Note: 1: 2228 2:  3: Error 4: SELECT
 `Message` FROM `Error` WHERE `Error` = 1607
 MSI (s) (B4:74) [07:21:15:937]: Note: 1: 2205 2:  3: Error
 MSI (s) (B4:74) [07:21:15:937]: Note: 1: 2228 2:  3: Error 4: SELECT
 `Message` FROM `Error` WHERE `Error` = 1603
 MSI (s) (B4:74) [07:21:15:937]: 1 application(s) had been reported to
 have files in use.
 Info 1603. The file C:\Program Files\Acme\Foobar 1.0\FoobarAppl10.exe
 is being held in use by the following process: Name: FoobarAppl10, Id:
 5400, Window Title: '(not determined yet)'.  Close that application
 and retry.
 MSI (c) (34:8C) [07:21:15:937]: Font created.  Charset: Req=0, Ret=0,
 Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

The 1603 and 1607 codes are, as the next message indicates, for
detecting and showing in-use files. Do you have a FilesInUse dialog in
your .msi package? Is it not showing? Are you getting those log lines
during the UI or execute sequences?

--
sig://boB
http://bobs.org



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Verb question

2006-11-22 Thread Arnette, Bill
The issue is that we use the App Path\Path registry value to specify
additional paths for our application.  We use the full name of the
application which is longer than 8.3.  But because the verb registration
uses the short path name, the App Path entry is not found when the
application is launched by clicking on a document for our application,
and so the dependent dlls are not found.  

I could add an App Path\Path entry based on the short name, except I
don't think I can reliably deduce the short name to register.  Most
likely it will be BLAH~1.EXE, but can I guarantee that?



 -Original Message-
 From: Bob Arnson [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, November 22, 2006 4:43 PM
 To: Mike Dimmick
 Cc: Arnette, Bill; wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Verb question
 
 Mike Dimmick wrote:
  It may well have problems if you use a long path with
  spaces in it. This might be considered a bug (I'm not sure 
 if Windows
  Installer would properly quote a [#TargetFileId] expansion). 
 
 It doesn't add quotes, whether they're needed or not. Hence the short 
 path recommendation.
 
 -- 
 sig://boB
 http://bobs.org
 
 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] New Website install

2006-11-22 Thread Zane Teh
Hi Rob,

We did some investigation and found out our code worked for build 2.0.3719.0, 
but we got the same error for builds 4117 and 4611.  Do you know of any bugs or 
any changes in the schema that could have caused this?  Or is there a work 
around with the later builds?

I have pasted in our code below. Thanks.

--zane


?xml version='1.0'?
Wix xmlns='http://schemas.microsoft.com/wix/2003/01/wi'
  Product Id='775673B7-FFA7-4556-B6F1-F0168CBACC7D' Name='Test Website 
Installer ($(env.BUILDTYPE)) ($(env.BUILDVERSION))' Language='1033' 
Version='$(env.BUILDVERSION)' Manufacturer='Microsoft Corporation'
Package Id='CB7E7DE9-08B1-4667-90B7-777EB1F8936F' Description='Test 
Website Deployment' Comments='Windows Installer package to deploy Test Website' 
InstallerVersion='200' Compressed='yes'/
Media Id='1' Cabinet='Test.cab' VolumeLabel='Disk1'/
Property Id='INSTALLLEVEL'10/Property
Property Id='ALLUSERS'2/Property
Feature Id='TestWebsiteFeature' Title='Test Website' Description='Installs 
the Test Website' Level='1'
  ComponentRef Id='TestWebSite_Install' /
/Feature
WebDirProperties Id='ReadAndExecute'
Read='yes'
Write='no'
Script='yes'
Execute='yes'
AnonymousAccess='yes'
DefaultDocuments='default.aspx' /
Directory Id='TARGETDIR' Name='SourceDir'
  Component Id='TestWebSite_Install' 
Guid='31846218-E623-4055-8D99-DDBF784F8121' DiskId='1'
WebSite Id='TestWebSite' Description='Test Web Site' 
Directory='TARGETDIR' AutoStart='yes' ConfigureIfExists='yes' 
DirProperties='ReadAndExecute'
  WebAddress Id='TestWebSiteAddress' IP='*' Port='83' Secure='no'/
/WebSite
  /Component
/Directory
  /Product
/Wix


From: Rob Mensching
Sent: Tuesday, November 21, 2006 3:52 PM
To: Zane Teh; 'wix-users@lists.sourceforge.net'
Cc: Suresh Parameshwar
Subject: RE: [WiX-users] New Website install

Not off the top of my head.  You might try debugging in and seeing what is 
exactly going wrong.  I'm not currently in a place where I can try an IIS 
install.

From: Zane Teh
Sent: Tuesday, November 21, 2006 15:44
To: Rob Mensching; 'wix-users@lists.sourceforge.net'
Cc: Suresh Parameshwar
Subject: RE: [WiX-users] New Website install

Thanks for the quick reply Rob.  I installed the build 2.0.4611.0 but seem to 
getting the same error.  Any ideas?

--zane
From: Rob Mensching
Sent: Tuesday, November 21, 2006 3:30 PM
To: Zane Teh; 'wix-users@lists.sourceforge.net'
Cc: Suresh Parameshwar
Subject: RE: [WiX-users] New Website install

That's a pretty old build.  I believe there was a couple bug fixes more recent 
than that which may fix the issue you are seeing.  Try grabbing a newer version.

From: Zane Teh
Sent: Tuesday, November 21, 2006 15:27
To: Rob Mensching; 'wix-users@lists.sourceforge.net'
Cc: Suresh Parameshwar
Subject: RE: [WiX-users] New Website install

We are using v2.0.4117.0

From: Rob Mensching
Sent: Tuesday, November 21, 2006 3:24 PM
To: Zane Teh; 'wix-users@lists.sourceforge.net'
Cc: Suresh Parameshwar
Subject: RE: [WiX-users] New Website install

What version of the WiX toolset are you using?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zane Teh
Sent: Tuesday, November 21, 2006 15:01
To: 'wix-users@lists.sourceforge.net'
Cc: Suresh Parameshwar
Subject: [WiX-users] New Website install

Hi All,

I am new to WIX and am trying to install basic website but am running into 
issues.  When I try installing the website I get the following error:

Failed to read IIsWebs table.  (-2147024774   )

Here is the code and settings I currently have:


1.   Snippet of code from Wix:
...
Component Id=TestWebSite_Install 
Guid=896d5f1f-eb73-461c-9fee-43c99577eb26
  WebSite Id=TestWebSite  Description=Test Web Site 
Directory=WEBSITEDIR
WebAddress Id=TestWebSiteAddress IP=* Port=80 /
  /WebSite
/Component
...

2.   There are other websites installed on Port 80 but with different 
Headers.

3.   There is NO Test Web Site that already exists

4.   When I specify IP=All Unassigned OR Port=Port# different from 80 
OR Header=localhost I get the same error.


So far I have only gotten the website to install successfully when I have 
already manually preinstalled a website called Test Web Site but even with 
this I ran into issues:


1.   I tried changing the port number to this preinstalled website from 80 
to 81 and my MSI installed without errors and changed the port back from 81 to 
80.  Although this worked, it did not work when this site was preinstalled on 
port 80 and my MSI had port 81.  When I tried this I still received the same 
error as above.

2.   When I added Header=localhost to the Website attribute in my code, 
the MSI actually overrode a preexisting website that was installed with a 
Header=localhost.  Even when I changed my preinstalled website named Test 
Web 

Re: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready?

2006-11-22 Thread Rob Mensching
I've asked many times for people to send me information that their company uses 
the WiX toolset to build their MSI packages so I can post it on the web site.  
Nobody has been willing to send in their name.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Rockwood
Sent: Monday, November 06, 2006 17:26
To: [EMAIL PROTECTED]; 'Justin Rockwood'; 'Mike Dimmick'; 
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Convincing customer to use WiX toolset - is 
itenterprise ready?

1. Good idea. We should probably do that on our home page.
2. I can get to wix.sourceforge.net just fine. Maybe SourceForge was down for a 
minute? If you keep having problems getting to it, let us know.

Justin

-Original Message-
From: Jacek Blaszczynski [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 5:23 PM
To: 'Justin Rockwood'; 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is 
itenterprise ready?

Hello Justin!

Thnx for this list of references it is really very helpfull to me.
Personally I am not worried for WiX stability or robustness and I used it
for all my installation packages created during last year. Furthermore, I am
a strong advocate of WiX among all my customers.

However, I would strongly recommend to fix 2 small things which create
problems for coders trying to convince their customers to use WiX:

1. Provide official list of most prominent installer packages created with
WiX - it tells actually everything.
2. Provide nice WiX home page linked via sourceforge.net project page -
currently wix.sourceforge.net points to nothing and it may be bad www card
for the package.

Jacek


-Original Message-
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 1:16 AM
To: [EMAIL PROTECTED]; 'Mike Dimmick';
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is
itenterprise ready?

Here are some of the Microsoft products and groups that use WiX for their
installations:

* Office 2007
* Office Server 2007
* Windows SharePoint Server
* SQL Server 2005
* Visual Studio
* Windows Defender

Additionally, there are several non-Microsoft products that use WiX. The
biggest one that comes to mind is MySQL.

There are lots more, but I can't remember off the top of my head. WiX has
become the de-facto installation technology within Microsoft and all of the
major product groups use it for their installations. If you or your client
are worried about the stability, robustness, etc. don't be. The fact that
some of the largest software products in the world use WiX should be
testament enough that it's enterprise ready.

Now, having said that, it doesn't mean that WiX is complete by any means.
There is still lots of active development that goes on in the 3.0 version
(which is still beta). Also, although there's a Visual Studio development
experience, Votive still lacks a lot of the nice GUI designers that you'll
find in Wise or InstallShield. There are some 3rd party designers for WiX
files also available. And yes, sadly our documentation is not up to snuff
yet.

Let us know if you have any other questions.

Justin


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jacek
Blaszczynski
Sent: Monday, November 06, 2006 2:58 PM
To: 'Mike Dimmick'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Convincing customer to use WiX toolset - is
itenterprise ready?

Hello!

Thnx for replies - they are very helpful.

Can someone from MSFT WiX developers confirm which enterprise grade product
installers are currently created with help of WiX package?

Rgrds

Jacek

-Original Message-
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 9:48 PM
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is
itenterprise ready?

I know that Microsoft use WiX for at least some parts of the SQL Server
2005, Office 2007 and Exchange Server 2007 installers.

Version 2.0.x is considered the stable version. It does get bugfixes, but no
major new development. Version 3.0.x is considered the unstable development
version. The versions at
http://sourceforge.net/project/showfiles.php?group_id=105970 of both are
considered particularly stable; there are point releases (approximately
weekly) at http://wix.sourceforge.net/releases/ (when it works).

Most people want to download the binaries or the Votive MSI, not the sources
package. It's self-contained - no other tools are necessary, not even the
Windows Installer SDK. Votive is the GUI, which is a Visual Studio
integration package. The documentation is in the 'doc' folder of the
binaries package as a chm file. Documentation is currently a weak area - the
WiX.chm file gives the syntax, but not really much in the way of semantics.
There's a tutorial at 

Re: [WiX-users] CheckBox question...

2006-11-22 Thread Rob Mensching
Property Id=X is the same as nothing.  If you don't want a Property to have 
a value, don't define the Property.  smile/

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Lovett
Sent: Tuesday, November 07, 2006 12:55
To: david adams; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] CheckBox question...

That worked, thanks.  I guess I was confused by the following warning:

C:\MQ\ndp\fx\src\xmltools\Tools\XmlNotepad\Wix\XmlNotepad.wxs(112,0): Warning 
CNDL1006: Property 'LicenceAccepted' does not contain a Value attribute and is 
not marked as Admin, Secure, or Hidden.  The Property element is being ignored.



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams
Sent: Tuesday, November 07, 2006 11:32 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] CheckBox question...

Chris:

Set your property to no value by default Property Id=LicenseAccepted /

For an unchecked box, I believe that the Property @Value is empty.  Checking
the checkbox sets it to the value defined in the control.

David Adams
MSN MessengerID: [EMAIL PROTECTED]





From: Cullen Waters [EMAIL PROTECTED]
To: Chris Lovett [EMAIL PROTECTED],wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] CheckBox question...
Date: Tue, 7 Nov 2006 11:04:56 -0800
MIME-Version: 1.0
Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by
bay0-mc4-f15.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, 7
Nov 2006 11:05:23 -0800
Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by
sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 36D8B1309B; Tue,  7 Nov
2006 11:05:22 -0800 (PST)
Received: from sc8-sf-mx1-b.sourceforge.net
([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net
with esmtp (Exim 4.43)id 1GhWG5-00084W-2Ufor
wix-users@lists.sourceforge.net; Tue, 07 Nov 2006 11:05:17 -0800
Received: from mail2.microsoft.com ([131.107.115.215]
helo=smtp.microsoft.com)by mail.sourceforge.net with esmtps
(TLSv1:RC4-MD5:128) (Exim 4.44)id 1GhWFz-0006Cj-R2for
wix-users@lists.sourceforge.net; Tue, 07 Nov 2006 11:05:16 -0800
Received: from mailout5.microsoft.com (157.54.69.148)
byTK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168)
withMicrosoft SMTP Server id 8.0.685.15; Tue, 7 Nov 2006 11:04:58 -0800
Received: from IGT-HUB-02.redmond.corp.microsoft.com ([157.54.69.150])
bymailout5.microsoft.com with Microsoft SMTPSVC(6.0.3790.2786); Tue, 7
Nov2006 11:04:58 -0800
Received: from tk1-exhub-c102.redmond.corp.microsoft.com ([157.56.116.113])
byIGT-HUB-02.redmond.corp.microsoft.com over TLS secured channel
withMicrosoft SMTPSVC(6.0.3790.1830);   Tue, 7 Nov 2006 11:04:58 -0800
Received: from NA-EXMSG-C102.redmond.corp.microsoft.com ([157.54.53.6])
bytk1-exhub-c102.redmond.corp.microsoft.com ([157.56.116.113]) with
mapi;Tue, 7 Nov 2006 11:04:57 -0800
X-Message-Info: LsUYwwHHNt2tSteDIfXKnZROuncSXH5N/2+fUqd0FVk=
Thread-Topic: [WiX-users] CheckBox question...
Thread-Index: AccCniaLbvSLaSsLSLWUGe3AIjOMGwAAWk2g
References:
[EMAIL PROTECTED]
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US
X-OriginalArrivalTime: 07 Nov 2006 19:04:58.0262
(UTC)FILETIME=[9E52A360:01C7029F]
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by sourceforge.net.See
http://spamassassin.org/tag/ for more details.Report problems
tohttp://sf.net/tracker/?func=addgroup_id=1atid=210.0 HTML_MESSAGE
BODY: HTML included in message1.2 HTML_ATTR_UNIQUE BODY: HTML
appears to have random attributes intags
X-BeenThere: wix-users@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: General discussion for Windows Installer XML
toolset.wix-users.lists.sourceforge.net
List-Unsubscribe:
https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:[EMAIL 
PROTECTED]
List-Archive:
http://sourceforge.net/mailarchive/forum.php?forum=wix-users
List-Post: mailto:wix-users@lists.sourceforge.net
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe:
https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:[EMAIL 
PROTECTED]
Errors-To: [EMAIL PROTECTED]
Return-Path: [EMAIL PROTECTED]

Just a guess, but I'd try changing the CheckBoxValue=1 to a 0

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Lovett
Sent: Tuesday, November 07, 2006 10:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CheckBox question...

I'm trying to put a check box on my license agreement dialog using the
following:

 Control Id=AgreeCheckBox Type=CheckBox
  Text={\DlgFont8}I amp;accept the terms in the License
Agreement
  X=5 Y=207 Width=250 Height=15
Property=LicenceAccepted CheckBoxValue=1/

Where the property is defined as :
Property Id=LicenceAccepted Value=0/Property

But the checkbox comes up pre-checked.  How do I force the checkbox to come
up unchecked to 

Re: [WiX-users] How do I install a Win32 service that uses SvcHost.exe?

2006-11-22 Thread Rob Mensching
AFAIK, the Windows Installer doesn't support creating services like that.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Byron Changuion
Sent: Tuesday, November 07, 2006 15:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How do I install a Win32 service that uses SvcHost.exe?

Hi,

I have a Win32 service that should be installed with my MSI.  The typical WIX 
entry for a service would look something like:

Component Id='MyDemoComponents' Guid='----'
File Id=MyServiceDll Name='MySvcDll.dll' LongName='MyService.dll' 
DiskId='1' src='$(env.MySourceDir)\MyService.dll' Vital='yes'/
ServiceInstall Id=MyServiceInstall
Name=MyService
DisplayName=My Service Name
Description=My Service Description
Type=ownProcess
Interactive=no
Start=auto
Vital=yes
ErrorControl=normal
/ServiceInstall
/Component

However, this produces an ImagePath service entry that references 
MyService.Dll, whereas I need to specify something like 
%SystemRoot%\system32\svchost.exe -k MySvcHostGroup.

Cheers,
-Byron.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Error code lookup

2006-11-22 Thread Cullen Waters
Alright, I figured out the problem, and I think it is a bug in the Preprocessor.

In my include files, I am using elements from the Utility extension.  The 
Include tag has xmlns:util=:.  When this file is included in my main .wxs, by 
using ?include ?, the Include element is stripped out.  This removes the 
xmlns:util attribute from the top of the included section.

Because my .wxs file does not use any elements in the util namespace, the root 
element in that file does not contain the xmlns attribute.  This causes an XML 
exception, because the elements in the Included section have util: prefixes, 
which is not declared in the concatenated xml.

I'm going to work on a fix, which I'll submit Monday or Tuesday.

As a workaround, I just added the xmlns:util attribute to my .wxs files, so the 
total xml, after including the include files, is valid XML.

I am also going to submit a change to the error message for this error, and 
note that it is caused by malformed XML, rather than a .NET 1.1 SP1 bugfix.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters
Sent: Wednesday, November 22, 2006 3:05 PM
To: [EMAIL PROTECTED]; Wix-Users List
Subject: Re: [WiX-users] Error code lookup

I agree on the too aggressive bit, especially since Wix is explicitly(in the 
exe.config files) set to run under .net 2.0 as well as 1.1.  Presumably, any 
bug fixes that were present in 1.1 SP1 are also present in 2.0, which means 
that this message is only correct if there is an error, and if the user is 
running under 1.1.

Thanks for the heads-up, Mike, I'll check into the xml, especially how it looks 
after the include is processed.  I will send out an email once I find the root 
cause, so everyone can share in the learning.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, November 22, 2006 7:38 AM
To: Cullen Waters; Wix-Users List
Subject: Re: [WiX-users] Error code lookup

[EMAIL PROTECTED] wrote:
 Is there a way to lookup Wix error codes?  I'm getting CNDL0124, and I'd li
 ke to find out more about the error, so I can start debugging it.

As Rob says, look in messages.xml. IIRC in v3 all the Message elements carry a 
Number attribute so you can simply search for Number=124.

I've looked into this problem before and I think that you've actually got 
malformed XML, or after performing the include step the XML is malformed. I 
noted last time that the Component element is not valid under Include in 
the WiX v2 schema.

The catch block in Preprocessor.cs reports SP1ProbablyNotInstalled if *any* 
XmlException occurs, which seems too aggressive to me. No doubt some exception 
is erroneously thrown if SP1 isn't installed and you try to load an XmlDocument 
from a StringReader, but can we not tell the difference between this and an 
actual malformed document?

--
Mike Dimmick



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Convincing customer to use WiX toolset - is itenterprise ready?

2006-11-22 Thread John Vottero
 
 I've asked many times for people to send me information that 
 their company uses the WiX toolset to build their MSI 
 packages so I can post it on the web site.  Nobody has been 
 willing to send in their name.

We use WiX to build our msi packages and we're willing to have our
company and/or product name on the WiX web site.  Let me know if what
you need (if anything).

John Vottero
MVP Systems, Inc.
http://www.mvpsi.com

 
 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Justin Rockwood
 Sent: Monday, November 06, 2006 17:26
 To: [EMAIL PROTECTED]; 'Justin Rockwood'; 'Mike 
 Dimmick'; wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Convincing customer to use WiX 
 toolset - is itenterprise ready?
 
 1. Good idea. We should probably do that on our home page.
 2. I can get to wix.sourceforge.net just fine. Maybe 
 SourceForge was down for a minute? If you keep having 
 problems getting to it, let us know.
 
 Justin
 
 -Original Message-
 From: Jacek Blaszczynski [mailto:[EMAIL PROTECTED]
 Sent: Monday, November 06, 2006 5:23 PM
 To: 'Justin Rockwood'; 'Mike Dimmick'; wix-users@lists.sourceforge.net
 Subject: RE: [WiX-users] Convincing customer to use WiX 
 toolset - is itenterprise ready?
 
 Hello Justin!
 
 Thnx for this list of references it is really very helpfull to me.
 Personally I am not worried for WiX stability or robustness 
 and I used it
 for all my installation packages created during last year. 
 Furthermore, I am
 a strong advocate of WiX among all my customers.
 
 However, I would strongly recommend to fix 2 small things which create
 problems for coders trying to convince their customers to use WiX:
 
 1. Provide official list of most prominent installer packages 
 created with
 WiX - it tells actually everything.
 2. Provide nice WiX home page linked via sourceforge.net 
 project page -
 currently wix.sourceforge.net points to nothing and it may be 
 bad www card
 for the package.
 
 Jacek
 
 
 -Original Message-
 From: Justin Rockwood [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, November 07, 2006 1:16 AM
 To: [EMAIL PROTECTED]; 'Mike Dimmick';
 wix-users@lists.sourceforge.net
 Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is
 itenterprise ready?
 
 Here are some of the Microsoft products and groups that use 
 WiX for their
 installations:
 
 * Office 2007
 * Office Server 2007
 * Windows SharePoint Server
 * SQL Server 2005
 * Visual Studio
 * Windows Defender
 
 Additionally, there are several non-Microsoft products that 
 use WiX. The
 biggest one that comes to mind is MySQL.
 
 There are lots more, but I can't remember off the top of my 
 head. WiX has
 become the de-facto installation technology within Microsoft 
 and all of the
 major product groups use it for their installations. If you 
 or your client
 are worried about the stability, robustness, etc. don't be. 
 The fact that
 some of the largest software products in the world use WiX should be
 testament enough that it's enterprise ready.
 
 Now, having said that, it doesn't mean that WiX is complete 
 by any means.
 There is still lots of active development that goes on in the 
 3.0 version
 (which is still beta). Also, although there's a Visual Studio 
 development
 experience, Votive still lacks a lot of the nice GUI 
 designers that you'll
 find in Wise or InstallShield. There are some 3rd party 
 designers for WiX
 files also available. And yes, sadly our documentation is not 
 up to snuff
 yet.
 
 Let us know if you have any other questions.
 
 Justin
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Jacek
 Blaszczynski
 Sent: Monday, November 06, 2006 2:58 PM
 To: 'Mike Dimmick'; wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Convincing customer to use WiX toolset - is
 itenterprise ready?
 
 Hello!
 
 Thnx for replies - they are very helpful.
 
 Can someone from MSFT WiX developers confirm which enterprise 
 grade product
 installers are currently created with help of WiX package?
 
 Rgrds
 
 Jacek
 
 -Original Message-
 From: Mike Dimmick [mailto:[EMAIL PROTECTED]
 Sent: Monday, November 06, 2006 9:48 PM
 To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
 Subject: RE: [WiX-users] Convincing customer to use WiX toolset - is
 itenterprise ready?
 
 I know that Microsoft use WiX for at least some parts of the 
 SQL Server
 2005, Office 2007 and Exchange Server 2007 installers.
 
 Version 2.0.x is considered the stable version. It does get 
 bugfixes, but no
 major new development. Version 3.0.x is considered the 
 unstable development
 version. The versions at
 http://sourceforge.net/project/showfiles.php?group_id=105970 
 of both are
 considered particularly stable; there are point releases 
 (approximately
 weekly) at http://wix.sourceforge.net/releases/ (when it works).
 
 Most people want to download the binaries or the Votive MSI, 
 not the sources
 

[WiX-users] Wix v2 Appllication launch fails if user changes install path.

2006-11-22 Thread Chuck
Hi,

I have an installer that has a checkbox on the exit dialog that is 
supposed to launch the application.  It works perfectly unless the user 
changes the installation folder?

I added the checkbox and custom action following the method in section 
8.6 of the tutorial.

Any idea as to what would cause this to happen would be greatly appreciated.

Cheers
Chuck

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How do I install a Win32 service that uses SvcHost.exe?

2006-11-22 Thread Anthony Valente
I'm installing a service as part of my install using Wix 3. Here's the
(slightly modified) code I use:

 

Component Id=MyService.exe Guid={----}

File Id=MyService.exe 

Name=MyService.exe 

KeyPath=yes 

Source=C:\BuildOutput\MyService.exe /

ServiceInstall 

Id=MyService.exe.ServiceInstall 

Name=MyService 

DisplayName=My Special Service 

ErrorControl=ignore 

Start=auto 

Type=ownProcess /

ServiceControl 

Id =MyService.exe.ServiceControl 

Name=MyService 

Start=install 

Stop=uninstall 

Remove=uninstall 

Wait=yes /

/Component

 

Hope it helps.

 


Anthony





 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Thursday, November 23, 2006 10:50 AM
To: Byron Changuion; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How do I install a Win32 service that uses
SvcHost.exe?

 

AFAIK, the Windows Installer doesn't support creating services like that.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Byron
Changuion
Sent: Tuesday, November 07, 2006 15:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How do I install a Win32 service that uses SvcHost.exe?

 

Hi,

 

I have a Win32 service that should be installed with my MSI.  The typical
WIX entry for a service would look something like:

 

Component Id='MyDemoComponents'
Guid='----'

File Id=MyServiceDll Name='MySvcDll.dll' LongName='MyService.dll'
DiskId='1' src='$(env.MySourceDir)\MyService.dll' Vital='yes'/

ServiceInstall Id=MyServiceInstall

Name=MyService

DisplayName=My Service Name

Description=My Service Description

Type=ownProcess

Interactive=no

Start=auto

Vital=yes

ErrorControl=normal

/ServiceInstall

/Component

 

However, this produces an ImagePath service entry that references
MyService.Dll, whereas I need to specify something like
%SystemRoot%\system32\svchost.exe -k MySvcHostGroup.

 

Cheers,

-Byron.



smime.p7s
Description: S/MIME cryptographic signature
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Convincing customer to use WiX toolset - isit enterprise ready?

2006-11-22 Thread André Pönitz
Rob Mensching wrote:
 2.  There is a block of documentation in the WiX.chm file 
 that should be in every binaries.zip.  You can also go to 
 http://wix.sourceforge.net and see the online manual and the 
 online tutorial there.  We can always use more documentation 
 but there is definitely documentation available.

When one accesses SF the SF way, documentation will be
expected at http://sourceforge.net/docman/?group_id=105970.

However, this page only contains three Sponsor Links,
no trace of any Wix related documentation at all.

This gives the wrong impression IMHO.

Andre'


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users