Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

10
  • 6
    +1. Very unfortunate error message -- it's actually most likely to arise when you've moved the files the "correct" way according to your SCC provider. (e.g. using 'tf rename' for TFS) Moving the project on disk w/o telling TFS, or forgetting to update a sln/csproj file, will result in different error messages in my experience. SUO files are opaque so you're left scratching your head until you do a tfpt treeclean / scorch. Commented Feb 26, 2010 at 20:32
  • 45
    Don't forget to restart Visual Studio after deleting the .suo file
    – orandov
    Commented Jun 11, 2012 at 13:45
  • 9
    Oh. So now the .suo file is hidden. Why? Oh, I know why. We are developers and are obviously not capable of handling the added complexity with seeing the .suo file out in the open ;-) Commented Aug 24, 2012 at 9:06
  • 30
    This also works in Visual Studio 2015, though the path to the .suo file has changed to <SolutionFolder>\.vs\<SolutionName>\v14\.suo.
    – Greg M.
    Commented Aug 31, 2015 at 14:22
  • 4
    I'm also using VS 2015. As Greg M. noted, the SUO file is now in a hidden folder called .vs within the solution folder. I was able to fix the error by closing VS, deleting the entire .vs folder and reopening VS.
    – ckkkitty
    Commented Jul 6, 2016 at 17:34