Error analysis Summary for. NET developers-practical tips

1. Think you have to use Visual Studio.NET to develop. NET Applications
Those to Microsoft. NET development people are mistaken: Visual Studio.NET must be used to develop application software using the. NET framework. This is not true. You only need to install the free download on the Microsoft website. NET Framework.

installed. NET Framework, you can apply your favorite text editor and. NET tool command line for development. Also, you can apply third-party development tools, such as SharpDevelop.

For a thorough understanding of the discussion of Visual Studio.NET, see previous columns. The choice of development tools varies from person to person, but many development teams standardize to simplify their work.

2. Exclusive information
One of the salient features of developers is that they tend to be secret information. Xiao Man's ability often leads to false superiority. On the contrary, sharing information helps the team to expand their knowledge. In addition, sharing information can be improved as other team members join. Finally, when you explain an idea or idea to another or a group of developers, your knowledge expands.

Team spirit is the driving force of the agile Software Development movement. In addition, many teams use peer code evaluation (peer code reviews), where developers review and comment on the code of other developers, which facilitates both learning and understanding.

3. Ignore code comments
It's a simple and straightforward way to annotate your code, but why do people always ignore it? Some developers mistakenly believe that reducing documentation (in any form) can improve job security. This is as much a fallacy as the exclusive information discussed earlier.

A small amount of properly arranged annotations can greatly improve the readability of your code and facilitate the management of your code. Now there is a tendency to use annotations too much. Basically, these comments should be briefly described in terms of code, variables, methods, and so on. Many teams like to insert comments when they make changes to the code. When there is a problem, it is easy to find out what changes have been made before.

4. Not seeing the value of the version control system
Most developers are familiar with the situation: you launch a new version of an important Web application, and the next morning your phone rings and it's full of web problems.

As long as you are willing to admit that you may have made one or two mistakes, in this case the version control system is your best friend. By using version control systems such as CVS, IBM Rational ClearCase, and Microsoft Visual SourceSafe, you can easily revert to a previous version of your application and produce it. This gives you time to find the problem in the development environment when the production site is ready. This approach is far superior to finding the problem by searching the production code.

In addition, the source control system allows different team members to develop the same code at the same time. These changes are combined when a developer examines changes made to the system.

One reason some developers dislike versioning systems is because it adds a step to the development process, which means that the process of submitting code to the source control system and recovering the code through it slows down. This extra waiting time has hit some developers ' patience.

5. Think all projects need network services
Due to the excessive publicity of network services, many developers believe that a network service must be used in some form when developing projects. Although it may be necessary or appropriate to use Web services during the development process, it is not entirely possible. You need to analyze different situations to determine whether it is appropriate to perform a network service. For example, using remoting may be more appropriate.

6. Ignoring the importance of identifying data
In the application code, the data is processed in different forms. For this reason, developers should identify the integrity and effectiveness of the data during the development process. This means that the data is read through a terminal database that can return 0 characters. The data is checked before it is executed because 0 values are not available in most operations.

Understanding is half the success
Whether you're developing a new recruit or a veteran, you have to realize that developers have a tendency to make these six mistakes. Even if you find yourself without these bad habits, be aware that other developers on your team may make these mistakes. Be wary of these potential mistakes, and do so to prevent these mistakes from hindering your team's plans.