Set InvariantGlobalization in api template

[eerhardt]

API server applications do not typically need culture aware behavior. A better default is to use invariant globalization mode for API apps.

This allows for the globalization code to be trimmed away, making the final executable size smaller. It also reduces startup and memory consumption because ICU isn't loaded.

This also allows the apps to run with consistent behavior on container images that don't include ICU, making the container image smaller as well.

Fix #47029

[mitchdenny]

I'm onboard with this. Just want to represent @DamianEdwards opinion that we need to make sure that we've done the right thing in terms of MSBuild docs. We need that checklist in an issue so we can finalize this.

[captainsafia]

I'm onboard with this. Just want to represent @DamianEdwards opinion that we need to make sure that we've done the right thing in terms of MSBuild docs. We need that checklist in an issue so we can finalize this.

I went ahead and took care of this in dotnet/msbuild#8543 since it was fairly straightforward to do.

[DamianEdwards]

I'm onboard with this. Just want to represent @DamianEdwards opinion that we need to make sure that we've done the right thing in terms of MSBuild docs. We need that checklist in an issue so we can finalize this.

I went ahead and took care of this in dotnet/msbuild#8543 since it was fairly straightforward to do.

Right, we just need to follow up on VS property page support.

[JamesNK]

Update other templates? webapi, grpc, worker?

Figure out how to test that culture is disabled. I'm not sure how to easily do this. The default template endpoints are returning invariant data already.

Responded to feedback

[Varorbc]

@eerhardt If enabled by default,SqlClient will throw an exception

[ghost]

Hi @Varorbc. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[eerhardt]

@eerhardt If enabled by default,SqlClient will throw an exception

The simple workaround in that case is to just remove this line from the .csproj then.

[ghost]

Hi @eerhardt. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[AlmightyLks]

FYI:
Breaks usage with EFC (Or SqlClient?) and thus makes ASP.NET Core 8 incompatible with EFC (/ SqlClient) by default

[ghost]

Hi @AlmightyLks. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[roji]

FYI this is purely a SqlClient-related issue that has nothing to do with EF per se.

[ghost]

Hi @roji. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.