How do I fix broken VS2017 solution explorer?

Question

0.00/5 (No votes)

See more:

Hi,

This is a vague question and I wouldn't ask if I weren't desperate.

I have just switched to a brand new installation of VS2017 on a new installation of Windows 10. The Solution Explorer appears to be broken.

My solution-level folders disappear every time I reopen the solution. I have to click on some odd combination of the buttons to get it to show the solution-level folders while not showing every bin and obj folder.

More worryingly, I have just created a fresh WPF project and it has failed to nest the .xaml.cs files beneath their .xaml counterparts.

To be honest, the whole thing so far feels as buggy as hell. Has anyone else encountered anything like this?

Any help or advice would be desperately appreciated. I'm struggling to work in it as it stands.

What I have tried:

Deleting the solution and recreating it.

Running VS2017 as Administrator.

Posted 12-Feb-18 23:15pm

Patrick Skelton

Updated 13-Feb-18 0:39am

v2

Add a Solution

Comments

Mehdi Gholam 13-Feb-18 5:19am

Have you installed WPF support in VS2017?

phil.o 13-Feb-18 5:24am

I'm running VS2017 on Windows 10 for a year now, and so far I did not have any issue.
For your first problem, you could try to delete the .suo file (once) from the solution before opening it.
For your second problem, I don't do XAML enough to answer. Does the nesting issue also occurs with other object types (Forms, for example)?

Richard MacCutchan 13-Feb-18 5:29am

I have been using 2017 for quite a few months on Windows 10 and never seen anything like you describe. I have imported lots of different projects from previous versions and all came over without incident. But it is difficult to guess exactly what may be the issues you are seeing.

RickZeeland 13-Feb-18 5:33am

Maybe run the VS installer and select "repair" ?

Patrick Skelton 13-Feb-18 5:50am

Ooo! That fixed it! I've never had a huge amount of faith in repair options. Silly, I know, but historically I just seem to have had such a low success-rate with them, not just in VS but in many other applications. This time it worked. Sometimes the obvious suggestions are the best. Thank you!

I still don't have a .suo file though. Is that normal for VS2017?

Patrick Skelton 13-Feb-18 5:34am

Thanks for the answers.

WPF support is installed. I have just updated to the latest VS 15.5.6, but it hasn't fixed the problems.

Interestingly, the Solution doesn't have a .suo file, at least not anywhere I can find.

The nesting issue appears to be related to the way I fix my solution-level folders. Initially, .xaml.cs files are properly nested. Then I click 'Solutions and Folders' at the top of Solution Explorer, then click 'Show All Files', then click 'Show All Files' again. This gets my solution-level folders displaying correctly but un-nests the .xaml.cs files.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RickZeeland · Accepted Answer · 2018-02-13T00:39:00

Solution 1

Maybe run the VS installer and select "repair" ?

The .suo files have moved somewhere deep in the .vs directory ...

Posted 13-Feb-18 0:39am

RickZeeland