Visual Studio hacks (1)

Here hacks does not mean to use vs to do bad things. Although I really want to, it just collects various vs usage skills and so on to accelerate our development and enhance our vs Experience.

Now I feel that I have read a lot of books recently. "secrets" Give me advanced Asp.net knowledge. "vs hacks" solves many of my daily questions, "vs security programming" opens the way to vs security. The third version has not been started yet. The second version is now officially started. As for web services, it is not as good as ideal.

* Solution and project: I remember that they had doubts when talking about these two concepts, because many of the previous ides were based on a singleProgramOr there is no solution concept for a project. In fact, all enterprise-level development projects are composed of multiple projects, which is easy to imagine, for example, if you need PJ in a presentation layer and PJ in a data driver layer, you can also add a business layer and other layers to easily manage documents and reference projects.

* SLN & Suo: it is clear that Suo is a user option file. The startup Item setting is in this file, and SLN is the solution file. Appendix:Source codeDo not select suo in management. This is a problem I always encounter.

* Project generation sequence: if the project dependency has been set, vs knows the sequence. The startup project cannot be a non-output project, such as a class library.

* Ah, these books are too old and depressing.

* Solution creation: If the folder structure is complete, the top-level solution file sub-folders are various projects. In this case, it is best to create a blank solution and then add it.

* It is recommended that each layer be a project in a hierarchy.

* Multiple solutions: You can create a primary solution by using projects that correspond to multiple solutions.

* In a super-large project, you can add one logical folder to multiple projects for classification.

* Suo: a hidden file that stores binary data. If the file crashes, it can be deleted directly, and information set by the user will be lost.

* {E24C65DC-7377-472B-9ABA-BC803B73C61A}: The GUID that uniquely identifies a project or project type.

* Projectsection: record the project dependencies and whether the project is in debugging mode. If the project has no dependencies, this section is unavailable;