Replies: 1 comment
-
|
Thank you for reaching out!
It's an addition that's not a part of the Aspire product, which is why it's separate.
That's a good point. Let us have a look at that, it makes perfect sense for us to use it if it's available. We've added an issue to track the work here: dev-proxy-tools/aspire#16 We're yet to upgrade the Dev Proxy Aspire extensions to Aspire 13, so bear with us just a bit longer. We'll be tracking the work here: dev-proxy-tools/aspire#15. We appreciate your patience. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to add dev-proxy to a project with Aspire. The goal of using Aspire is to achieve a zero-configuration for developers. They should be able to git the repo and start developing using their preferred environment.
I am using the dev-proxy Aspire integration but there are a few things that do not work as I would like:
Integration
The dev-proxy integration is a "stand-alone" integration. Why is it not part of Aspire or the Aspire CommunityToolkit?
This would also make sure that it is using the latest version of Aspire.
Root Certificate
I am using the AddDevproxyContainer() to add the dev-proxy integration. The issue with this is that it requires that developers do an extra step to trust the root certificate.
I would like to use the dotnet dev certificate for this. The workflow would be to have Aspire add the dev certificate (this is supported in Aspire 13 and dev-proxy will then pick up the certificate for further usage.
This would achieve my goal that there is no extra configuration required.
Having the integration in Aspire should be easy achievable and I am happy to help with this.
I understand that the certificate is more complex, but it would make the experience much better.
Beta Was this translation helpful? Give feedback.
All reactions