Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Web Development

How to Structure .NET Solutions and Components


This week's podcast answers some recent questions emailed from a reader:

Hi Udi,


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


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


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.