Spring.Net Framework sunset? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 6 years ago.

Improve this question

I've been considering going back to the springframework for .net DI, but I just noticed that there hasn't been any recent development or announcements on their site. Can anyone confirm that they are still actively developing the .net version of the spring framework, or is the project dead?

I know this has been asked before (is spring.net being actively maintained/developed/documented?), but that was over 2 years ago. The last announcement on the site's homepage is from December 2012.

---

Some more evidence of it being dead:

1. The forums site is down, for how long I don't know
2. There is no spring.net project on the download page
3. The build has been failing on the jira site since May 2013

Answer 1

Have a look at the GitHub repo

there was a recent check-in (a few hours ago of this comment being posted) https://github.com/spring-projects/spring-net/commits/master

also gives you an idea to who is developing the library.

forum looks to be up and running.

however that said, the same question is being asked on the forum http://forum.springframework.net/showthread.php?10866-Current-state-of-the-Spring-NET-project

Answer 2

I can refer only to this part "I've been considering going back to the springframework for .net DI" . Definitely it is not worth to do that. There is a wide range of good DI frameworks in .NET. In comparison with them Spring.NET is outdated. Mainly because of XML based configuration. There is a subproject to provide XML-less configuration but it is not finished. It can't be compared even with Java's original Spring configuration.

That said I'm going to use Spring.Net even if it is abandoned project. This is because it has other goodies too:

• AOP integrated with DI;
• libraries to use DI easily, for example when using WCF or ASP.MVC;
• ADO.NET transactions handling; this allows us to write components which later can be configured to work within different transaction contexts even with drivers not supporting TransactionScope.

Answer 3

2.0 is GA finally. so it is still active.

https://github.com/spring-projects/spring-net/releases/tag/spring-net-2.0.0-GA