. NET leverages NuGet to manage class Library packages-system interactions

the University cloud platform, the development process, each team develops a subsystem. Each sub-system is also opened in a separate submodule.

for the entire platform, individual development does not affect other people's development. That is, interface-oriented programming.

so for each module, how to unify the interface of the other modules to call it?

In the development process, the development and use of the interface is definitely not updated regularly. Then the entire platform will definitely use a tool to manage The interface of each module uniformly.

Use nuget to manage the class libraries for each module. Each publish one of its own interfaces. If another system is called, the reference is made.

For example, the test system data, mostly from the basic system. So you need to reference the underlying system DLL files under the platform .

within each system, you can also use NuGet to manage.

Management using:

To publish your own class library package using NuGet:

1, on the NuGet official website, now register an ID and or apikey

Sign in to http://www.nuget.org/ and sign up for an account

after logging in, copy your apikey.

(This apikey is an account voucher that you publish your DLL file to NuGet.)

2. Download NuGet.exe

a command-line tool, a small plug-in it. Use him to upload.

3. Set the Apikey on your own computer

NuGet Setapikey < own apikey>

4. Develop your own class library

...

take a look at the AssemblyInfo.cs file in the class library.

In this file, there is the version number of the class library

rebuild the project, and then there will be a *.csproj file under the project folder

5, to publish

inside the cmd:

First, skip directories to your class library directory at the command line

After

Packaging: NuGet Pack examviewmodel.csproj

release: NuGet push Daxnetnugettest.1. 1 . 4 . 1 . Nupkg

after the publication is successful, you can NuGet The Management Toolkit found its own published class library package.

In the nuget Package , if you can see your own published class library. Indicates that the class library was published successfully.

if the system interface changes during the development process, take the fifth step directly (make sure to modify the version number OH). (This machine has already registered the API's case)

Using nuget to manage interactions between systems eliminates the hassle of copying dll files. reasonable use of management tools, eliminate the brain-free copy, can speed up the efficiency of the development of the system. Improving efficiency is the hard truth.

. NET leverages NuGet to manage class Library packages-system interactions