Recently, due to work needs, I verified before researching the xml generation. If there is a vacancy and the field content does not meet the requirements, an error message is displayed instead of producing xml content. After the demo test, I feel that it can be used, so I consider packaging it into a class library for later use. Because after consideration, it will use the core project, so I wanted to create a .net stardant 2.0 class library. In the process of its creation and release, there is this article, which is a summary of this knowledge point, and I want to share it.

Create a .net stardant 2.0 class library project-reference another library to create a custom class library. such as:System.ComponentModel.DataAnnotations，Newtonsoft.Json, etc. Because my verification considers usingDefinition features in DataAnnotations.

After writing a custom function, right-click on the project = "Properties" and check the "Produce NuGet package (G) during build" check box as shown above. Then compile and generate the project, you can see the NuGet package produced in debug.

As shown in the figure below, in the newly created project, open the "NuGet Package Manager" and click the icon in the upper right corner.

As shown in the figure below, add the source of the custom package and select the custom NuGet package set in the first image of this article.

Then select the source of the added package and add a custom package.

The above content is just a way for .net stardant 2.0 to reference, and .net stardant 2.0 only supports .net 4.6 and above versions to add references. So if you are using .net framework 4.6 or above or .net core project, you can consider producing Nuget packages.

The other is the same as the .net framwork reference method, just add the dll file reference directly. But this way is only when other libraries are not referenced in the custom class library, that is, all functions are manually implemented by you. Direct reference to dll, mainly to consider the compatibility of some projects can only use. Net framework 4.6 version below.

Another way is to publish directly. The specified file directory is published. The result of the publication is to generate a Nuget package. Refer to the above description for the reference method. Regarding this point, you can understand it yourself.