Repository files navigation

The .NET Podcast app is a sample application showcasing.NET,ASP.NET Core,Blazor,.NET MAUI,Azure Container Apps,Orleans,Playwright, and more.

In addition, we created an Approval App usingMicrosoft Power Apps to handle incoming podcast requests.

For this sample application, we build an app to listen to all your favorite .NET podcasts for all the ecosystems: Web, Android, iOS, macOS and Windows. You can find the different apps separated by folders in this repo:

• Mobile & Desktop: Native .NET MAUI Application for iOS, Android, macOS, and Windows
• Website: Blazor WebAssembly app and ASP.NET Core Razor Marketing website
• Backend API: ASP.NET Core Web APIs & Minimal APIs, ingestion worker, and podcast update worker
• Blazor Hybrid App: Sample hybrid application of .NET MAUI with Blazor.

Additionally, we build an application usingMicrosoft Power Apps to allow us to reject or accept incoming podcast requests:

• Microsoft Power Apps: Power Apps sample to handle incoming podcast requests.Follow these guidelines on how to import the Approval Power App into your own Power Platform environment orcheck out how to connect your API with the Microsoft Power Platform.

dotnet-podcasts repo is configured to deploy all services and websites automatically to Azure using GitHub Actions.Follow the detailed guidelines to setup GitHub Actions on your fork.

The easiest way to get started is to build and run the .NET Podcasts app service, database, and storage using Docker.

1. First installDocker Desktop
2. Clone the repository and navigate to the root directory in a terminal
3. Run the following docker command (this may take some time to pull images, build, and deploy locally)

docker-compose up

• For Apple arm64-based system:

docker-compose -f docker-compose.arm64.yml -f docker-compose.override.yml up

This will deploy and start all services required to run the web, mobile, and desktop apps. The Web API will run onlocalhost:5003 and the SignalR Hub for listen together will run onlocalhost:5001.

The apps are configured to speak tolocalhost on the correct ports for each service. Simply open theWeb solution or the.NET MAUI solution and run the app.

Ensure that you have the following services running in Docker (podcast.api, listentogether.hub, podcast.updater.worker, podcast.db, storage):

Open theServices solution and pick a service to run locally such as thePodcast.API.

Ensure that the following services are running in Docker, note that you only need thepodcast.db andstorage:

1. First installDocker Desktop
2. Clone the repository and navigate to the root directory in a terminal
3. Open the solutionNetPodcast.sln, set the start project todocker-compose and hit F5. To optimize debugging while running all services, please refer toLaunch a subset of Compose services documentation.
4. By default, the Podcast.Api's swagger endpoint will be launched. Navigate tolocalhost:5002 for the web application. If you see any errors, wait for a while and refresh the page.

This project welcomes contributions and suggestions. Most contributions require you to agree to aContributor License Agreement (CLA) declaring that you have the right to, and actually do, grant usthe rights to use your contribution. For details, visithttps://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to providea CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructionsprovided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted theMicrosoft Open Source Code of Conduct.For more information see theCode of Conduct FAQ orcontactopencode@microsoft.com with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsofttrademarks or logos is subject to and must followMicrosoft's Trademark & Brand Guidelines.Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.Any use of third-party trademarks or logos are subject to those third-party's policies.