[Podcast] How to structure .NET Solutions and Components

Ask Udi Podcast – Udi Dahan – The Software Simplist

This week’s question comes from Mike who asks:

Hi Udi,

I was wondering if you could help me out or point me in the right direction. I’ve been programming on the .Net framework for several years now and want to move towards an architecture role. Additionally, I have been reading up on WCF and related .Net 3.0 technologies, but have more questions than answers.

1. Do you have guidelines/best-practices for how to structure a .Net solution and related assemblies? Also, guidelines as to how to factor the various namespaces and what goes where would be helpful.

2. How should components be factored, i.e. one component to an assembly or multiple components to an assembly? I’ve read several different articles that go back and forth, but never really got a straight answer.

3. How do components relate to services from an SOA perspective?

4. Does application scope/size impact the decision to use SOA? And,

5. Do you have any resources that I could use to learn more about SOA and .Net?

I appreciate the help and any answers that you can provide.

Mike

Get it via the Dr. Dobb’s sitehere.

Or download directly here.

Additional References

• On the importance of splitting up projects and DLLs
• Inversion of Control Containers and the Dependency Injection pattern

Dependency Injection Tools:

• [.NET] Spring Framework
• [.NET] StructureMap
• [Java] Spring Framework

Podcasts:

• Podcast on Autonomous Services and Pub/Sub
• Podcast on Business and Autonomous Components in SOA

Want more? Go to the “Ask Udi” archives.