. NET 3.5 C # Building dynamic type Best practices

There are several reasons why you should build under. net3.5:

1. Win7 comes with. NET 3.5, users do not need to install

2. I'm using vs2008, I don't want to upgrade.

3. . NET 4.0 introduced keywords, but I think there are similar features under. NET 3.5

4. This is the basis for building ORM, Word, the ORM on the market is not good, I want to rebuild the wheel

5. Not at the moment.

The end result is this.

The property name is a string, and the property value is whatever type.

I wrote the ORM for two nights, the multi-table query generates a dynamic type list, which is mapped to multiple entity classes, and the amount of code in the presentation layer is minimal, making it easy for tools to generate.

My vision for ORM is as follows:

1. The basis of the additions and deletions to check, must be concise, convenient

2. Generating entity class tools

3. Automatic inspection of entity class

4. Auto-Generate WEBAPI tool with a lightweight console httpserver

5. Multi-Table Association retrieved data is automatically bound to multiple entity classes

6. Automatic Transaction processing

7. Output type (list<t>,datatable, XML, JSON)

8. Presentation Layer Helper--generate WinForm (based on DotNetBar), Web (based on Ligerui), phone (based on Ionic), this is my childhood dream

9. Supports common databases and provides data migration tools

10. Cross-platform .... It's a fashion trend.

11. The above integrates a set of ORM visualization tools

12. Pick out the features above that can be realized this year first yards up

. NET 3.5 C # Building dynamic type Best practices