When I install Unity I've been installing from my non-admin account, but when UAC prompts I'll select the admin user and enter the password, not sure if there are known issues with that (that's how I install all of my software, never had problems except with old/legacy apps not designed for Vista+/UAC).Įdit: Looks like the BAT file trick mentioned here got my SLN files created at least, guess I'll just live with that. Guess I'll try changing my account to admin and reinstall yet again, see if that helps, but I can't leave it that way. I do run using a non-admin account, under Win8, as is recommended by Microsoft for security reasons and because this is a family/shared PC. I've tried running Unity with elevated permissions (UAC), and without. and I don't even care if I can't open it from Unity, but how do I at least get Unity to build the solution file? I've tried reinstalling Unity with and without Mono installed, same thing either way, and I've tried changing the preferences in Unity to Mono Develop, then back to Visual Studio 2012, and also tried using the Browse. Checked the registry settings under HKEY_CURRENT_USER\Software\Unity Technologies, and the path to the script editor is correct (points to devenv.exe), I even tried changing the / to \ since I'm on Windows not Mac/unix, no luck. No errors in the Unity console or otherwise, very annoying. Selecting "Sync Mono Develop Project" in Unity, or trying to open any CS files just flashes the MonoDevelop splash screen for half a second then "nothing happens".
VISUAL STUDIO FOR MAC WONT OPEN PRO
I've tried uninstall + reinstall of the latest version of Unity, and I already have VS 2012 Pro installed, and still same problem. After that, double clicking any scripts or double clicking any errors will work as expected. suo trick (double click a script file, close mono develop, close unity, open the sln file with VS2012 Pro, save so the suo file is generated, start Unity, now double clicking works) as it only requires me to generate the suo once (given I don't delete it) and only have to open the project with Visual Studio before I want to access any code with it. Uninstalling the redundant versions so I only have 2012 Pro, and resetting the editor preferences to point to my single install of VS 2012 Pro is not enough.
If it helps anyone find a pattern, my background is that I have installed/uninstalled several versions of Visual Studio (Express/Pro/2010/2012) and at some point it got borked. suo file generation worked only as long as Visual Studio already was running, but it jumps to the correct line in the correct file. bat file works - but when double clicking a log entry for a compile error, it will only jump to the file but not the correct line in the file.
0 kommentar(er)
