Search does not work any more.

MiloslavBeno

Hi guys,

I think I can reproduce it as well now - in the new PHP project type. I will try to find out more. So far, it seems just stuck at:

SteveA The fast way to know if it's a legacy project is to take a look in the Solution Explorer. If you see References under the project name, it's a legacy project. If you see Dependencies, it's the new one.

SteveA

MiloslavBeno and @JakubMisek Updating to the newer format seems to have fixed the problem for me. Indexing the new project took less than 30 seconds and search seems to be working. I've only tried this on one project, but my fingers are crossed.

BarryHarrington

Thanks guys! I updated the PHP project and all is back to normal. I am able to search across the project now.

JustJoe

Thanks a lot! I can confirm that this now works. The solution is to migrate the PHP project to the new project format. When using the old format, the indexing will run for ever. Thanks again! :-)

JakubMisek

Thank you all for the confirmation;

FYI, The New Project is significantly faster, so Visual Studio is able to index files faster, and search sooner :-) It's still an issue in VS itself though.

MiloslavBeno

Great, Thank you all!

I've also updated to 17.5.2 and I'm no longer able to reproduce it either on the new project or the legacy one. So it seems we can close this one.

UPDATE: The legacy project only works if the same folder was opened as the new project first. Otherwise, the issue persists. It basically means, the legacy project shouldn't be used since VS 17.5.

« Previous Page