added links to folders

Author: yorek

README.md

@@ -13,19 +13,19 @@ A set of samples that show how to integrate SQL Server and Azure SQL with .NET A
 
 ## Base Sample
 
-- Folder: `./base`
+- Folder: [`./base`](./base)
 
 The basic .Net Aspire application with a simple WebAPI project (WebApplication1) that you can use as a starting point to add support for Azure SQL or SQL Server
 
 ## Bring-Your-Own-SQL-Server (BYOSS)
 
-- Folder: `./byoss`
+- Folder: [`./byoss`](./byoss)
 
 The simplest integration of SQL Server in .NET Aspire. It takes the "Base" example and updates the WebAPI so that now it is calling an existing SQL Server, using a provided connectiong string.
 
 ## Aspire-Hosted SQL Server
 
-- Folder: `./hostedss`
+- Folder: [`./hostedss`](./hostedss)
 
 Change the BYOSS sample so the SQL Server is deployed and managed by Aspire orchestration, providing a basic integration with the Aspire environment. SQL Server is deployed in a OCI container by Aspire. No changes to WebAPI project.
 
@@ -35,7 +35,7 @@ The client WebAPI application (Webapplication1) is still getting the connection
 
 ## Aspire-Hosted SQL Server + DBUp
 
-- Folder: `./hostedss - dbup`
+- Folder: [`./hostedss - dbup`](./hostedss - dbup)
 
 In this sample, which is based on the previous one, deployment of database schema is also added to the solution. 
 
@@ -45,13 +45,13 @@ The database is deployed using an imperative approach, via the `DbUp` library, t
 
 ## Aspire-Hosted SQL Server + Database Project
 
-- Folder: `./hostedss - dbprj`
+- Folder: [`./hostedss - dbprj`](./hostedss - dbprj)
 
 Similar to the previous sample, but the database is deployed using a declarative approach, using a [SDK-Style Database Project](https://techcommunity.microsoft.com/blog/azuresqlblog/the-microsoft-build-sql-project-sdk-is-now-generally-available/4392063), that is also orchestrated by Aspire, via the community extension `CommunityToolkit.Aspire.Hosting.SqlDatabaseProjects`.
 
 ## Aspire-Hosted SQL Server + EF Core
 
-- Folder: `./hostedss - ef`
+- Folder: [`./hostedss - ef`](./hostedss - ef)
 
 In this sample, the client application (Webapplication1) is now using Entity Framework Core to interact with the SQL Server. The EF Core database context is provided via Dependency Injection, thanks to the usage of the library: `Aspire.Microsoft.EntityFrameworkCore.SqlServer`.
 
@@ -64,15 +64,15 @@ Please note that to keep the sample as simple as possible the EF Core entities a
 
 ## Aspire-Hosted SQL Server + DbUp + DAB
 
-- Folder: `./hostedss - dbup - dab`
+- Folder: [`./hostedss - dbup - dab`](./hostedss - dbup - dab)
 
 In this sample, taken from the `./hostedss - dbup` sample, and add Data API Builder (DAB) to the solution, so that the database can be exposed as a REST and GraphQL API, so there is no need anymore to manuallly created a CRUD API and therefore the WebAPI project is removed.
 
 DAB is orchestrated by Aspire, via the community extension `CommunityToolkit.Aspire.Hosting.Azure.DataApiBuilder`, that has been added to the AppHost project.
 
 ## End-To-End Jamstack "ToDo List" Application 
 
-- Folder: `./todo_app`
+- Folder: [`./todo_app`](./todo_app)
 
 Full end-to-end example of a Jamstack application, with a Vue front-end, a Data API Builder back-end, and SQL Server database, deployed using a [SDK-Style Database Project](https://techcommunity.microsoft.com/blog/azuresqlblog/the-microsoft-build-sql-project-sdk-is-now-generally-available/4392063). Everything is orchestrated by Aspire, including the Node application (TodoApp.Frontend), thanks to the `CommunityToolkit.Aspire.Hosting.NodeJS.Extensions` library.