Can't open project property in visual studio 2015 with Unity 5.3.2

Question

I can't open project property in visual studio 2015 with Unity 5.3.2 So I can't edit build flags. When I hit Alt+Enter in solution explore, project property windows blink shortly and closed immediately. I worked fine with Unity 5.2.1 Anyone with same issue?

Answer 1

Answer by Venryx · Aug 14, 2016 at 02:54 AM

Found out the fix!

You have to enable the "Access to project properties" option in the Tools>Options>Tools for Unity>General" section.

Then just restart VS, and it should let you open the properties panel.

40 Show 6 · Share

alliequintano · Sep 02, 2016 at 05:56 PM 0

Share

Thanks for sharing, but I don't see the "Access to project properties" option there. I am using Unity 5.4 / VS 2015.

Venryx alliequintano · Sep 02, 2016 at 06:47 PM 0

Share

Odd. I'm using the same, and it shows for me: http://i.imgur.com/2ByN8co.png

My "Visual Studio Tools for Unity" version is 2.3.0.0, btw.

And my Visual Studio version:
Microsoft Visual Studio Community 2015
Version 14.0.25425.01 Update 3
Microsoft .NET Framework
Version 4.6.01586
Installed Version: Community

Ultroman · Jan 28, 2017 at 02:28 AM 0

Share

The fix doesn't seem to work with newest Unity / VS2015.

OneLemon · Mar 10, 2017 at 09:42 PM 0

Share

For anyone that still can't get it to work after applying this fix, update your VS 2015 to version Update 3 and that should fix the issue.

BeatMicrosoft · Apr 08, 2018 at 10:18 AM 0

Share

very thanks man,i slove this problem in vs 2017,,and maybe slove a add dll reference question too.

Zacryon · Jul 07, 2019 at 02:47 PM 0

Share

This fixed it for me as well. Using Visual Studio Community 2017 15.9.13 with Unity Tools and Unity 2019.1.3f1.

Answer 2

Answer by awwwwjay · Apr 06, 2016 at 08:27 PM

I'm having the exact same issue, from visual studio I try to access a project's proeprties vis Project->Properties, the IDE blinks white for a split second, probably loading the properties page, then instantly shuts.

I have a hunch the Solution file Unity is generating is well, invalid somewhere.

6 Show 2 · Share

matt_icejam · May 16, 2016 at 12:56 PM 0

Share

Do you have any hunch as to what could be causing the issue in the sln file?

I ask because the use case I have only seems to require me to enable a property for a single run, and the .sln file is only 32 lines. I wonder if it could be fixed by hand for this use case.

I realise that it's far from an ideal solution.

Venryx · Aug 14, 2016 at 02:55 AM 1

Share

Found fix. See my answer.

Answer 3

Answer by JayParikh · Nov 02, 2016 at 01:24 PM

Found the Fix! for VS 2015 Its Same As Venryx.

Go to Tools > Options > Tick "Show All Settings" (Bottom Left) > Search For Unity (Optional) >Tools For Unity > General > Access to project properties = true

3 Show 1 · Share

hydrix · Dec 03, 2017 at 12:08 AM 0

Share

worked on Visual Studio 2017! It also hid the "add reference" dialog when you right click references.... Me: searches for hammer for 3 hours... finds it under pile of rocks.... Unity: "Oh yeah, we hid that under this pile of rocks because we want you to use the nail gun." ME: WHYYYYYY and AT LEAST TELL ME adsfwefqa lol

Answer 4

Answer by Zoogyburger · Mar 11, 2016 at 06:20 PM

Apparently Unity5.3.2 is not compatible with Vuforia? 5.3.1 https://developer.vuforia.com/forum/unity-extension-technical-discussion/unity-532-and-vuforia

Patch http://unity3d.com/jp/unity/qa/patch-releases/5.3.1p3

However, when the Unity 5.3.1f1 check, so an error or have a crash often I think that the patch is good. Details: http://unity3d.com/jp/search?gq=Unity%205.3.1p3%20patch

0 · Share

Answer 5

This is still an issue as of 5.3.4f. Assuming you want the XML file for use with Sandcastle or other documenting programs, I've found a workaround that appears works.

Open the Unity-generated .csproj file.
Build. This should create bin and obj folders in the Temp folder under your Unity project. Your project must not be open in Unity for this to work, as Unity typically deletes Temp upon closing.
Copy the DLLs and XMLs generated, such as UnityEngine* DLL, XML. Personally I copy these to separate folders since Sandcastle doesn't seem to compile with the DLL references.
Make a new C# Console program.
Add the DLLs to the Console project's references (in the Solution tab).
Copy your Unity scripts to the project (you can Add Existing Files/Folder to import).
You can now properly set the XML Building preferences in Properties.
Build this Console program. It should build fine.
In Sandcastle, hook up the Console project's EXE, XML, and CSPROJ along with the Unity-generated XMLs.
Build the Sandcastle documentation.

This should produce the desired Documentation.

Can't open project property in visual studio 2015 with Unity 5.3.2

9 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions