aspnet
Removing PubTernal Localization APIs
Summary
In order to better maintain the public API surface of ASP.NET Core we're removing some "PubTernal" (having the type be public, but in a namespace that implies an internal intent) APIs from Localization.
Version introduced
5.0.0-preview6
Old behavior
Microsoft.Extensions.Localization.Internal.AssemblyWrapperis publicMicrosoft.Extensions.Localization.Internal.IResourceStringProvideris publicMicrosoft.Extensions.Localization.ResourceManagerStringLocalizer.ctorwithAssemblyWrapperis publicMicrosoft.Extensions.Localization.ResourceManagerStringLocalizer.ctorwithIResourceStringProvideris public
New behavior
Microsoft.Extensions.Localization.Internal.AssemblyWrapperbecameMicrosoft.Extensions.Localization.AssemblyWrapperand is now internalMicrosoft.Extensions.Localization.Internal.IResourceStringProviderbecameMicrosoft.Extensions.Localization.Internal.IResourceStringProviderand is now internalMicrosoft.Extensions.Localization.ResourceManagerStringLocalizer.ctorwithAssemblyWrapperparameter is now internalMicrosoft.Extensions.Localization.ResourceManagerStringLocalizer.ctorwithIResourceStringProviderparameter is now internal
Reason for change
Explained more thoroughly here the decision was made to do away with "PubTernal" types. These changes are simply bringing more classes in line with that decision.
Recommended action
Applications which intentionally or accidentally took a dependency on these types should migrate away from them. Since the classes in question existed only as an extension point for our internal testing we believe that's an unlikely scenario, but if you try to do so and believe you have located a scenario which our public API allowed before this change but does not now please file an issue at https://github.com/dotnet/aspnetcore/issues
Category
ASP.NET
Affected APIs
Microsoft.Extensions.Localization.Internal.AssemblyWrapperMicrosoft.Extensions.Localization.Internal.IResourceStringProviderMicrosoft.Extensions.Localization.ResourceManagerStringLocalizer.ctor
See https://github.com/dotnet/aspnetcore/issues/22291 for discussion.
Issue metadata
- Issue type: breaking-change
