IoC in C#...is it worth it?

[Guest]

Hi folks

I come from the Java World, where Springframework has finally became the
defacto standard for new architectures. For several reasons I am back to the
Microsoft world, and new to VS.Net, and I find a pretty cool environment
where *almost* everything is solved (at least I haven't heard of Struts.Net
yet ). ORM is promissed to be included on ADO.NET 3.5, the debugger is so
cool that you don't miss log4j, etc. I am wondering if design patterns like
Template Factory, Data Access Object, IoC, etc, make sense for the *regular*
C# developer. Am I wasting my time trying to teach design patterns to my
programmers? is it worth the effort? Does Spring.Net add value to the .Net
food chain?

I would like to listen to your thoughts.
Best regards

 

[Guest]

I come from the Java World, where Springframework has finally became the
defacto standard for new architectures. For several reasons I am back to the
Microsoft world, and new to VS.Net, and I find a pretty cool environment
where *almost* everything is solved (at least I haven't heard of Struts.Net
yet ). ORM is promissed to be included on ADO.NET 3.5, the debugger is so
cool that you don't miss log4j, etc. I am wondering if design patterns like
Template Factory, Data Access Object, IoC, etc, make sense for the *regular*
C# developer. Am I wasting my time trying to teach design patterns to my
programmers? is it worth the effort? Does Spring.Net add value to the .Net
food chain?

I would not call Spring a defacto standard for architecture. It is not
even as hyped as it was 2 years ago. Today it is just a frequently
used tool among many other tools.

I would say that Spring is just as useful in C# as in Java. It is
not particular language or library specific. And at least in 2.0/3.0
I don't see much overlap with .NET itself.

An alternative to Spring.NET would be
http://www.castleproject.org/castle/index.html !

Arne

 

[Ben Voigt [C++ MVP]]

Hi folks

I come from the Java World, where Springframework has finally became the
defacto standard for new architectures. For several reasons I am back to
the
Microsoft world, and new to VS.Net, and I find a pretty cool environment
where *almost* everything is solved (at least I haven't heard of
Struts.Net
yet ). ORM is promissed to be included on ADO.NET 3.5, the debugger is
so
cool that you don't miss log4j, etc. I am wondering if design patterns
like
Template Factory, Data Access Object, IoC, etc, make sense for the
*regular*
C# developer. Am I wasting my time trying to teach design patterns to my
programmers? is it worth the effort? Does Spring.Net add value to the .Net
food chain?

Design patterns such as "inversion of control" are important to any project
of non-trivial size.