microsoft / microsoft/MIEngine
'Hit F5' is not enough as guide suggests
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
The initial guide suggests that debugging MIEngine could be started automatically as soon as F5 is hit, when solution is opened. That's not correct for me and should be updated. Or am I doing something wrong?
I noticed that MIEngine actually shares the same GUIDs as VS build-in MDD debug-engine used for Android development (which RTM version doesn't work for me neither; can't start debugging on my 2 non-VM machines, failing with 'Reference not set to an instance of object' exception). That's why MIEngine is never loaded, then no breakpoints are working etc.
Very first step is actually following redistribution instructions to customize the GUIDs. Then it works as expected.
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
Start with the Quick-tutorial-on-debugging-the-MIEngine guide and compare its F5 instructions with the Redistribution instructions. Update the guide to explain that GUID customization is required before debugging starts, then verify that the documented setup matches the reported working sequence.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100