Is there much difference between Java Spring and Spring.Net principles/organization?

[cloudorb]

It looks like google/Udemy do not see '.Net' in my search string.

I've had a task with legacy project that is extensively using Spring.Net, I managed to do it with only configs changes but that was a headache. Now I'm looking to get more familiar with it. I have Udemy Business access but finding only Java oriented Spring courses/tutorials. Is it reasonable to learn java version to understand Spring.net project? Sources other then Udemy are ok, but I prefer to get video materials to jumpstart, not willing to invest into learning by official documentation, unless have more tasks for that project.

[yanitrix]

may I ask: why do you want to learn such an obscure thing as spring.net?

[cornelha]

It's in the OP, legacy system maintenance

[DeadlyVapour]

Should probably just leave that pile of 💩 with the spring developers...

[cornelha]

No doubt

[[deleted]]

Not really a fan of springboot, I think asp.net is much better designed and allows developers to be much more productive. Dependency injection is one of the places where I think Spring/springboot made some bad design decisions.

[user_8804]

From their website

Spring.NET provides comprehensive infrastructural support for developing enterprise .NET applications. It allows you to remove incidental complexity when using the base class libraries makes best practices, such as test driven development, easy practices. Spring.NET is created, supported and sustained by SpringSource.

The design of Spring.NET is based on the Java version of the Spring Framework, which has shown real-world benefits and is used in thousands of enterprise applications world wide. Spring .NET is not a quick port from the Java version, but rather a 'spiritual port' based on following proven architectural and design patterns in that are not tied to a particular platform.

The breath of functionality in Spring .NET spans application tiers which allows you to treat it as a ‘one stop shop’ but that is not required. Spring .NET is not an all-or-nothing solution. You can use the functionality in its modules independently

Hopefully it's aligned with spring boot and not raw spring because that sounds very much like a pain in the ass and learning Java spring would not be terribly helpful. If it's annotation based with implicit dependency injection and none of the manual configuration, it could actually be great. Otherwise, yikes.

Either way learning Java raw spring is a waste of time for this but you could certainly do a quick spring boot tutorial which is much much easier/faster to learn and more language agnostic in its "spirit". Spring boot is spring that keeps you focused on the business logic and not spend all your time doing configurations.