Skip to content
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

[BUG] Unable to create project using C# Dev Kit on Apple Silicon Mac #798

Closed
evgenyKozlov1996 opened this issue Dec 11, 2023 · 7 comments
Closed
Labels
area-project-cps bug Something isn't working

Comments

@evgenyKozlov1996
Copy link

Describe the Issue

Receiving error like
image

Steps To Reproduce

  1. Install C# Dev Kit 1.2.2 or 1.1.16.
  2. Try to run command .NET: New project

Expected Behavior

Project creates successfully

Environment Information

  • OS: macOS Sonoma 14.1.2

  • VS Code version: Version: 1.85.0 (Universal)
    Commit: af28b32d7e553898b2a91af498b1fb666fdebe0c
    Date: 2023-12-06T18:18:04.614Z (4 days ago)
    Electron: 25.9.7
    ElectronBuildId: 25551756
    Chromium: 114.0.5735.289
    Node.js: 18.15.0
    V8: 11.4.183.29-electron.0
    OS: Darwin arm64 23.1.0

  • C# Dev Kit version: 1.1.16, 1.2.2

@evgenyKozlov1996 evgenyKozlov1996 added the bug Something isn't working label Dec 11, 2023
@evgenyKozlov1996
Copy link
Author

Unable to run any command from C# Dev Kit for example .NET: Build produces the same error, but for build command:
image

@evgenyKozlov1996
Copy link
Author

After selecting existing folder with .csproj extension started working as expected

@timheuer
Copy link
Member

Everything working now @evgenyKozlov1996 ?

@evgenyKozlov1996
Copy link
Author

Hello, @timheuer! Yes, it's working now as expected but I think it's not a good solution to open existing directory with .csproj file in order to configure extension.

@timheuer
Copy link
Member

Hello, @timheuer! Yes, it's working now as expected but I think it's not a good solution to open existing directory with .csproj file in order to configure extension.

What would you prefer? I think you may be alluding to wanting an experience like CS to browse and open a file? This is a difference to how VSCode works—extensions activate on a workspace (folder) first

@evgenyKozlov1996
Copy link
Author

If it is possible to make the same behaviour if user opens *.sln file directory?

@webreidi
Copy link

Closing issue as initial error is resolved, enhancement request to open sln files is duplicated of #588.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-project-cps bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants