public class ContextStorage
{

[ThreadStatic]
private static Dictionary threadContext = new Dictionary();

public static bool IsWebContext()
{
try
{
return (HttpContext.Current != null);
}
catch (HttpException) { }
return false;
}

public static IDictionary Items
{
get
{
return IsWebContext() ? HttpContext.Current.Items : threadContext;
}
}

}

i.e. Child.ForName(“subscriber”) roughly equates to “give me child of the one named subscriber (SubscriberInfo?)

Are Child.ForName, .Eq, Attrib.ForName MicroKernel Registration API extension methods?

Sorry about the dumb questions. I am deciding on IoC containers and evaluating code-based configuration paradigms. I think I understand how to leverage your approach on down the road – I thought I might as well poke the unknowns. I am also a little linq-naive.

Just few a questions in regard to the class encapsulation where Subscriber encapsulates SubscriberInfo. I typically warn myself off of usage like this because I don’t understand the qualities.

Is this implementation:
a) a pattern of which I am unaware
b) Does it afford quality to the container or the fluency framework?
c)?

Thanks, Brad

Component.For()
.ImplementedBy () .Subscribers(Subscriber.ForComponent (“subscriberId”,(x, y) => x.ServiceStarted += y.Subscriber));

This is possible since I’m using lambda’s as delegates. I think i can process it to get the right stuff: which subscribed to what but this ForComponent part disturbs me as it is not necessary.

Standard = non touch screen device (with cellphone)
Professional = touch screen device (with cellphone)
Classic = touch screen device (without cellphone).

The two SDKs essentially deal with issues caused by the presence (or lack of) a touchscreen. As an example the .NET CF does not support use of the standard Button control while building an application for a Windows Mobile standard device (how would the user click it?). Even a simple multiline textbox operates differently on the two types of devices.

Over time the platforms do appear to be getting closer to each other and features have migrated between them with each major release. For example the current XML based CAB file format used by Pocket PC devices was originally a Smartphone only feature.

I do agree with your comments about some of the “value added” .NET CF components (CameraCaptureDialog etc) however. Quite often they have poor consistancy across devices and leave a lot of functionality present in the native versions of the APIs inaccessable.