Debugging a single service orchestrated by Aspire #4278
Unanswered
KieranSunshine
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Can you explain the setup here a bit more? You mentioned 'that's normally orchestrated' -- why wouldn't it be now then? I'm assuming you are saying you'd still have something orchestrated w/Aspire (let's say ServiceA) that calls ServiceB, but that is NOT part of the Aspire environment? If so, what is preventing ServiceB from being a part of it? Don't own the source, diff repo, etc? (that'd be good to know). But given you say that you can still debug it I'm curious the source of ServiceB here? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey all, super pleased to see Aspire go to GA and I've been testing it out on some projects. So far it's been great!
I'm wondering what would be the easiest way to debug a single service that's normally orchestrated by Aspire? I can't see anything on the topic mentioned in the docs. I'm assuming it'd be something like running the service I need to debug externally (likely from an IDE) and somehow pointing the other Aspire projects to it. Honestly, this solution is probably fine. I just wasn't sure if there were any other 'better' approaches.
Cheers.
Beta Was this translation helpful? Give feedback.
All reactions