microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Echobot v2 - run locally error
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hi, I wanted to know how I can run the echobot v2 locally, as there used to be a local configuration file where I could add keys and test quickly, but that no longer exists.
What I do is clone the project and try to run it in Visual Studio as an administrator.
Note that I have already deployed it using steps 1, 2, and 3 in Azure, but for testing purposes, I want to run it locally.
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 by reviewing the repository's local run process after cloning and compare it with the Azure deployment steps 1, 2, and 3 mentioned in the issue. The screenshots describe the local Visual Studio failure, and the work is done when Echobot v2 can be run locally for testing with the required configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100