Yeah, well, in the solution I skipped over the simple part that makes this a
difficult request to fulfill. I looked in the CustomAction code and saw the
support for it and didn't think about the troubles the Compiler and Linker
would have with such a feature request. Alas, the bug isn't actually fixed
because of the Compiler/Linker issue. Do you mind reactivating it?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dana Gutride
Sent: Thursday, January 11, 2007 9:54 AM
To: [email protected]
Subject: Re: [WiX-devs] [ wix-Bugs-1520745 ] SqlDatabase/@User - Change to
formatted element
That makes sense to me, but I thought that this bug should allow the [EMAIL
PROTECTED] attribute to be formatted text (allowing a property instead of a id
reference). If it is fixed, than using a property in that attribute should be
ok and would eliminate the need for two sqldatabase components depending on
whether the user wants to use windows auth or not.
Dana
On 1/11/07, Rob Mensching <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
That error is trying to tell you that the SqlDatabase/@User attribute should
reference an User/@Id element somewhere.
From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Dana Gutride
Sent: Tuesday, January 09, 2007 7:36 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [WiX-devs] [ wix-Bugs-1520745 ] SqlDatabase/@User - Change to
formatted element
I just downloaded the latest build (2.0.4908.0) and using the following code, I
received a light error LGHT0112, Unresolved reference to symbol
'User:[SQLUSERID]'. Am I using this correctly?
Thanks,
Dana
<User Id='SQLUser' Name='username' Password='userpassword' />
<Directory Id='TARGETDIR' Name='SourceDir'>
<Directory Id='ProgramFilesFolder' Name='PFiles'>
<Directory Id='InstallDir' Name='Acme'>
<Component Id='SqlComponent'
Guid='B735BCD6-982D-40F2-8802-9A17FA1A7E09'>
<SqlDatabase Id='SqlDatabase' Database='Foobar' User='[SQLUSERID]'
Server='mymachine'
CreateOnInstall='yes' DropOnUninstall='yes' ContinueOnError='yes'>
<SqlScript Id='CreateTable' BinaryKey='CreateTable'
ExecuteOnInstall='yes' />
</SqlDatabase>
</Component>
</Directory>
</Directory>
</Directory>
<Binary Id='CreateTable' SourceFile='CreateTable.sql ' />
<Feature Id='SqlFeature' Title='SqlFeature' Level='1'>
<ComponentRef Id='SqlComponent' />
</Feature>
<Property Id='SQLUSERID'>SQLUser</Property>
On 1/8/07, SourceForge.net <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Bugs item #1520745, was opened at 2006-07-11 12:46
Message generated for change (Comment added) made by robmen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1520745&group_id=105970
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: DGutride (dgutride)
>Assigned to: Rob Mensching (robmen)
Summary: SqlDatabase/@User - Change to formatted element
Initial Comment:
Currently, the database custom actions have the option
to connect using Integrated Authentication or SQL
Server Authentication. The way the choice is made is
determined is based on the presence of a SQLUser tag
within the SQLDatabase tag.
The downside to using the current SQLUser tag
methodology as the determining factor is we have to
create two components for each database create tag and
condition those based on the WINDOWS_AUTH property.
This is fine when you are only referencing a few
SQLScripts or SQLStrings. For complicated databases;
however, there can many scripts that need to be
executed and it makes it the installation more prone to
error and much more complicated by requiring these tags
be duplicated.
>From Rob in an e-mail on the Wix-Dev list:
What if we make the SqlDatabase/@User a formatted
element? Then a Property could be used to select the
appropriate SqlUser or empty property to mean Windows
Auth. The code doesn't have to change much at all and
everything behaves pretty much as it does right now.
----------------------------------------------------------------------
>Comment By: Rob Mensching (robmen)
Date: 2007-01-08 16:48
Message:
Logged In: YES
user_id=991639
Originator: NO
This appears to have been fixed many builds ago.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1520745&group_id=105970
-------------------------------------------------------------------------
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.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
