A set of solutions under dotNet, dotNet Solution
I haven't written an article in the blog garden for a long time. I plan to open up a whole set of systems that I have been writing by myself. Today I will first release some addresses that can be demonstrated!
This system contains the data layer (HB. data), scheduled tasks (HB. planTask), log system (HB. log), template System (HB. templateEngine), Url rewriting (HB. urlRewriter), api (HB. apiControls.
Why write data layer? Isn't there a lot of ready-made ORM? Why do I have to write it myself? Many years ago, there was no ORM in dotNet, and many things could only be written by themselves, so the data layer feature became more and more powerful,
You can use entity classes to generate tables in the database, or tables in the database to generate databases, and support multi-medium databases, such as SQL Server, Access, Sqlite, Oracle, and MySql. The data layer has a common addition, deletion, modification, and query method, and supports parameterized writing. The entity class also supports expression writing (Note: The expression writing method is not complete at the moment )!
The main improvement of Url rewriting is the support for configuring domain names and rewriting rules through databases, and the support for multi-domain names. For example, I only bought one space, but I have several websites. This function enables multiple websites in one space! You can try www.8fdc.com, www.54rm.com, and www.5wshop.com. The results are different. Because the path is rewritten, www.8fdc.com is actually under 8fdc.com/www/, and so on, of course, this can be configured through the database.
The api function automatically matches parameters and writes methods directly in the background class to access them in the form of/api/class name prefix/method name. ashx.
First, let's take a look at the images of the entire system, and open the website background demo address at the end!
Background address: http://www.8fdc.com/admin/login.ashx
Account: test password: 123456