Wasm standalone doesnt configure in Aspire & gives "there was no runtime..." error. #2959
Unanswered
SalomonHenke
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey all
When adding a webassembly standalone to the aspire orchestration it:
When i add it manually i get the following error:
if i do not add it to the shared, aspire starts 2 instances of the wasmstandalone project + isn't able to configure service discovery bindings. not sure if it's just me. Tried reinstalling my sdks, vs, workloads etc. same issue.
feedback appreciated.
Beta Was this translation helpful? Give feedback.
All reactions