Where will Castle go in the "New. Net Era"? DOTNET channel)

In China. NET developers believe that castle is no stranger. Castle is targeted. A very good open-source project under the. NET platform, from the data access framework ORM to the dependency injection container, to the Web layer MVC Framework, AOP, it basically includes everything in the entire development process, allowing us to quickly build enterprise-level applications. Program Provides good services. After several years and three RC versions, Castle finally wants to release version 1.0.

The author has been studying the castle project for a long time and has written a lotArticle. However, with the advent of Microsoft. The arrival of the Net Era, the castle project will face some embarrassment. How to find your own position and how to develop in the future is a question that the castle project author has to consider.

1. Data Access activerecord

Activerecord in Castle is a lightweight ORM Component, which encapsulates nhib.pdf. nhib.pdf at the underlying layer is based on. Net, used for Object Persistence class libraries of relational databases. It is famous for hibernate. . Net version. The xml configuration file is used to map the relationship. In activerecord, this method is further encapsulated and mapped using the attribute method. With Microsoft. Net Framework 3.5 launched its own lightweight ORM--LINQ to SQL, activerecord situation has become a bit embarrassing, although some people will say that the current only SQL Server is supported by LINQ to SQL, yes, however, we can see the strong scalability of LINQ. Now, the interfaces of LINQ to the Oracle database are open, so this will be solved in the near future, when Microsoft's physical framework was released, it was okay to support the Oracle database's LINQ.

 2. MVC Framework monorail

In 3.5, Microsoft released the first CTP version of ASP. NET Extentions, the most notable of which was ASP. net mvc Framework. Before that, monorail in castle could be said to be. NET platform, the most famous MVC framework. Because ASP. net mvc framework appears, in. The net development community has aroused a discussion such as "Why the MVC framework under ASP. NET platform" and "The Future of Monorail in the ms mvc Framework vortex. Indeed, after Microsoft ASP. net mvc Framework, monorail is in a dilemma. Hamilton also said, "How the final result of monorail 2.0 depends on the implementation of the ms mvc framework. If the final Ms MVC is great and provides many functions, I will consider giving up monorail 2. 0. if the final version of Ms MVC is not so perfect and the necessary functions are missing, monorail 2.0 can reuse the basic architecture of Ms MVC to provide some valuable extensions ". But there is no doubt that the number of viewers owned by ASP. net mvc framework cannot be reached by monorail?

3. Dependency injection container Windsor container

Windsor iner plays an important role in Castle. I believe many of my friends have started learning about it. With its good design and concise configuration, Windsor container soon won the reputation of developers. Just as castle has passed three RC versions and is about to release the official version 1.0, the Microsoft mode and practice team published the Development Plan for Microsoft dependency injection container in its team blog, named "Unity, the other eight application blocks will be transplanted to unity. This is undoubtedly a blue ray for Castle. Although in the Current Unity CTP version released by the mode and practice teams, we can see that its design is still very ugly, such as constructor injection and attribute injection. However, we have to admit that as long as it is a product officially released by Microsoft,. NET developers will use it, and the level of support is far greater than that of open-source projects.

4. Conclusion

In a short time, Castle will release version 1.0. net MVC Framework, unity, and other products, Castle can find its own way out. What kind of surprises will it bring to us in the new version, let's wait and see.