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

ASP.NET Web Forms Integration in .NET Framework 4.7.2 #562

Open
amwins-fred opened this Issue May 30, 2018 · 5 comments

Comments

4 participants
@amwins-fred

amwins-fred commented May 30, 2018

How does the integration change for an Asp.Net Web Forms app targeting .Net 4.7.2 which includes support for DI?

@dotnetjunkie

This comment has been minimized.

Collaborator

dotnetjunkie commented May 30, 2018

Can you elaborate your question? I'm not sure I understand what it is you'd like to know.

@Kahbazi

This comment has been minimized.

Kahbazi commented Jun 10, 2018

.Net Framework 4.7.2 adds built-in support for Dependency Injection for Web Forms.
https://blogs.msdn.microsoft.com/dotnet/2018/04/30/announcing-the-net-framework-4-7-2/

This feature enables the following:

  • Support setter-based, interface-based and constructor-based injection in web application project in Handler, Module, Page, User control and Custom control.
  • Support setter-based and interface-based injection in web site project in Handler, Module, Page, User controls and Custom controls.
  • Extensebility to support different dependency injection frameworks.

Do you have any plans to integrate simple injector for .Net 4.7.2 Web Forms?

@dotnetjunkie

This comment has been minimized.

Collaborator

dotnetjunkie commented Jun 10, 2018

We have no plans in creating an integration package a.t.m. You can build an adapter yourself as explained here: https://stackoverflow.com/a/50641383/264697

@dotnetjunkie dotnetjunkie changed the title from Asp.Net Web Forms Integration in .Net Framework 4.7.2 to ASP.NET Web Forms Integration in .NET Framework 4.7.2 Jun 10, 2018

@mason-mcglothlin

This comment has been minimized.

mason-mcglothlin commented Sep 11, 2018

@dotnetjunkie Any changes on the status of this request?

Although Microsoft may have screwed up the implementation details of this, it still seems like it'd be something worth supporting directly via an official package.

@dotnetjunkie

This comment has been minimized.

Collaborator

dotnetjunkie commented Sep 11, 2018

The status hasn't changed. We still have no plans a.t.m.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment