I wish to join this project to help get it going again

[jeffreyschultz]

Like the title says, I would like to join the project and help get development started again. There is still a need for Spring.NET in the .NET ecosystem, and it's a shame to see this wonderful code base collect dust.

I have already forked the repo in GitHub, and am wondering what is the state of things that need to be worked? I have used both Spring.NET and Spring, so I have a bit of familiarity with them, which is good, but I have only recently started to poke around the source code.

Also, who is available to provide guidance on implementation decisions and deal with pull requests? Anyone?

[gergroen]

I am available to contribute. I have used Spring.NET for a while and like it a lot.
Maybe we can focus us on the ".NET Core support" #133
And create some documentation on the github wiki. For example a getting started guide with the config in code. Because i think a lot of users create there configuration in xml files instead of in code.

[jeffreyschultz]

At the moment I have included Core, AOP, Web, and Mvc5 into my solution and am attempting to work through a couple minor issues that I have encountered. I am maintaining the existing Spring.NET solution structure by storing it under a folder in my project tree, and am selectively referencing projects into the solution. I think this will go a long way with regards to testing integration with my application, while being able to debug issues that I encounter.

I will also be sure to push changes I make to my fork on GitHub.

Until I can get further direction on things to do this will have to do for now. I think there is a JIRA for this project over at Spring Source, so I will have to take a look at that, too.

[sbohlen]

I can assist in code review, accepting PRs related to the project, etc.

…

-Steve B.

On Oct 27, 2017 4:40 PM, "Jeffrey Schultz" ***@***.***> wrote: Reopened #144 <#144>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#144 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AALX4I-IJZHfZPL_umiHdAUCh4vGOafSks5swj-sgaJpZM4QJfhy> .

[cptully]

I am starting a new job at the moment using C#, ASP.Net and IIS. The current website I am responsible for is 8-10 years old and the new version of it will be in Wordpress. I need to look into whether Spring and Wordpress will work together. If they do or can then it will be in my best interests to help out on this project. Chris Tully, M.S., Java and .Net Developer and Image Analysis Expert t 240.475.9753 f 419.831.0527 | cptully@gmail.com Sent from my iPhone please excuse typos.

…

On Oct 27, 2017, at 4:46 PM, Steve Bohlen ***@***.***> wrote: I can assist in code review, accepting PRs related to the project, etc. -Steve B. On Oct 27, 2017 4:40 PM, "Jeffrey Schultz" ***@***.***> wrote: > Reopened #144 <#144>. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#144 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AALX4I-IJZHfZPL_umiHdAUCh4vGOafSks5swj-sgaJpZM4QJfhy> > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[lahma]

Maybe I'll try to invest some time too. As I've said earlier I have some branches collecting dust that should be completed in the way forward. At least converting from Rhino.Mocks to FakeItEasy will allow as cleaner road towards .NET Core.

[guryanovev]

Hey this sounds really exciting, "Spring.NET" was a synonym of "best practice" for me for about 10 years and it was a really hard decision to move to another IoC container. But we had to do it as Spring.NET really outdated. It would be great if you guys get project back to life. But if to talk about actual project tasks, Core support is cool, but honestly, there are a lot of other things that should be done to get Spring.NET back to track. For example, XML looks just ridiculous our days, no one would use it. Modern applications register dozens of dependencies and a preferred way is to do it in code (using lambdas) and to do it automatically everywhere, where it's possible. Also, I think supporting of ancient .NET versions is a road to nowhere as even MS abandoned them. I'm saying that because Spring tried to support .NET 1 and 2 for so long blocking usages of 3.5 features in core modules.

[jeffreyschultz]

I am one of those people that’s loves XML. Sorry, but I think XML really has a place in Spring.NET, and I would really like to see more support for generalized XML authoring and consumption.

That being said, any way of configuring a container should be nothing more than a source of configuration definitions. The XML config factory, or fluent configuration, shouldn’t be an intrinsic component of the container. Use what you need and leave the rest behind. As for me, not supporting XML is a no-go.

I think the reason that XML isn’t bigger in the .NET community is because suppor for it is kind of crappy, which means that you end up with crappy implementations that add more of a burden to developers and end consumers. I would like to see this change.

[lahma]

I've used both XML and code configuration and they both have their merits. My Msc work was about product lines and XML played key role when defining readable variation points. Now using CodeConfig mostly to wire things up. XML is not going away and I wonder how the current CodeConfig would not meet requirements. A fee more lines to write compared to some fluent interfaces or auto scanning, I prefer the explicit wiring via CodeConfig, no guesses what is being used.

[jeffreyschultz]

I have used both as well, but I feel that configuration stops being "configuration" once you write it in code. That's kind of the point of external declarative configuration schemes, there is already a lot of code to deal with, so the goal is to have a separate representation of it that is focused on the task at hand, configuration. I feel that Spring.NET provides a pretty good mechanism for accomplishing this, but it still leaves a lot of room for developers to muddle it, hence what everyone has experienced before when dealing with large amounts of declarative configuration. With that said, I do believe that you should have the option to use either, and that they should be able to be used together. There are some parts of applications configuration that I want left internal, which could accomplished by embedded the XML in the assembly, or using code config, but when thinking about it from an end-users perspective, there is some that I want to expose. I think a lot of these mechanisms are for the people that consume our products, rather than the ones that develop using them, even though the developers do benefit from them.

