Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DependencyInjection, DataProtection and Antiforgery extension classes have been renamed to avoid ambiguity #187

NTaylorMullen opened this issue May 27, 2016 · 1 comment


None yet
1 participant
Copy link

commented May 27, 2016


Format: Microsoft.AspNetCore.DataProtection.*

Package Old Type Name New Type Name
Abstractions DataProtectionExtensions DataProtectionCommonExtensions
Extensions DataProtectionExtensions DataProtectionAdvancedExtensions
Primary Package DataProtectionExtensions DataProtectionUtilityExtensions

Dependency Injection

Format: Microsoft.Extensions.DependencyInjection.*

Package Old Type Name New Type Name
Abstractions Extensions.ServiceCollectionExtensions ServiceCollectionDescriptorExtensions
Abstractions ServiceCollectionExtensions ServiceCollectionServiceExtensions
Abstractions ServiceProviderExtensions ServiceProviderServiceExtensions
Primary Package ServiceCollectionExtensions ServiceCollectionContainerBuilderExtensions


Microsoft.Extensions.DependencyInjection.ServiceCollectionExtensions => Microsoft.Extensions.DependencyInjection.AntiforgeryServiceCollectionExtensions

@NTaylorMullen NTaylorMullen added this to the 1.0.0 milestone May 27, 2016

@aspnet aspnet locked and limited conversation to collaborators May 27, 2016


This comment has been minimized.

Copy link
Member Author

commented May 27, 2016

DependencyInjection Discussion: aspnet/DependencyInjection#412
DataProtection Discussion: aspnet/DataProtection#150
Antiforgery Discussion: aspnet/Antiforgery#86

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.