Unity Personal (64bit) 5.0.1f1 and Microsoft Visual Studio Community 2013 Version 12.0.31101.00 Update 4, .Net Framework Version 4.5.50938
Long story:
Preferences are set to use Visual Studio 2013
Double clicking a .cs file in the Unity Project opens Visual Studio.
However, in VS, I cannot debug Unity. It does not say Attach to Unity, it just says Start.
If I try Asset->Sync MonoDevelop Project, it (sometimes) says “Opening Visual Studio”. Whether it says that or not, it always opens MonoDevelop.
In Visual Studio, if I try DEBUG->Attach Unity Debugger, it only shows Unity processes on other people’s machines, not mine.
If I try DEBUG->Attach to Process… and choose Unity, breakpoints are disabled because symbols can’t be loaded.
If I try Preference->External Tools->External Script Editor->UnityVS.OpenFile with args set to “$(File)” and double click a .cs file, it opens Visual Studio, but VS complains it cannot file UnityVS.project_name.sln, which doesn’t exist, only project_name.sln exists.
If I try Assets->Sync MonoDevelop Project while using UnityVS.OpenFile, Visual Studio opens and complains it can’t find \project_name.sln\UnityVS.project_name.sln.sln, which doesn’t exist, and why in God’s name would/should it?
Short story:
None of this seems to work as intended. Anything I can do to fix it?