3

I have a theoretical question about the .net framework.

As I see it Microsoft gave us bunch of technologies for different layers.

We have the ADO.NET and with the more improved Entity Framework for Data Access.

And ASP.NET for WEB UI. And even WCF for Facade and SOA.

But what in the middle, what do we have for the Business Layer? Is it just Referenced DLLs?

How do we deal with the Application Pooling this days? I remember using COM+ 10 yeas ago because the IIS couldn't handle the pressure.

Is Spring.Net is the best option available for injection?

Thanks, Ronny

Ronny
  • 2,399
  • 3
  • 20
  • 27
  • 6
    What exactly are you asking? – SLaks Apr 25 '10 at 21:09
  • The bottom line, I'm asking that tools, methodology and technology is most suitable for separating the Business Logic layer – Ronny Apr 25 '10 at 21:17
  • For "separating logic", how about assemblies > namespaces > classes? What kind of tools are you looking for to help separating logic? – Jørn Schou-Rode Apr 25 '10 at 21:19
  • Sure, but then as I wrote, just referenced DLLs and not a designated technology for dealing with common issues as pooling and injection – Ronny Apr 25 '10 at 21:22
  • If you looking for dependency injection tools, have a look here also: http://stackoverflow.com/questions/148908/which-dependency-injection-tool-should-i-use – Jørn Schou-Rode Apr 25 '10 at 21:27
  • BTW, does the AppFabric server addresses some of the issues? – Ronny Apr 25 '10 at 21:56

1 Answers1

5

For dependency injection, you can use the Unity Application Block from Microsoft Patterns & Practices.

You can also use the Managed Extensibility Framework.

EDIT: You might be looking for the entire patterns & practices group.

SLaks
  • 868,454
  • 176
  • 1,908
  • 1,964