Visual Studio hangs on running project

I am running Visual Studio 2015 on an Azure VM running Server 2012 R2. I have been designing an MVC project for a while with no problems. Recently VS has started to hang intermittently after I Ctrl+F5 to run the project. Sometimes VS stops running the project all together.
There are no breakpoints or build errors, and the problem arises before VS gets to any of my code.

I guess the problems are VS related but I have no idea how I would begin to locate the problem! Any suggestions?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Does the problem persist after rebooting?

There's a VS collector process that runs in the background and can grow out of control. It eventually sucks up memory after a while (mostly commit) and can cause weird behavior.
John TsioumprisSoftware & Systems EngineerCommented:
How about copying the project to your computer..if something in the VM is blocking your project then on your computer should run fine...
If it has the same behavior then probably an error that you probably chose to ignore is causing conflicts an eventually crashing VS
Hi ,

In the solution folder there is a hidden folder ".vs" ... try deleting it and re-open your solution.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
If there's no indication of whose comment actually pertained to the solution and we're closing the question then I'd recommend splitting points evenly.
kaizenproAuthor Commented:
Unfortunately I had to restore the VM to a backup pre-problem. I have since copied (post-problem) code and the problem has gone. Not the solution that I was looking for and it has cost me significant time, but it has worked.

Your input was much appreciated.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Visual Studio

From novice to tech pro — start learning today.