can't run the basic console tutorial, can't run the program, Attach shows rather than program name

Question

can't run the basic console tutorial, can't run the program, Attach shows rather than program name

Ken Hackbarth 0

Just installed VS 2022 and am trying to run the first tutorial - create a console app. When I launch VS 2022 I don't see the app name to the right of the green "play" icon. Instead I see the word "Attach". If I click on that I am presented with an "Attach to process" dialog and I have no idea what to do or why. I see the same behavior on two different Windows 11 computers after a fresh install of VS 2022 Version 17.9.1.

Ken Hackbarth 0 Reputation points

2024-02-22T22:32:15.3766667+00:00

FWIW, I've tried running VS 2022 as administrator and have tried changing MS account to the account that I use to login on this PC.

6 answers

Your answer

Ken Hackbarth 0 Reputation points

2024-02-22T22:32:15.3766667+00:00

FWIW, I've tried running VS 2022 as administrator and have tried changing MS account to the account that I use to login on this PC.

Answer 1

I was able to install VS 2022 on a third PC and get the Console app to work. This PC has fewer applications installed - in particular it doesn't have NSB AppStudio and RemotePC installed. I don't know if either of these apps is in conflict with VS, but they're both more valuable to me right now than VS. So, rather than installing each on the third PC and seeing when/if the problem resurfaces, let me ask you, "What should I Attach to ?" Maybe I can get VS working on the first two PCs (even if just procedurally). Thanks, Ken

Answer 2

I gave it a shot. First, I looked at my environmental variables and there was no entry for C:\Program Files\dotnet or C:\Program Files (x86)\dotnet. So I put the first one in and moved it above the reference to the tools directory. EV1

relaunched VS and saw no change (still "Attach" next to Play button) I thought it might be the absolute path so I put %USERPROFILE% in place of C:\Program Files: EV2

Restarted VS and no change. So I followed the link to install the latest .NET and here's what I saw at completion of the install: The installation was successful. The following products were installed: • .NET SDK 8.0.201 • .NET Runtime 8.0.2 • ASP.NET Core Runtime 8.0.2 • .NET Windows Desktop Runtime 8.0.2 Per instructions on the install page, I tested the install in the command window: C:\Users\ken>dotnet Usage: dotnet [options] Usage: dotnet [path-to-application] Options: -h|--help Display help. --info Display .NET information. --list-sdks Display the installed SDKs. --list-runtimes Display the installed runtimes. path-to-application: The path to an application .dll file to execute. Restarted VS and repeated the process. No change (other than lots of ConsoleApp solutions...): current state

Ken Hackbarth 0 Reputation points

2024-02-23T16:55:15.9966667+00:00

I moved over to the other Windows 11 PC because that one has screen recording software. I recorded a video that shows exactly what I'm experiencing. Please point out where I've deviated from the proper project creation process or what might be going on. First, here's what the Path value looks like on that PC after the installation of VS 2022 and un-edited:

Here's a link to the video on YouTube. Thanks, Ken

Answer 3

Anna Xiu-MSFT 31,201 Microsoft External Staff

Hi @Ken Hackbarth,

Welcome to Microsoft Q&A!

Please search "Edit the system environment variables" in Windows Search box > Open it > Environment Variables… > System variables > select Path > Edit… > check if there are two paths to dotnet:

C:\Program Files\dotnet

C:\Porgram Files (x86)\dotnet

If you can find them, please click on the Move up button to move the entry C:\Program Files\dotnet before the x86 one.

Or delete this one: C:\Porgram Files (x86)\dotnet.

Then, re-launch the VS2022 and create a new project to check it again.

If it doesn’t work, please try to manually download and install the latest .NET SDK with 64-bit version.

Sincerely,

Anna

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Anna Xiu-MSFT 31,201 Reputation points Microsoft External Staff

2024-03-04T07:10:38.62+00:00

Hi Ken, sorry for the delay reply!

From your –info output, you are still hitting x86 path. Please select the Path of System variables instead of User variables.
Ken Hackbarth 0 Reputation points

2024-03-05T03:57:01.23+00:00

Here you go, hope it helps...
Anna Xiu-MSFT 31,201 Reputation points Microsoft External Staff

2024-03-05T06:41:45.84+00:00

Hello, please click on the Move up button to move the entry C:\Program Files\dotnet before the C:\Porgram Files (x86)\dotnet.

Or delete this one: C:\Porgram Files (x86)\dotnet.

Then, re-launch the VS2022 and create a new project to check it again.
Ken Hackbarth 0 Reputation points

2024-03-05T15:33:25.4066667+00:00

This solved the problem. Thank you. I only moved it up, I didn't delete the x86 entry for fear that a different program needs to reference it.

Answer 4

Ken Hackbarth 0

Here's the tutorial. I chose VB as the coding language. And here's what my screen looks like: IDE for console app

Thanks, Ken

Michael Taylor 61,221 Reputation points

2024-02-23T03:28:15.1266667+00:00
You don't have a project open and therefore there is nothing to debug. It doesn't seem like you followed the steps in order, or you did some of the steps and later came back to continue. Let's reset.

Open VS.

On the start page click Create a new project.

Select the Console App template for VB.

Type in a name for the project. Note the location where the project will be stored.

Finish out the wizard.

The screen you showed should pop up but in Solution Explorer under the solution node that you see now should be a project that matches the name you used in the earlier step. It should have a VB-like icon indicating it is a VB project.

You should now be able to build (F8) and run (F5) your project as the tutorial discusses.

If you had previously created the project but then shut down VS, or after completing the above steps you close VS then to get back to the same point do the following.

Start VS.

On the Start page it should show you the recent projects and solutions. Select the project you created before to reopen it.

You should now be able to build and run as before.

If you have a project/solution on disk that you have never opened in VS before (such as one you downloaded from the internet) then do the following.

Start VS.

On the Start page choose the option to Open a project.

Navigate to the project in the file system and select the .vbproj or .csproj file.

The solution opens and you can now build/debug as before.

Simply opening a .vb (or .cs) file does not allow you to build and debug like the tutorials would guide you.

Answer 5

Did you open the solution? In order to run code in the debugger that you wrote you need to have that code in a project. Wrapping each project is a solution which is just a virtual collection of related projects. Once you have a project loaded in VS with your code in it then you can build that code using F8 and then run the code using F5.

An easy way to tell if you have a solution open or not is the fact that the solution name is shown in the titlebar of VS. Additionally in Solution Explorer you'll see the solution node and under that your project node (console app). Under the project node is your source files that you can edit.

enter image description here

We don't know what tutorial you're referring to so please provide us a link to the steps you're following and ideally a screenshot or something so we can see what you're seeing.

Share via

can't run the basic console tutorial, can't run the program, Attach shows rather than program name

6 answers

Your answer