Commented Unassigned: SQL server alias on local machine is always created using shared memory despite the port is specified [20475]

I am installing all-in-one machine having SQL and sharepoint. I am specifying the sql alias for the same machine and the port as I want to have TCP connection. however the script tries to create the shared memory connection .

my computer is DEV1
my config is
<Database>
<DBServer>SPSQL</DBServer>
<DBAlias Create="true" DBInstance="DEV1" DBPort="1433" />
<DBPrefix>SP</DBPrefix>
<ConfigDB>Config</ConfigDB>
</Database>


solution:
change function Add-SQLAlias

replace the line
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {

with
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\")) -and ($port-eq '')) {
Comments: ** Comment from web user: PerrySharePoint **

Just struggled through finding this same bug.

It would be great if this were fixed in the source, so the next person doesn't have to spend the time trying to figure out why it doesn't work, and tracing it back into the powershell, and then coming up with some manual hack around this problem.

(I don't know why the local memory provider option is broken, but that is less relevant to me than getting the install to work.)