Reputation: 249
I'm trying to access the project properties but the window appears blank. I've tried web solutions View>Properties Window, f4, right click on project folder>properties, Also tried resetting import/export settings, searching for specific tab
everything results in a blank window.. Any help is appreciated! Thanks in advance.
Upvotes: 22
Views: 15618
Reputation: 315
Something to try: close and reopen the project, but don't open it back up using Visual Studio. Instead, navigate to the .sln project file and double click on that.
Upvotes: 1
Reputation: 51
The only solution for me was drag the window with the mouse! It immediately populate it! Then I leaved the window in its original position.
VS Community 2022 17.9.6
Upvotes: 0
Reputation: 21
Problems with properties window not updating when in view designer window.
It sometimes will not populate the properties window with the data of the object you have clicked on in the design view. To fix this I right click the .cs file in the Solution Explorer and change to view code, then right click again and select view designer and poof like magic the properties window start working again.
Upvotes: 2
Reputation: 131
I ran into this same problem with VS 2022 v17.4.0 Preview 1.0 in a C# Windows forms app. Closing and opening the solution/VS didn't have any effect.
After I closed all the open tabs and reopened a file, the Properties pane was populating correctly.
Edit: After closing tabs and opening the properties if its still blank move the Window and it shows!
Upvotes: 13
Reputation: 21
This just started happening to me in VS2022. I know I'm coming late to the question, but it's the most recent I could find.
In any case, I took a guess, deleted the .csproj.user file, and restarted VS. That did the trick.
Upvotes: 0
Reputation: 11
Had this issue for ages where properties wouldn't populate, properties finally populated after I had opened the VS app as admin. - Hope this helps others.
Upvotes: 1
Reputation: 543
I was able to consistently reproduce the bug by double clicking the Build Action value.
This was making the content of the Properties Window to disappear.
To work around it, I've created a new "abc.json" file and set the values of Build Action and Copy to Output Directory from the dropdown.
Upvotes: 2
Reputation: 1972
As IVanF. states in his answer above, I too experience this issue when I accidentally double click in the 'Build Action' option within the 'Properties' pane. For me the file type is a .cshtml file.
The easiest solution I've found is to exclude the file and then include the file.
Upvotes: 0
Reputation: 399
This just happened to me when I double clicked on the Build Action property.
I finally opened the project file in a text editor and noticed that the XML defining that file in an item group started with "Page" instead of "None".
<Page Include="myFile.txt" />
instead of
<None Remove="myFile.txt" />
Manually editing the project file back to "None" fixed the problem.
Seems that the root cause is that double clicking automatically selects the next option in the Build Action list, and the next option is "Page".
Upvotes: 1
Reputation: 773
I manually edited .csprj file and removed all entries related with [file].json, saved and the file's properties are now showing
Upvotes: 0
Reputation: 926
Going away on another opened tab and coming back starts populating properties window.
Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.5.3
Upvotes: 6
Reputation: 11
1 Make sure that your build program is not running (use task manager to end that process if needed) and make sure that you can rebuild your project without errors. 2 Restart Visual Studio as an Administrator. Good Luck For You All ^_^
Upvotes: 0
Reputation: 1
This happens constantly on my install. I simply minimize the entire VS window, then restore it. Poof! My properties appear. Trivial, but painful.
Upvotes: 0
Reputation: 414
Does your toolbox items also appear 'greyed out'?
Try Going to your Build Menu and select
Clean Solution
(and perhaps Rebuild afterward - or not)
Upvotes: 0
Reputation: 25
I have just encountered this error and it was simply solved by closing the visual studio and reopening it again. it is just gone.
Upvotes: -1