Hi Houssam,

Thanks for the great post. I have some comments and questions.

>- How well your framework fit into multi-tiered architecture?

I know web services is supported and I too would like to see better remoting support.

>
>- I think your framework could use a schema designer. First, I can be used to set some business rules at design time. Second, it can be used to generate business and data access classes accordingly, as well as a typed data set class. Third, it will be used to synchronize table structure with the database. Finally, it can be used to implement the appropriate code (SQL/programming) to handle an important but almost always ignored database design pattern: one-to-one relationships.
>

This might be easier once partial classes are available. Can you explain in an example how you use your one-to-one relationship? Maybe it is supported in another way?

>- It seems that you’ve based your entire security logic on the user interface. While I think it should be placed in the business components instead. A solution could be found in the schema designer I’d mentioned earlier. This schema builder should also be available to the end user at runtime. Besides allowing him to extend the schema or add additional business rules, it will also be used to set module-level, table-level, field-level and even record level security. Client-side business component should be able to determine user rights and enforce them. Controls and command buttons should also be able to render themselves accordingly.
>

Are you thinking of something that would generate the rules as attributes and then the UI controls would read these attributes from the business layer with reflection?

I think there should be role based security in the framework based on a GenericPrincipal. This is really a separate issue from enforcing busines rules.

>- Finally, we have a set of user interface components different than the ones that come with .net. To use them, we will have to sacrifice the code that comes build into your components. Wouldn’t it be better if you had implemented that code in a property provider class? I think this way we could easily write our own property handling code for each type of control.
>

I couldn't find anything on property provider. Are you talking about the PropertyDescriptor class?