Strangest thing happened today, I have it set to open in VS 2010, then while it was opening a file, it opened up in the default editor that comes with Unity on Windows, AND it launched VS 2010 but froze trying to open the file. I have no clue how to duplicate this issue, not sure if anyone else has experienced this problem, so not sure if it is a bug or a default behavior if VS doesn’t open in XX amount of time to open in default editor. So this might be a natural design of Unity 3. Once I closed both the Unity editor and VS 2010, then tried to open the CS script again, it opened up fine in VS 2010, the delay happened when VS complained about the line endings to fix, while that dialogue window was opened, the internal Unity editor then opened. Was wierd.
Beta 6 uses a separate preferences file than previous betas (and 2.x, natch). The idea being that it will be easier to have 3.0 and 2.x installed side-by-side so you can finish up 2.x projects in that editor and new projects in 3.0 without worrying about accidentally “upgrading” your 2.x projects. The downside is that you’ll need to reset all your editor prefs in beta 6 (default external programs, keys, colors, etc).
Oh, and having a new editor prefs file clears your recently opened projects in the beta 6 project selector as well, which you’ve probably noticed.
Fair enough, but this is after I had reselected my editor type, so not sure how this relates but it is good to know for anyone installing U3B6. I always check my settings when I install any new beta builds. Who knows, maybe some wierd behavior between B5 and B6, something goofy in general.
BAH it happened AGAIN!
This time I was able to capture the error, here was what I did, I opened up Unity, switched projects by using “select other”, opened up a different project, double clicked on the CS script file, and BOOM!
UniSciTE editor opened instead of Visual Studio, and the editor showed the following error:
Things to note, in THIS instance, I already had VS2010 opened up (last time I did not have it opened up prior to the problem). Here is the screen shot showing the error and at the bottom shows some line number in Unity code.
Now, my next step that fixed this the last time, I am going to close out of the Unity editor, go back in and see if it loads normally.
See video:
http://screencast.com/t/YjlkNjNhYzUt
The only thing that fixed it this time was to drag the CS file from the folder I had it in, into the root of the assets folder, then it would open in VS 2010, otherwise it would ONLY open in 2008, once I did the drag then dragged it back into its original spot, then it opened just fine in 2010.
This problem still persists with b7. I have a fresh installed VS2010, I have selected VS2010 as my external editor. I have restarted Unity (to be sure that the settings are saved etc).
Whenever I double click onto a C# file, I get the error: “Couldn’t call method SyncVisualStudioProject because the class SyncVS couldn’t be found. […]”.
Definitely something odd happening. Do you have a case number for this?
Hi,
I quickly posted a bug report (Case 373281) 
Still present in f1. On a clear install (completely reinstalled machine).
Case #374703
Hi everybody !
I find some manipulation to fix this problem.
Right click on the Project tree → Use Sync MonoDevelop Project
Then you could edit your code with visual studio 2010.
This has been tried by those who are using VS on a day to day basis and does not work… I finally switched back to VS2008 which works without a flaw…
Have you seen this:
http://forum.unity3d.com/threads/62200-Visual-Studio-2010-issue?p=409312&viewfull=1#post409312
This workaround worked for me, though the issue really needs to be fixed.