Now, besides the obvious steps that need to be taken to get this project back on track, such as ensuring unit tests correctly represent expected behavior and are passing, and establishing platforms that will be supported in the way forward (and how to better structure the project to support that), I think a little life needs to be injected into some of the public facing parts of this project, such as updating the website to announce a call for contributors, etc. Whatever we can do to wake people up needs to be done.

I also have some ideas for other Spring.NET initiatives. The way that I look at the Java version of Spring is that it provides a foundational framework for structuring your applications, while attempting to smooth over differences that are encountered when using the various application servers that are used, and then providing a lot of integrations using those same concepts that become available to your application out of the box. With Microsoft's divergence from a couple of frameworks for .NET that are pretty much the same in general, to now with several frameworks to choose from, each having their own caveats and restrictions on usage of accepted .NET features, there needs to be some middle ground project that provides a solid base to build off while minimizing effort required by developers to support as many targets as possible. That can be the new niche that Spring.NET aims to fill.

There have been so many new developments in the .NET ecosystem over the past few years that it can make your head spin. Now with the shift in efforts to self-host services within your own process, there could be an initiative to provide guidance and frameworks to support these developers. Spring.NET could become that set of abstractions and default implementations to ensure best practices are present from the beginning. I personally love OSGi and Apache Karaf, and would like to see something like those available for .NET. Yes, I know there are some aspects of .NET that make OSGi for .NET not completely feasible, but you could capitalize on the benefits while accounting for limitations in the platform.

Also, I think a few of things are extremely critical for the longevity of the project (those will be described later), and one of them is Project Alliances. Spring.NET should position itself as an integration platform where developers can opt-out of default implementations to integrate another project's implementation. Spring.NET should be more than just an IoC/DI framework. Yes, I know there are other projects, but the focal point has always been the container for me.

I think we should also evaluate where the Java Spring project has gone in relation to where Spring.NET currently is, and see if there is anything else that could be taken from that set of projects.

I am serious about this, and I hope that anyone interested in being a part of this would join me.

[jeffreyschultz]

I would also like to help move the .NET community towards an old idea, but what I think could be a new paradigm for .NET.

Composition is Configuration

Pretty self explanatory, but it shifts the perspective of how application configuration is handled. It should not be an after thought where classes grab needed values from AppSettings (ick!). An objects configuration should be a definition of that class for a particular instance, and that is addressed with composition.

[jeffreyschultz]

It looks like there is a lot of good stuff in JIRA, along with some Futures tasks. Are these still valid?

https://jira.spring.io/browse/SPRNET/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel

Is JIRA available for us to use? Or have ties been severed? I am not really sure how the current Spring.NET projects tie in with the original project that used to be available from the Spring Source site.

[jeffreyschultz]

As for porting to other platforms, would it be a better bet to aim for the .NET Standard targets, rather than .NET Core itself?

As an update, I have found a few issues while developing my prototypes for a new project we are working on at work, and will be creating corresponding issues to be worked. I have also updated my GitHub profile to show my email address, so that anybody interested can contact me directly and assist.

I think there is another effort to port to the .NET Standard 2.0 platform, called Summer, so I will also be reaching out to that developer in an attempt to combine our efforts if they are still interested.

[luizcarlosfaria]

Hi guys,

i've working with spring.net since ~2007/2008 and a really appreciate this project.
It's help-me do to more, and about that i have some special feelings about this projetct.

What i did

At september 26 i've started a independently and unpretentious port of Spring.Core and Spring.AOP to .NET Standard. This port is a success, i'm working with this port on production, using misc of code and xml configuration, AOP and some daily features as well.

The port that i did is based on 4 solid steps:

1 - New Projects

Create a new projects based on .NET Standard 2.0, copying all code files to new project mantaining the assembly name, namespaces.

2 - Switch and Adapt

Addind nuget packages for known dependencies and creating a fake classes to replace some behavior that not portable, like Common.Logging and System.Runtime.Remoting and System.Runtime.Remoting.Messaging. These fake classes was created to garantee that i don't add a new issues or mistakes during remove your utilization, instead that, i create a fake implementations to maintain codebase intact. The only not ported thing is registry32, that was removed.

3 - Tests

The third step is make tests working. About first and second step, i'm talking exclusively about the Spring.Core and Spring.AOP projects, without your test projects. At third step and this is a most dificult on this port, is make tests working fine and Rhino.Mocks has maked it mor dificult. I really had some dificults to mantain same contract, wrapping other framework to do that using NSubstitute. But, on my work plan, i'm still here.

4 - Growing up

The last continuous step is make this project live!
But, it's depend of have or not this talk. I'm waiting for that. I really don't planed create any fork, the mindset behind this work is prove that can be done. And if i'm done, and was done, that i can use on my projects, until the official version was released.
If this talk was not exists, i'will think about the for in a few months or never, it's depends.

what i will do

If anybody ask me about work on this project. My answer is yes! i Will be glad to contribute!
I'm in!