-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Can not launch game from Visual Studio 2022 #28
Comments
I can not install this tools. |
Debug will not launch even after plugin installed. |
I have the same problems |
Same here. Plugin is completely useless at this point. Install it and it does literally nothing but waste your time and cause hours of frustration as you try to find any way to get it to work properly. Please fix. |
I have the same issues, hopefully this can get a fix. I prefer Visual Studio over Visual Studio Code. |
Works for me, if i use the workaround, including Intellisense completion (completion stopped, then started working again). |
I have the same issue, how can we resolve this? I tried some workarounds, but none worked so far. Main problem with those is migrating project of sort error. |
Can someone say, how to debug with this plugin? |
Workarounds do not work if you target C# 8.0. |
Update 27th Feb 2023Summary of instructions for VS2022 |
Workaround mentioned for VS2022 works but with one additional note: Remove existing VS extension if it was previously installed. |
Windows 10
Godot 3.4.3
Microsoft Visual Studio Community 2022 (64-bit) - Current: Version 17.1.0
Using version 2.0.0 of the extension
As I understand it the package is supposed to add launch profiles, similar to the extension for VSCode (that one worked wonderfully) but it seems to do absolutely nothing in Visual Studio 2022.
I tried installing and resinstalling, enabling and disabling the extension, I looked through the available settings for that extension (and found that it needed the path to Godot, that I added).
But no launch profiles are added, so I'm not sure if it's a bug, if I forgot a step, or if this simply isn't what the extension is supposed to do.
The text was updated successfully, but these errors were encountered: