Bug 12021 – VS2012-2013 .vcxproj files don't show in the solution explorer

Status
RESOLVED
Resolution
FIXED
Severity
major
Priority
P2
Component
visuald
Product
D
Version
D2
Platform
All
OS
Windows
Creation time
2014-01-28T22:28:00Z
Last change time
2015-11-29T02:34:57Z
Assigned to
nobody
Creator
turkeyman

Attachments

IDFilenameSummaryContent-TypeSize
1319NoFiles.pngScreenshot showing the missing filesimage/png259865

Comments

Comment #0 by turkeyman — 2014-01-28T22:28:19Z
In VS1012 and 2013, if a solution has a .vcxproj and a .visualdproj (ie, C++ lib + D exe) in the same solution, the files in the .vcxproj don't display in the solution explorer. The folders still display, but they all have no files under them. If I: 1. Remove the .visualdproj from the solution 2. Save the soluition 3. Close and reopen the solution The solution loads properly showing all the files in the .vcxproj in the solution explorer. If I then: 4. Right-click solution -> Add existing project 5. Add the .visualdproj project back to the solution It adds back to the solution properly and the C++ project files all remain visible. If I then: 6. Save All (save the solution in this working state) 7. Close and repoen the solution The C++ project files are all gone again. Something about having a .visualdproj file present in the solution stops VS12-13 initialising correctly I guess?
Comment #1 by turkeyman — 2014-01-31T19:09:50Z
Created attachment 1319 Screenshot showing the missing files Here's a screenshot illustrating the issue.
Comment #2 by r.sagitario — 2014-02-09T14:13:26Z
I cannot reproduce this with VS2013 and small sample projects. Can you try to reduce your projects and see whether the problem goes away at some point?
Comment #3 by r.sagitario — 2015-01-01T22:19:37Z
Did this ever appear again?
Comment #4 by turkeyman — 2015-01-02T11:22:43Z
I haven't had contact with those IDE's for quite a while now, so I haven't been testing these cases. I'll close this, and we can revisit later if it comes up again.
Comment #5 by r.sagitario — 2015-11-02T19:43:46Z
Arrgh! I'm getting this with Visual D 0.3.43-beta1 and VS2015.
Comment #6 by r.sagitario — 2015-11-05T07:16:08Z
Turned out that this is caused by an unimplemented method in the automation model, that stops asynchronous loading of the C++ project in some intemediate state.
Comment #7 by r.sagitario — 2015-11-28T09:28:39Z
Comment #8 by turkeyman — 2015-11-29T02:34:57Z
Perfect timing! I just ran into this again about 1 hour ago... been trying to find a workaround since ;)