Objective C # Master related tools and resources

This is an exciting time for C # And. net. These tools are still relatively new. Community They are learning how to use these tools. Some resources can help you improve your knowledge and create a larger Knowledge Community for. NET and C. These tools are recommended to C # developers every day. All the content about C # practices is still being written. Follow up with them and keep learning about the relevant content.

The first tool that should be used in every C # developer's toolbox is nunit, which can be found at http://www.nunit.org/net site. Nunit is a tool for automatic unit testing, which features similar to JUnit. Like most other developers, I hate writing tests.CodeAnd test it by yourself. Nunit makes these processes very efficient. After you use these tools regularly, you will be used to testing all your C # classes. Whenever I create a class library project, I add an nunit test project and add the automatically generated test as part of it. I add a configuration to create and run a test so that the test can be performed at each compilation. Then, I can switch the configuration of the activity to determine whether to make the unit test formal.Program. By default, I run them. When I need to perform a UI test, I will switch to another configuration.

When using nunit, you can check the nunitSource codeI learned some interesting technologies. Nunit uses some advanced reflection habits to load and test your assembly. It uses features to find test packages, test cases, and expected results for each test case (see Principle 42 ). This is a very good example. It shows you how to use these technologies to create tools that can be dynamically configured by yourself and can be widely used.

Next is fxcop, a free tool that can be obtained from gotdotnet (http://www.gotdotnet.com. Fxcop analyzes the IL in your assembly to see if it violates the principles of practice and where to report such violations. Each principle has a reliable metric specification, and the reason for its use. Like all the Recommended Principles in this book, some documents have a brief reason for a certain principle. You can determine whether these actual problems comply with these suggestions. You can also configure whether to apply every principle to the project. I do not agree with some principles in fxcop, And I have explained the reason before this book. However, like nunit, fxcop can be part of the formal program you create. After each compilation, you can have a post-compilation step. You can use fxcop to analyze the principles you choose. Figure 6.1 shows an example output from fxcop. Although some recommendations are not my favorite (for example, one is to make every assembly visible to com), it is indeed a useful tool, because it allows you to think a lot about the default decisions you have made.

Figure 6.1: A project analyzed by fxcop:
Figure 6.1. fxcop analyzing a project.

[View full size image]

 

 

Ildasm is an il anti-assembler. In this book, I have demonstrated some il code, which is generated by the compiler for different C # structures. Although I don't believe many people may choose to write il Code if they have advanced languages, you should be familiar with it. Knowing the Il code generated from different C # structures can help you become a better developer. You can check the Il code for your own assembly, or the assembly in the. NET Framework. This is the use of ildasm, And it is released together with the. NET Framework SDK. Il is available for all developers. Ildasm allows you to see the intermediate language of your assembly. In any case, this is a good way to learn the. NET Framework assembly, which is also the original information.

 

 

These are only part of your official toolbox, but having these tools is just one aspect of improving your skills. A large number of online resources and communication communities allow you to participate and learn, and increase your own C # And. NET Framework knowledge. The first and most important thing is the gotdotnet website (www.gotdotnet.com), which is the official website of the. NET group. C # The team has a site on msdn, which is currently in msdn.microsoft.com/vcsharp/ (which is accidentally reorganized due to changes on the msdn website ). If your work is primarily network-based, try to access www.asp.net, which is provided for ASP. NET groups. If your job is mainly based on Windows form, try www.windowsforms.net, which is the official website of the Windows form group. These websites contain many references and implementations of conventional programming, which may be desired in your applications. They are also source file components, so you can detect and modify them to make them what you want. The last and most important point should be to understand the web pages in the MS mode and practice. This webpage is currently in.
In addition, the Code and libraries of some new examples are often updated here, which may help you solve regular programming problems. When writing this, you can use 10 different application blocks to implement some common program requirements. I'm sure when you read this, there is more content in these areas.

I also recommend subscription of some FAQ in group C: Buy. Here you can find the latest list: http://msdn.microsoft.com/vcsharp/team/blogs/

If you want to learn more about the language and environment, you can detect the shared CLI (code-named rotor ). This includes the. NET Framework and some core content of the C # compiler. You can read these materials to gain a deeper understanding of every function and. NET Framework in C. Not all. Net commercial frameworks have available shared materials: for example, shared code is not released for special windows code. However, these released subsets are also enough for you to learn more about the CLR and C # languages.

C # the compiler has been released with the shared CLI, which is written in C ++ and serves as the underlying CLR code. You must have a deep understanding of C ++ and a clear understanding of compiler design. Modern Language compilers are complex software blocks, but CLR data is a useful tool to understand how the core functions of the. NET Framework are implemented.

Here is just a simple list, I just introduced a surface in many materials. You can get a lot of information in MS, other online websites, or books. The more you use these tools, the more knowledge you get. The whole. NET and C # communities are moving forward, because they are developing rapidly and the resources listed may be constantly changing. You can learn and write your own documents.