Mitch Denny

> Would love love love to see full reverse proxying be built into aspire. I see it as somewhat mandatory to complete the experience. You can't properly test things like...

To be fair those issues always have existed. We just haven't plastered over them yet ;)

I was going to say this is fixed .. but there is another dimension. Storage for example actually implements `IResourceWithEndpoints` because it returns an `EndpointReference` which takes an `IResourceWithEndpoints` in...

Closing this. I think Azure Storage is a special case but I don't think we can fix this without breaking API. We would need the notion of a resource that...

I'd be interested in @jstedfast's perspective on this. For Aspire we have a model for adding Aspire-specific APIs to glue in various OSS libraries (for example we could have Aspire.MailKit)...

Yeah, I think building from `smtp://host[:port]` to the various auth mechanisms mentioned in the draft make sense.

Once the format of the connection string is established them being able to plug and play different mail servers and clients becomes a heck of a lot easier.

I'm going to move this over to community toolkit because if we do add any support for a specific dev-time mail servers it'll probably happen over there.

@maddymontaquila @aaronpowell what is the correct way to hand these off?

OK so I've had a bit of a look at this. I think what we would need to do is modify `WithDaprSidecar()` to get access to the underlying `ExecutableResource` that...