Difference in WithEndpoint impl from preview 4 to preview 5 #3709
-
|
Hi, I opened this issue today and it's closed. The proposed solution in comment works, but is different than what was working for me in preview 4 Can someone ELI5 to me why in preview 4 was this working for my case:
I understand this was defining a endpoint that isn't proxied (ie Aspire doesn't generate any URL for it) and binds to host port (which I dynamically change in my service). However, I don't have the same flexibility with new implementation of I presumed |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
By default, when you add a project resource, we read your launch profile and add endpoints. Using this should still work fine:
Non proxied endpoints means that you need to specify the port.
If you don't disable the launch profile, we'll still end up using it in your appliction. That's the same as it was in preview 5.
This doesn't do anything related to what you want, ignore it. Looking at your repository, you're defining endpoints in the kestrel configuration section. If you want to use these bindings then you do want to disable the launch profile and specify them in the apphost (as @mitchdenny said here #3695 (comment)). There's an open work item to support reading the kestrel configuration section for project resources to automatically define endpoints: |
Beta Was this translation helpful? Give feedback.
By default, when you add a project resource, we read your launch profile and add endpoints. Using this should still work fine:
Non proxied endpoints means that you need to specify the port.
If you don't disable the launch profile, we…