Delete our own log files from IsoStorage to make room when possible or silently stop logging. There should be neglectable to no impact on the client perf.

I want to specify different caching storages with their own settings: cache size (in bytes, #entries), compression, others?

I want to specify how log messages are formatted via tokens. I want to be able to reuse my formatters.

I want to be able to add tracing to my application, that can be turned on or off using configuration I also want to be able to configure which tracelisteners receive my trace messages.

When logging, a maximum size of the log information can be set, and when that size is reached older log information will be deleted to keep the log within the set sized.

I want to log from my Silverlight app to various destinations, which are externally configurable

I want to be able to control how long data should be cached for and when it should be purged. There are several settings I like to use, such as: absolute time, sliding time (how long since the last access ), extended time format, dependencies (if a dependency is changed, the item in cache automatically expires) or never expires (see http://msdn.microsoft.com/en-us/library/ff664596(PandP.50).aspx). I also want to specify a priority, so that lower priority items are purged first. Implement an LRU algorithm (Least Recently Used: discard the least recently used items first).

I want programmatic config via fluent interface for all the blocks.

I want to cache application-wide data once and reuse it across different Silverlight sessions. In these situations, it can be helpful to store this data in isolated storage. This way, my data is persisted when the application is closed and can improve startup time. This can also help in occasionally-connected scenarios.

For applications that use a large amount of reference data, I want to preemptively fill the caches with reference data (on a background thread of course), to speed up the user experience.

I want my validation logic to be composable. I want to combine validation rules using Boolean logic (AND/OR/NOT clauses)

A type interceptor. It uses dynamic code generation to create a derived class that is instantiated instead of the original intercepted class, and to hook up the behaviors.

An instance interceptor. Uses dynamic code generation to create the proxy class.

Transparent data access regardless if this data will only be stored in memory or will be stored in isolated storage. Especially for OOB & Offline scenarios.

I want to have a comprehensive built-in library of common primitive validation rules. See the list of existing EntLib validators at http://msdn.microsoft.com/en-us/library/ff664694(PandP.50).aspx

I want to allow for cross validation (e.g. either Name or CompanyName can be null but not both).

I want to specify validation by placing attributes on my objects.

I want an easy way to compose validators programmatically, via a fluent interface with IntelliSense support.

I want to specify validation rules in configuration separate from the object that's being validated. This will help me to maintain my validation rules during development and after deployment.

I want my validation logic to be composable. I want to combine validation rules on type members