ASP vNext DI integration

[Tom Dietrich]

Are there plans to build capabilities within windsor to act as the DI
container for the new ASP vNext DI? Autofac is working on it:
http://alexmg.com/autofac-4-0-alpha-1-for-asp-net-5-0-beta-3/

[hammett]

I probably need to do a lot of catch up on these topics, but what's
the main selling point of asp vnext and what's the benefit of having
Windsor adapted to it?

I can only see myself investing time on this if it has immediate and
tangible benefits.

Post by Tom Dietrich
Are there plans to build capabilities within windsor to act as the DI
http://alexmg.com/autofac-4-0-alpha-1-for-asp-net-5-0-beta-3/
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/castle-project-devel.
For more options, visit https://groups.google.com/d/optout.

--
Cheers,
hammett
http://www.d-collab.com/
http://www.hammettblog.com/

[Tom Dietrich]

The new version is a huge departure. It now uses NPM and Bower for client
side packages, has json based configurations, uses a html-like tag syntax
for the Razor view engine, now uses the same controllers for both MVC and
WebAPI, and was developed with performance and modern development practices
in mind. The session context for example has been reduced from 30k to 2k.

Microsoft has built DI into the technology. It's not unity or mef, it's a
completely new DI container- however it is with a very simple container
with poor features. It can only do constructor injection, and can't do
constructor selection- any component with more than one public constructor
will cause errors. It doesn't support per web-request lifestyles. Here's a
blog about
it: http://blogs.msdn.com/b/webdev/archive/2014/06/17/dependency-injection-in-asp-net-vnext.aspx

Anyway, here's the gitub repo for the DI stuff
-> https://github.com/aspnet/DependencyInjection . As you can see, Autofac
and Ninject both have submitted alternate DI implementations for usage. I
think that all that needs to be done is for someone to write a windsor
based implementation of these abstractions
-> https://github.com/aspnet/DependencyInjection/tree/dev/src/Microsoft.Framework.DependencyInjection.Abstractions

Post by hammett
I probably need to do a lot of catch up on these topics, but what's
the main selling point of asp vnext and what's the benefit of having
Windsor adapted to it?
I can only see myself investing time on this if it has immediate and
tangible benefits.

Post by Tom Dietrich
Are there plans to build capabilities within windsor to act as the DI
http://alexmg.com/autofac-4-0-alpha-1-for-asp-net-5-0-beta-3/
--
You received this message because you are subscribed to the Google

Groups

Post by Tom Dietrich
"Castle Project Development List" group.
To unsubscribe from this group and stop receiving emails from it, send

an
<javascript:>.

Post by Tom Dietrich
Visit this group at http://groups.google.com/group/castle-project-devel.
For more options, visit https://groups.google.com/d/optout.

--
Cheers,
hammett
http://www.d-collab.com/
http://www.hammettblog.com/