Written in dotnetnuke is about to usher in the 6 Era

Dotnetnuke is about to usher in its 6 era. The biggest change is undoubtedlyCodeFully converted to C. Long agoShaun Walker also writesArticleWhy don't we use C #. I finally made a difficult decision, even though I couldn't help the public. I don't know why.ThinkThe difference between VB. NET and C # Is that C #ProgramThe number of members is much higher than that of VB. NET, and the trend becomes more and more obvious over time. Therefore, dnn has to be transferred to attract more developers. I have always had this idea that the success of an open-source framework depends not only on how powerful its own functions are, but on whether it can provide a sound and scalable platform, to attract more developers. Only when more developers are available can their functions be expanded infinitely to meet the needs of more customers. The success of dnn is at the same time. To continue to succeed, we still need to build a platform in a down-to-earth manner. TransformationProgramming LanguageThat's why I think.

 

I have been dealing with dnn for many years, and I will not talk about the advantages. It is undoubtedly powerful and excellent. Let's talk about two shortcomings. We hope we can make some improvements in the 6 era. First of all, I think if dnn is used to build projects for customers, there are two kinds of customers that are more suitable. First, the requirement is not high, and it is satisfactory to basically meet the functional requirements. It is best for such customers to use dnn, so they can work together on a website with almost no development cost. The other is customers with strong DIY ideas. They like to add pages, add things, and change their skin. Dnn is also very suitable for such customers to fully satisfy their desire for DIY. However, dnn is afraid of encountering a type of user. They have high requirements, but their hands-on capabilities are not strong. Sometimes these user requirements on some interfaces lead to rewrite the code of many existing modules, so that the reusability of the modules is not high, which is very contrary to the original intention of dnn. In fact, these customers have not changed their functions, but only some interface adjustments. If dnn can provide a skin mechanism refined to the module, it can well meet such requirements. In this way, you can meet the diversified user interface requirements without modifying the program code. Secondly, the dnn front-end code is not concise, which is not conducive to front-end code optimization. Especially when the customer attaches great importance to front-end code and Seo, dnn cannot meet these requirements at all. Looking at the long viewstate, this may be a common problem with the Asp.net Web Forms Program. Will dnn switch to ASP. net mvc? Although the previous Shaun Walker I have also written an article saying that it will not be converted into MVC, .... Wait and see.

Finally, I would like to talk about the expectations of the dnn6 era. I think dnn needs to embed a similar app store function in the 6 era. It can complete the promotion, Introduction, purchase, one-click installation, upgrade reminder, and other functions of the module. Today, application stores are so popular that dnn will not keep pace with the times.