You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.

nightlies.md 3.0 kB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. ---
  2. uid: Guides.GettingStarted.Installation.Nightlies
  3. title: Installing Nightly Build
  4. ---
  5. # Installing Discord.Net Nightly Build
  6. Before Discord.Net pushes a new set of features into the stable
  7. version, we use nightly builds to test the features with the
  8. community for an extensive period of time. Each nightly build is
  9. compiled by AppVeyor whenever a new commit is made and will be pushed
  10. to our MyGet feed.
  11. > [!IMPORTANT]
  12. > Although nightlies are generally stable and have more features
  13. > and bug fixes than the current stable build on NuGet, there
  14. > will be breaking changes during the development or
  15. > breaking bugs; these bugs are usually fixed as soon as they
  16. > are discovered, but you should still be aware of that.
  17. ## Installing with MyGet (Recommended)
  18. MyGet is typically used by many development teams to publish their
  19. latest pre-release packages before the features are finalized and
  20. pushed to NuGet.
  21. The following is the feed link of Discord.Net,
  22. * `https://www.myget.org/F/discord-net/api/v3/index.json`
  23. Depending on which IDE you use, there are many different ways of
  24. adding the feed to your package source.
  25. ### [Visual Studio](#tab/vs)
  26. 1. Go to `Tools` > `NuGet Package Manager` > `Package Manager Settings`
  27. ![VS](images/nightlies-vs-step1.png)
  28. 2. Go to `Package Sources`
  29. ![Package Sources](images/nightlies-vs-step2.png)
  30. 3. Click on the add icon
  31. 4. Fill in the desired name and source as shown below and hit `Update`
  32. ![Add Source](images/nightlies-vs-step4.png)
  33. > [!NOTE]
  34. > Remember to tick the `Include prerelease` checkbox to see the
  35. > nightly builds!
  36. > ![Checkbox](images/nightlies-vs-note.png)
  37. ### [Local NuGet.Config](#tab/local-nuget-config)
  38. If you plan on deploying your bot or developing outside of Visual
  39. Studio, you will need to create a local NuGet configuration file for
  40. your project.
  41. To do this, create a file named `NuGet.Config` alongside the root of
  42. your application, where the project is located.
  43. Paste the following snippets into this configuration file, adding any
  44. additional feeds if necessary.
  45. [!code[NuGet Configuration](samples/nuget.config)]
  46. After which, you may install the packages by directly modifying the
  47. project file, using the dotnet CLI (`dotnet add package Discord.Net`),
  48. or by using PowerShell (`Install-Package Discord.Net -Prerelease`).
  49. ***
  50. ## Installing from AppVeyor Artifacts
  51. As mentioned in the first paragraph, we utilize AppVeyor to perform
  52. automated tests and publish the new build. During the publishing
  53. process, we also upload the NuGet packages onto
  54. AppVeyor's Artifact collection.
  55. The latest build status can be found within our [AppVeyor project].
  56. [AppVeyor project]: https://ci.appveyor.com/project/rogueexception/discord-net
  57. 1. In the project, you may find our latest build including the
  58. aforementioned artifacts.
  59. ![Artifacts](images/appveyor-artifacts.png)
  60. 2. In the artifacts collection, you should see the latest packages
  61. packed in `*.nupkg` form which you could download from and use.
  62. ![NuPkgs](images/appveyor-nupkg.png)