You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Pubternal" APIs in ASP.NET Core have been removed
In order to better maintain the public API surface of ASP.NET Core, we've moved a large majority of the types in the *.Internal namespace (previously we used the term "pubternal" to refer to these) to be truly internal. Members in these namespaces were always in a gray area. They were never meant to be supported as public APIs and could break in minor releases (and often did). We've moved away from pubternal for a large majority of APIs (there are still a few edge cases) an as a result, code that used to depend on these APIs will be broken when moving to 3.0.
Previously, these APIs were public, but in namespaces with the Internal in the name.
New behavior
These APIs are now internal and can no longer be used.
Reason for change
The guidance for these "pubternal" APIs was that they could change without notice and were not subject to our policies to prevent breaking changes. In 3.0 we determined that leaving them public (even in the Internal namespaces) was still confusing to customers.
"Pubternal" APIs in ASP.NET Core have been removed
In order to better maintain the public API surface of ASP.NET Core, we've moved a large majority of the types in the *.Internal namespace (previously we used the term "pubternal" to refer to these) to be truly internal. Members in these namespaces were always in a gray area. They were never meant to be supported as public APIs and could break in minor releases (and often did). We've moved away from pubternal for a large majority of APIs (there are still a few edge cases) an as a result, code that used to depend on these APIs will be broken when moving to 3.0.
See these issues for more details:
Version introduced
3.0
Old behavior
Previously, these APIs were
public
, but in namespaces with theInternal
in the name.New behavior
These APIs are now
internal
and can no longer be used.Reason for change
The guidance for these "pubternal" APIs was that they could change without notice and were not subject to our policies to prevent breaking changes. In 3.0 we determined that leaving them public (even in the
Internal
namespaces) was still confusing to customers.Recommended action
Discontinue use of these APIs. If you have questions about alternate APIs, feel free to file issues at https://github.com/aspnet/AspNetCore
Category
Affected APIs
All APIs in namespaces under
Microsoft.AspNetCore
orMicrosoft.Extensions
which have anInternal
segment in the namespace name. For example:Issue metadata
The text was updated successfully, but these errors were encountered: