microsoft / microsoft/ConcordExtensibilitySamples
Extension not loading when debugging non-x86/x64 targets
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 135
- Forks
- 54
- Avg merge
- 5h 58m
- Merged PRs (30d)
- 3
Description
This might just be my lack of knowledge of how each target platform is supported using extensions more than anything else, so I'm trying to get a basis understanding.
My extension loads and runs fine when I start debugging a Windows x64 executable, but I'd like it to support other proprietary targets. Currently the extension does not load for these, and its DLL is not listed as a loaded module when debugging the extension itself. Is there a way I can confgure the extension to load for additional target types, or would I need some insider understanding of how their own Visual Studio debugger extensions work?
The platforms in question are covered under NDA so please excuse the vageness.
Cheers!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start with the Concord extensibility samples and the Visual Studio debugger-extension documentation to determine whether loading can be configured for additional target types. Done would require either a supported configuration path or confirmation that these proprietary targets are not supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100