-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First run on fresh machine fails #1721
Comments
Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned. |
Note: Restarting Visual Studio Code and trying again did not resolve the issue. |
Thanks @pierceboggan for the feedback! From your attached log (the Our toolkit depends on .NET 5 or .NET SDK 3.1. However neither .NET 5 nor .NET SDK 3.1 supports M1 Mac yet (see this github issue). Our current design is the users will follow the "learn more" link to install .NET manually in case they work on M1, so this is the expected behavior. But we think your feedback is great and we will update our document to clarify the issue of .NET SDK on M1 Mac explicitly. If you have any other questions, please let us know. |
I am blocked on this too with my m1 MacBook. Is there a way to install .NET 6.1 which has support for m1 chips and use with the msteams vscode extension? |
Describe the bug
The first run experience failed due to an issue installing required .NET dependencies.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Application builds and deploys successfully without requiring user intervention.
** Actual behavior**
Failed to install .NET Core SDK error.
Screenshots
If applicable, add screenshots to help explain your problem.
VS Code Extension Information (please complete the following information):
Additional context
Teams Toolkit extension output:
The text was updated successfully, but these errors were encountered: