ASP. NET MVC Website Development Summary (iv)--Alumni Platform Development Summary

After one months of efforts, the school's alumni platform project is nearing the end of the beta, a simple summary of the project development.

Compared with the last time to do wingstudio Studio portal site, the same team development, the number of people involved in a more than one months, but from the overall situation, this time than the last to do a lot better (whether the page style or the background of the modular package), this is progress is inevitable, This time the task is still responsible for backstage and backstage and the front desk splicing.

In general, the efficiency of developing a Web site with ASP. NET MVC is quite high (and quite good deployment), especially for background development, as long as the function analysis of the page is in place, The design of the database and the initial implementation of the background code (background and foreground can not be synchronized, this is the charm of MVC development). And all the backstage functions of this alumni platform (including database design and all logic control in the background) only used for a week, and the most time spent is still the background and the front desk splicing (after all, is a lot of people write, integration is a bit troublesome), used for more than 10 days, and then spent more than a week to improve and improve continuously.

Summary of Competency Enhancement:

(1), the biggest harvest of this development should be to contact and master the use of Ajax and json , learned to use JSON to carry forward and backward data transfer, with Ajax Solve the local refresh problem and the asynchronous loading of data (especially the loading of the picture, if a one-time loading of multiple images, the site will be very card (Studio portal Home is the case-the problem will be solved), so this time can consider using Ajax To implement data caching and asynchronous loading).

(2), because did a lot of page splicing, so contact the foreground of things can not be less, this time also further in-depth understanding of JS,jQuery,html,CSS.

(3), also learned several front-desk components use (waterfall flow picture Automatic layout components and Prettyphoto components) and combined use. (There may be a lot of people in the front-end development of the site will be offensive or unwilling to use components, think that the use of other people have written components of their own ability to improve not much help.) Personal Insight: The use of components is not only a great improvement in the efficiency of web site development, but also makes the site look taller. And most think that the use of components does not have much ability to improve, because he/they simply call the interface function (which is also a corollary to the high package of components) on the implementation of the big function, the internal implementation is completely unknown. And most of the time, because of the changing requirements, some functions do not simply call the interface function can be a good implementation of the requirements, then you need to modify the component internal function implementation (However, many people in this step to give up or use another component), to customize their functional requirements, if you can do this, Both the mastery of the components and the improvement of their abilities are of great help. One of my own way of learning: not, to study, to learn, to imitate, and then to form their own things. )

(4), further master the front page frame modification.

(5), (for different browsers and different versions of the same browser) has a further understanding of page compatibility, not only the label, style, property compatibility issues, as well as JS will also appear some compatibility issues. If this problem is not taken into account in advance, it is quite a headache to change it later.

(6), the use of ASP. NET MVC Framework to develop the site has a further understanding and grasp, the efficiency of development further improved.

(7), the security of the check (the form of legal validation, etc.) has been better used, triple authentication: the label itself attribute limit verification,JS authentication, background data validation. (Simply put: all the front-end verification can be bypassed (tag itself attribute limit verification,JS authentication), so the most important is the background data validation, but in order to obtain a better user experience and efficiency, front-end verification is also very necessary. Asp. NET is a little bit more secure, which is by default filtering out a lot of illegal tag injections, which greatly reduces the burden on the backend developers.

In general, the team to develop Web projects, for their own foreground and back-office capabilities have varying degrees of improvement.

The next few blogs will discuss in detail some specific examples of the implementation of the function. (such as the use of Ajax and Json , etc.)

< my blog homepage;:http://www.cnblogs.com/forcheng/

ASP. NET MVC Website Development Summary (iv)--Alumni Platform Development Summary