-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check list for creating new Arcade package #374
Conversation
It might be worth to add that a way to pack the package is by using |
Documentation/HowToCreatePackages.md
Outdated
@@ -0,0 +1,39 @@ | |||
# How to Create an Arcade Package | |||
|
|||
One of the goals of Arcade is to be a vehicle to provide code sharing. One of the ways that this goal is implemented by through NuGet packages. This document assumes that you are adding a package called `ProjectOne` to Arcade and provides a list of things you should check when while doing that. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Documentation/HowToCreatePackages.md
Outdated
@@ -0,0 +1,39 @@ | |||
# How to Create an Arcade Package | |||
|
|||
One of the goals of Arcade is to be a vehicle to provide code sharing. One of the ways that this goal is implemented by through NuGet packages. This document assumes that you are adding a package called `ProjectOne` to Arcade and provides a list of things you should check when while doing that. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Documentation/HowToCreatePackages.md
Outdated
|
||
`src/Microsoft.DotNet.ProjectOne/tests` | ||
|
||
- It would be great if you could include a `README.md` file on the root of the package. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Documentation/HowToCreatePackages.md
Outdated
|
||
- Include the package on the `Arcade.sln` file. This way it will be compiled automatically when the solution is built. | ||
|
||
- Make sure that library dependencies of the new package use the Arcade defined version of the library. The versions are defined in the `eng\Version.props` file. For instance, if the project has a dependence on Newtonsoft.Json you must add it as follows: |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@maririos pushed new changes addressing your comments. Thanks. I believe the packages are created automatically during the building process. Do you want me to include a comment about how to manually create the package on the command line? |
Documentation/HowToCreatePackages.md
Outdated
## Further References | ||
|
||
- https://github.com/dotnet/arcade/blob/master/Documentation/Overview.md#toolset-nuget-package-requirements |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Closes: #370