You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explain how Aspire and package management is used with samples (#1139)
* Explain how Aspire and package management is used with samples
* Update astro/src/content/docs/identityserver/samples/index.mdx
Co-authored-by: Maarten Balliauw <maarten.balliauw@duendesoftware.com>
---------
Co-authored-by: Roland Guijt <roland.guijt@gmail.com>
Co-authored-by: Maarten Balliauw <maarten.balliauw@duendesoftware.com>
Copy file name to clipboardExpand all lines: astro/src/content/docs/identityserver/samples/index.mdx
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,25 @@ Most of the samples include both their own IdentityServer implementation and the
27
27
The [_Basics_](/identityserver/samples/basics.mdx) samples use a [shared IdentityServer implementation](https://github.com/DuendeSoftware/Samples/tree/main/IdentityServer/v8/IdentityServerHost).
28
28
Some samples use our public [demo instance of IdentityServer](https://demo.duendesoftware.com/).
29
29
30
+
### Aspire
31
+
32
+
To simplify local development, many samples include an *Aspire host* project. This eliminates the need to run or debug individual projects manually, and provides a better experience running the samples.
33
+
34
+
* Launching the `AppHost` project makes sure all projects are started in the correct order
35
+
* Relevant projects reference the `Aspire.ServiceDefaults` project, which automatically configures health endpoints and telemetry for the Aspire dashboard.
36
+
* If a sample includes a database, you can use the database icon directly inside the Aspire dashboard to create the database and run migrations.
37
+
38
+
### Package Management
39
+
40
+
These samples use **Central Package Management**. While individual project files still reference NuGet packages, they do not contain version numbers. Instead, dependency versions are managed in two places:
41
+
42
+
***NuGet Packages:** Managed via the `Directory.Packages.props` file located in each IdentityServer and BFF version directory.
43
+
***Aspire SDK:** Centrally defined in the `global.json` file at the repository root.
44
+
45
+
:::note[Always clone the full samples repository]
46
+
Because of this centralized structure, samples will only compile and run correctly if the entire repository is cloned. Downloading individual project folders will result in build errors.
47
+
:::
48
+
30
49
## Feedback
31
50
32
51
You can [join the Duende developer community](https://github.com/DuendeSoftware/community/discussions) if you are looking for a particular sample and can't find it here.
0 commit comments