Keyword not supported: 'application name'

[jjhoweyeprod]

At wits end, not sure what else it could be. . thanks!
I have a different app with similar ConnString and it has no issue.

Happening using SqlClient 5.5.2 and 6.0.1, inside the aspnet:9.0 runtime image.
<PackageReference Include="Microsoft.Data.SqlClient" Version="6.0.1" />
Cannot reproduce locally on Windows 11.

Also not sure why its converting to lowercase.

logger.LogInformation(connString)
await using var connection = new SqlConnection(connString);

Server=PODSDev-db;Database=PODS;Trusted_Connection=False;uid=E_READ;password=xxx;Application Name=My Service Test

Keyword not supported: 'application name'

When I make it one word:

Server=PODSDev-db;Database=PODS;Trusted_Connection=False;uid=e_READ;password=xxx;ApplicationName=My Service Test

Keyword not supported: 'applicationname'

[ErikEJ]

@jjhoweyeprod Maybe you can provide a runnable simple repro (.csproj and Program.cs)

[jjhoweyeprod]

@ErikEJ I can try, I was hoping it was something simple or a known issue as I have other apps that it works fine on.

[benrr101]

@jjhoweyeprod yep, we will definitely need a repro scenario for this one. The keyword you're using should be available, especially on the versions you listed.

One thing to double check, ASP.NET has some unexpected behaviors sometimes with package versions it pulls in. You might want to double check that in the scenario you experience this error, that you are in fact using Microsoft.Data.SqlClient v6.0.1 to make the connection. I've encountered issues where some specific parts of ASP.NET (eg, session managment) will implicitly use older versions of MDS without it being obvious.

[jjhoweyeprod]

I cannot reproduce myself in my repro project, so we can probably close unfortunately.

I suspect it's due to the way the Connection String env. is being injected into the container from our Helm Chart, something else is blowing up and its blaming the final index.
I still can't tell a difference looking at each character by character - my appsettings connstring was identical to my Chart env (pointing to k8s secret)
Even sillier -if I remove Application Name parameter from the k8s secret string it begins to work.

@benrr101
It was using .NET Runtime 9 MCR docker image with this dependency in the csproj that gets restored
PackageReference Include="Microsoft.Data.SqlClient" Version="6.0.1"

Not sure how this is another opportunity for a different one to come in.

[paulmedynski]

Does your password include a semi-colon or other reserved character? What happens if you specify Application Name earlier in the connection string?

[jjhoweyeprod]

Does your password include a semi-colon or other reserved character? What happens if you specify Application Name earlier in the connection string?

Password: No semicolon, only an exclamation mark.

I believe we had tried adding ;Encrypt:no; to the suffix, but had same issues.

The fact I removed the space and it went from 'application name' to 'applicationname' suggests it was partially parsing it. The lowercase it still confusing me.

Anyways, I am going to chalk it up to something with injection of ENV.

[cheenamalhotra]

@jjhoweyeprod Is this issue still occurring?

Have you tried using SqlConnectionStringBuilder instead to generate connection string?

[jjhoweyeprod]

@jjhoweyeprod Is this issue still occurring?

Have you tried using SqlConnectionStringBuilder instead to generate connection string?

I'm unable to get back to an environment to reproduce; I assume it would -- but I also think its something to do with the way env is being injected and handled inside this library.

I had used SqlConnectionStringBuilder and it threw similar exception -- I feel like I saw that it in the stack trace from the normal constructor too.