News

First Release of Spring.NET Now Available

Interface 21 bows Spring.NET 1.1, a dev-deployment framework for .NET apps.

Interface21 Ltd., the company behind the open source Spring application framework, has announced the first milestone release of Spring.NET. The 1.1 version of this Spring-based framework for enterprise .NET development comes with nearly 100 bug fixes and an expanded feature set.

With Spring.NET, Interface21 is seeking to extend the core concepts that have made Spring one the most popular application frameworks among Java developers-things such as dependency injection, aspect-oriented programming and the data access framework-to the .NET environment. Spring.NET also comes with features specific to the .NET domain, such as support for, and extension of, ASP.NET.

"While some of the features of Spring Java are unique to the Java platform, overwhelmingly, the best practices that are baked into the framework and the Spring programming model are completely applicable to .NET," says Mark Pollack, principal consultant at Interface21 and the Spring.NET project lead.

Adoption Issues
But will .NET developers, who tend to look to Microsoft for guidance, really add an app-dev framework from the Java world to their toolboxes? Forrester Research Inc. analyst Michael Goulde says they will-eventually.

"Many companies are doing both Java and .NET development-it's almost never one or the other," Goulde says. "And the two groups aren't enemies. They look over each other's shoulders all the time. So, to the extent that Spring is helpful to them, I think .NET developers will be giving it a try."

That's what led Pollack, who's one of the original Spring Java committers in the area of messaging middleware, to begin developing a port for .NET in 2003. At the time, he was working in a startup company whose product had a Java back-end and a .NET front-end. "I had architected most of the back-end, but no one in the company had a lot of front-end experience, and so I just kind of dived in," he says. "Right away I thought, wouldn't it be nice if I could do things the way I'd done before, in terms of the programming model?"

No .NET Stampede
Gartner Research analyst Thomas Murphy agrees that Spring.NET is likely to be adopted primarily by enterprises with both Java and .NET environments-but don't expect a stampede from the .NET camp.

"Spring.NET can provide increased developer velocity, and I wouldn't argue that it's invaluable," Murphy says. "But much of the Microsoft development audience sticks more closely to the frameworks that Microsoft provides."
Download Spring.NET at http://www.springframework.net.

About the Author

John K. Waters is the editor in chief of a number of Converge360.com sites, with a focus on high-end development, AI and future tech. He's been writing about cutting-edge technologies and culture of Silicon Valley for more than two decades, and he's written more than a dozen books. He also co-scripted the documentary film Silicon Valley: A 100 Year Renaissance, which aired on PBS.  He can be reached at [email protected].

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube