David Fowler
David Fowler
We have a lot of people trying to migrate from docker compose to aspire. It would be great to have a guide that explained how some of the concepts translate...
When we say aspire is optimized for local development, we say it without explaining how it relates to the different things that make up aspire. One common point of confusion...
- [ ] - Redis aspire component with SignalR - [ ] - Azure blob aspire component with data protection - [ ] - Azure table aspire component with orleans
There's enough interest that we should show a sample with Serilog
See https://github.com/dotnet/aspire/pull/388 e.g https://github.com/dotnet/eShop/blob/main/tests/Catalog.FunctionalTests/CatalogApiFixture.cs cc @ReubenBond
- https://github.com/dotnet/tye/tree/main/docs/recipes - https://github.com/dotnet/tye/tree/main/samples
https://learn.microsoft.com/en-us/dotnet/aspire/messaging/azure-service-bus-component?tabs=dotnet-cli#tracing We also don't mention that service bus traces are experimental in the SDK, and we don't explain how to turn it on. cc @eerhardt
Feedback for https://learn.microsoft.com/en-us/dotnet/aspire/frameworks/dapr?tabs=dotnet-cli 1. builder.AddDapr(); is not required. It is added automagically when you use `WithDaprSideCar` 2. `WithDaprSidecar` does not need the name specified, it's optional. 3. The mega code...