“Waiting for parse to complete” in Visual Studio 2013
One of my brilliant developers ran into an issue in Visual Studio 2013 when he opened a recent SharePoint project yesterday. There were several XML files in our InfoPath project opening so Visual Studio had to parse all of them. It showed “Waiting for parse to complete” along with a windows displaying that Visual Studio was loading solutions. After 15 minutes waiting for the process, we still couldn’t open the project to continue working. We then restarted Visual Studio and even virtual machine but this way didn’t work. There were a few threads in which people recommended installing Visual Studio 2013 Update 1 to avoid the issue. However, nothing happened after the update. We felt like we were sitting in the fire because the deadline was going to hit us.
We thought that we would have to figure out any XML editor add-ons against Visual Studio to speed up reading XML files. We couldn’t find any helpful tools though. We even found some tips to configure in Visual Studio to optimize its performance:
- Open Visual Studio Options, under Environment section, clear “Automatically adjust visual experience based on client performance”. Clear two beneath options as well. This is to reduce workload in visual experience that you wouldn’t need. This also saves memory up for another process.
- Open Visual Studio Options, under XML section, click Miscellaneous and clear Enter outlining mode when files open under Outlining setting.
We had a little hope after making some changes in Visual Studio setting. The issue, however, was still present. We thought that reinstalling Visual Studio would definitively solve it. Sometimes when you can’t fix something, re-installation is the only walkaround ultimately.
There had been an overnight improvement in the situation when we had figured out that if we closed all files somehow Visual Studio wouldn’t read to parse multiple XML files again. Going with that thought, we copied local mapped project to another location then remove mapping in Visual Studio.
In the Folder panel, right click on your project collection, select Advanced > Remove Mapping. Visual Studio will close all opening files before it removes your mapping.
Finally, we got the issue sorted out. It doesn’t look like a charm!
If you are to use this way, make sure you have a copy of local mapped project in another drive and remap into a different folder. If any changes in files locally that haven’t been updated into Visual Studio Online yet, you could copy all backup files after remapping. I’m not sure this way works because Visual Studio would auto generate numeric version progressively in some hidden files. If you remember what you have changed, simply compare backup version with the new one then make changes. You would need to open Visual Studio Online to track changes including some captures of modification date and time.
This is not really a wise walkaround to solve the issue. We just considered it for our specific case. It doesn’t address to solving technical problem. I strongly recommend you to get your great brain carefully considering this way before using it.
There are some helpful threads likely in relation to our issue: