I can only refer to this part of "I was thinking about returning to the spring calendar for .net DI." Definitely not worth it. There is a wide range of good DI frameworks in .NET. Compared to them, Spring.NET is deprecated. Mainly due to XML-based configuration. There is a subproject for providing configuration without XML, but it is not finished yet. It cannot be compared even with the original Spring Java configuration.
This suggests that I will use Spring.Net, even if it is an abandoned project. This is because he has other goodies:
- AOP is integrated with DI;
- libraries are easy to use DI, for example, when using WCF or ASP.MVC;
- Transaction Processing ADO.NET; this allows us to write components that can later be configured to work in different transaction contexts, even with drivers that do not support TransactionScope.
robsosno
source share