Write high-quality code to improve the C # program's 157 suggestions-Navigation opening

Due to the recent shift of focus, projects originally developed with several colleagues have also been launched, and new projects are optimized, extended, and expanded on the basis of existing projects. For example, the Web management website of the project administrative cases that have already been launched (the code is not so many-Phase Comparison of criminal cases to be done ), the new project is a Web management website for criminal cases, and the two websites, administrative and criminal, should be merged. Some time ago, my discussions with my colleagues and superiors resulted in the creation of a new project, the re-encapsulation, optimization, and expansion of various components of the original system, and the development of the website for criminal cases first, after criminal cases are developed, the original project will be re-integrated according to the ideas of criminal cases.

Recently, when I started viewing the old code, I found too many problems, and I felt like I couldn't help it. Some things were just implementing functions at the time, because I still had a limited experience and experience. So I plan to study this book. I have discovered this book. Haha, I feel very good, so I want to take a note here.

The author of this book also has a clear record. The author has been thinking about the question: what kind of programming books can help beginners quickly advance? The so-called "author" refers to people who can use a language to write programs but do not quite understand how to write high-quality code. The author recalled the early stages of his development career and found that at that time, he was often troubled by the following three types of problems.

　　The first type comes from the language itself.

1. How to format strings is the most efficient?

2. How is the most efficient conversion between basic types or other CLR types?

3. What is the difference between for and foreach? When should I use for and when should I use foreach?

4. What is the Dispose mode? Why are resources released? How are resources released?

5. How should I enable and end multithreading, why should I synchronize threads, how can I synchronize resources, and how can I lock resources?

　　The second type comes from the design framework.,If you are passionate about programming, I believe your brain will soon be filled with the following questions::

1. Why do I still need the singleton mode when I use the singleton mode or static class?

2. What are the essential differences between static methods and instance methods?

3. How to use an exception is the most correct. When to throw an exception, when to "eat" the exception, and why to customize the exception?

4. How can I avoid judging branches with too many conditions?

5. How to Ensure program data security and communication security?

　　The third type of problem is the most common, probably from coding habits and programming ideas.

1. Is it better for a file to contain only one class, or can a file contain multiple classes?

2. How to name a professional?

3. Should I use an abstract class or an interface?

4. What is real object-oriented coding? Is it enough for me to program object-oriented?

5. What is unit test and how to write unit test?

If you have asked yourself a similar question, it means you have prepared for professional programmers. Of course, if you still cannot find the answer, you may also be able to read this book. I believe you will get a lot of money. After reading this book, I feel that the author has spent a lot of time thinking about it, and I am still doing a good job in explaining a lot of knowledge. Here I just hope that more people will benefit from it, of course, you don't like the amount.

Part 1 Language

1. Chapter 1 BASIC Language Elements

2. Chapter 2 set and

3. Chapter 3 generic, delegated, and event

4. Chapter 4 Resource Management and serialization

5. Chapter 5 Exceptions and custom exceptions

6. Chapter 6 Asynchronization, multithreading, task and Parallelism

7. Chapter 7 member Design

8. Chapter 8 Type Design

9. Chapter 9 Security Design

10. Chapter 10 naming rules

Chapter 11 code cleanliness

Chapter 12 standardized development behavior

From the beginning of the book to the directory, this book really attracted me deeply, as the author said, just as it is. I have also considered the three types of problems I think, but I gave up or forgot about them, however, today I am finally able to see this familiar feeling. This time I want to take a thorough picture of these questions and hope that I can learn more about the knowledge and mysteries in the book.

After reading the above, maybe many people share the same idea with me and want to take a good look at this book. So I hope you can give me some ideas or questions after reading the book, the release will allow everyone to discuss it and let me wait for cainiao to have more insights. For the moment, I am also considering whether to start with a PDF file, which is not just downloaded online. Since the chapters in this book are not relevant, you can simply read those chapters based on the knowledge you need. Therefore, if you plan to encounter problems at work, you can directly remedy the problem.