VS 2022 New Console App project will not build - Microsoft.NETCore.App dependency exclamation point

Dan Push 1

I installed VS 2022 Community, but when I create a new Console App (.NET 6) the entire "Dependencies" section in the Solution Explorer shows an exclamation point
I can't build the project or do much of anything

I've tried...
removed other versions of VS (2019)
reinstalled VS2022
"dotnet restore" in the project folder
moved "C:\Program Files\dotnet\" PATH value to top of list
restarted my PC after each of these steps

I'm running Windows 10 Enterprise (20H2)

Please help!

Dan Push 1 Reputation point

2022-02-08T17:58:54.103+00:00

Forgot to mention i am running VS 2022 Version 17.0.5
Karen Payne MVP 35,116 Reputation points

2022-02-08T18:27:04.34+00:00

I've tried...
removed other versions of VS (2019)
reinstalled VS2022
"dotnet restore" in the project folder
moved "C:\Program Files\dotnet\" PATH value to top of list
restarted my PC after each of these steps

None of the above will help as you have learned. Try right clicking on the project, select clean then unload the project followed by reloading the project, perform a build. Come back and inform us of the outcome.

No guarantees but have seen this clear things up in other projects.
Dan Push 1 Reputation point

2022-02-08T19:44:51.773+00:00

Thank you for the suggestion!

The clean failed, but the Output window indicated a successful build; however, things still aren't right:
There's no bin folder in the project dir, and otherwise i cant find any dll
My Dependencies section still has the exclamation
It took like 10+ minutes to build an unmodified console app template project (takes a second or two in VS 2019 on this machine)
Tianyu Sun-MSFT 27,356 Reputation points Microsoft Vendor

2022-02-09T09:14:29.96+00:00

Hi @Dan Push , do you have any permission limitation for related folders or .dll files, maybe? Are you using any antivirus software…? Besides, does repairing VS 2022 work(using VS Installer)?
Dan Push 1 Reputation point

2022-02-09T15:45:19.68+00:00

Hello @Tianyu Sun-MSFT , I don't think I have any permissions issues to the folders/files since VS2019 doesn't have the same issues and targets the same files, and I also have administrative rights on the machine. I am running Symantec AV software; I just tried adding "C:\Program Files\Microsoft Visual Studio\" and "C:\Program Files\dotnet\" to the AV's exception list, but that didn't resolve. I tried repairing again via VS Installer, but still no luck :(

No idea if this will help diagnose in any way, but some more info: IntelliSense also takes a long time to load. I created a new console app template project about seven minutes ago and it's still showing the loading animation
Tianyu Sun-MSFT 27,356 Reputation points Microsoft Vendor

2022-02-10T06:41:50.67+00:00

Hello @Dan Push , was previous VS 2019 installed and worked well while Symantec AV software was running? Is it possible to disable the AV software temporarily(enable it after testing and confirming that the project can be built) and try to reinstall VS 2022 then test again?
Dan Push 1 Reputation point

2022-02-10T15:29:15.41+00:00

@Tianyu Sun-MSFT , thank you for your help
Yes VS2019 is currently installed and working fine while Symantec AV is running.
I just tried these steps:
Disabled Symantec
Started VS2022
Created new console app project

Still ended up in the same state where dependencies are "flagged" and I am unable to build the project :(
Karen Payne MVP 35,116 Reputation points

2022-02-10T17:26:55.593+00:00

Try dotnet --list-sdks and report back what is outputted.
Dan Push 1 Reputation point

2022-02-10T17:45:54.133+00:00

@Karen Payne MVP
Karen Payne MVP 35,116 Reputation points

2022-02-10T22:04:54.253+00:00
This entire issue feels like interference from either the folder placement of the project, insufficient permissions to work with project(s) and/or anti-virus software seeing Visual Studio and/or your Visual Studio solution as an intrusion on your computer.

With that

Ensure you have sufficient permissions to the folder

Add the root folder of where projects reside to your anti-virus software exclusion list

You can also look at Windows event logs that may have clues to this issue and think if so will point back to the two items above.

Millions of developers use Visual Studio and when there are issues like the ones you are facing 99 percent of the time stem from the above.
Dan Push 1 Reputation point

2022-02-12T00:34:48.71+00:00

@Karen Payne MVP , I completely forgot about the event logs :) thank you for that suggestion! I do see errors in there that look like they may be Symantec related (even though I have tried disabling the AV and running VS--I suspect that Symantec is a dirty liar and is still doing "work" :( )

Going to work with my IT team to try to find a resolution and will report back
Thank you very much for your time and help!

3 answers

Bruce (SqlWork.com) 56,771 Reputation points

2022-02-08T20:54:34.677+00:00
right click on the dependency and open folder. the ref folder inside should have the dll's.

if the folder is missing, then you probably need the sdk installed.

dir C:\"Program Files"\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.1 Volume in drive C has no label. Volume Serial Number is 3267-69D9 Directory of C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.1 01/14/2022 11:34 AM <DIR> . 01/14/2022 11:34 AM <DIR> .. 01/14/2022 11:34 AM <DIR> analyzers 01/14/2022 11:34 AM <DIR> data 01/14/2022 11:34 AM <DIR> ref 0 File(s) 0 bytes 5 Dir(s) 184,519,589,888 bytes free
Please sign in to rate this answer.
Dan Push 1 Reputation point

2022-02-09T00:28:00.4+00:00

I can right-click on the "Analyzers" dependencies and see the referenced dll's in the folder
There is no option to open folder when right-clicking the "Frameworks" dependency. It may be relevant that there is no "Path" value in the properties section when selecting the framework dependency: Microsoft.NETCore.App (see the screenshot in the original post)

However, I do see the SDK files in the "..\ref" dir

I failed to mention in the original post that I have also tried reinstalling the .NET 6 sdk (and have also tried targeting .NET 5 with the same issues--also tried reinstalling .NET 5 sdk too)
Sign in to comment
Francisco Malpartida 1 Reputation point

2022-04-15T00:59:52.79+00:00

I have the exact same problem on my end!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Foon Lam 1 Reputation point

2023-01-02T01:49:56.207+00:00

I had the same problem. I could not find the "AlwaysCreate" property they mentioned, but I did manage to find it when I opened up the ".vdproj" file with Notepad and did a search for it. So you need to change the value frpm "FALSE" to "TRUE" in "AlwaysCreate" = "11:FALSE". There are multiple of them, so make sure you change them all.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment