ASP.NET 5 - It's Basically Java

Minimalistic DI

The integration of a minimalistic dependency injection (DI) system in ASP.NET 5 marks a significant shift towards better software design practices. Alan Underwood highlights how DI is now a core component of the environment, promoting separation of concerns and enhancing testing capabilities 1. While some argue about potential performance hits due to object instantiation, Alan believes that DI's inclusion is beneficial for ASP.NET applications.

Dependency injection in general is not a bad practice, let's put it that way. And the fact that it's now wired in, as, you know, a core component to your ASP.NET 5, you know, app, I think is a good thing.

--- Alan Underwood

The system's simplicity allows developers to swap in other DI containers like Ninja X, making it versatile and adaptable to various project needs 1.

   

NuGet & Package Mgmt

ASP.NET 5 introduces a refined approach to package management with NuGet, streamlining the inclusion of necessary components. Alan Underwood explains that developers can now include only the packages they need, reducing bloat and improving application performance 2. This modular approach aligns with the trend towards a more "dockerfied" future, where applications are lightweight and self-contained.

You can update each application independently as needed.

--- Alan Underwood

Additionally, the Roslyn compiler enhances the build process by compiling multiple versions simultaneously, ensuring compatibility across different runtimes 3. This flexibility allows developers to maintain specific dependencies for full CLR or core CLR, optimizing their applications for various environments.