If InvariantGlobalization is enabled by default, SqlClient will throw an exception

[Varorbc]

Most applications will use EFCore or SqlCilent, and if InvariantGlobalization is enabled by default, SqlClient will throw an exception, although it is easy to remove InvariantGlobalization, But it always leaves users wondering

Originally posted by @Varorbc in #47066 (comment)

[mitchdenny]

What is the exception that is being thrown?

[Varorbc]

@mitchdenny dotnet/SqlClient#1913

[mitchdenny]

OK, there isn't really anything for us to do here since this behavior in SqlClient appears to be by design.

[Varorbc]

As I mentioned before, most applications will use EFCore or SqlClient. If both sides are designed for this purpose, exceptions will occur when used together. Can the two teams communicate to solve this issue?

[mitchdenny]

OK, I think the compromise position here could be to disable invariant mode when the project is created with out the --aot switch. The recent change we made here was really targeting native AOT scenarios where we might be willing to have people have to opt themselves out of invariant culture if they want to use SqlClient.

[ghost]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.