I remember this having inline documentation for the Unity APIs, but it seems to have disappeared in a recent version. Any chance you guys could bring it back?
Otherwise this is a fantastic tool.
EDIT: By inline docs I meant when intelisense makes suggestions. Like the docs VS picks up from XML files. Sometimes it appears, sometimes it doesn't, and recently it started appearing again so that's good I guess. Even still a lot of the methods don't have it. But maybe you guys could polish that up somehow so it's more reliable. Maybe pull the docs from the Unity manual pages?
Giving this 3 stars for the moment as after upgrading to the new version I keep experiencing Crashes in Unity. If I downgrade and install the 1.8.2 it is fine. If this can get resolved I will change to 5 stars as all the new features are fantastic. I really like being able to start debugging right from VS and having it start the project in the Unity Editor (as long as it doesn't hang).
The hang seems to happen after you have started the project once and then you are trying to start it a second time.
EDIT: After the update all seems to be well. Not getting any hangs any longer and 0 crashes. Sorry would have updated earlier but have been extremely busy with work and multiple projects for clients. Good problems to have.
As announced for the 1.9.0 release, C# being the predominant language in the Unity ecosystem (the new Sample Assets are in C#, the Unity documentation will default to C#), we removed our basic support for UnityScript and Boo to better focus on the C# experience. As a result, VSTU solutions are now C# only.
That's being said, you can have breakpoints in your C# files, then step into .js files and still be able to inspect variables.
I've owned the tools for a well over a year now, worth every penny! Now that they're free, there's nothing stopping a wider audience from enjoying the same. Keep up the good work! Can't wait to see what the next releases will bring...
The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Int32' for method 'System.Web.Mvc.ActionResult Details(Int32)' in 'MvcAppln_Crud.Controllers.EmpController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Parameter name: parameters
Using 220.127.116.11 for VS 2012, I can Open C# Project from Unity, and it opens the generated solution in VS correctly. Now if I add a new script in Unity and switch over to VS, it asks me if I want to reload the project. If I agree, then Unity.CSharp will be unloaded and I cannot reload it. I now have to close VS and reopen it from Unity to make it work.
Yes this issue is related to the opening mechanism now used by Unity with the native integration. We are working on this.
As a temporary workaround, if you open the solution directly with Visual Studio (do not rely on Unity to open VS first), you should not hit the issue anymore, even if you open or add a file from Unity after.
Sebastien Lebreton [MSFT]
InvalidOperationException: Operation is not valid due to the current state of the object
System.Linq.Enumerable.First[CompilationUnit(IEnumerable'1 source, System.Func'2 predicate, Fallback fallback)
I got this error message when I try to generate Project files. I searched reason and I found something.
I guess, Other plugin(NOT vs-tool) has 'editor' folder as child, Unity3d shown error message and If i change folder name (of other plugin) to another name (such as Editor2.. anything). Error message is gone.
And there is another conditions. there is no error on version 1.9.0 and 1.9.1.
However on lastest versions .. happens this error.
I just downloaded and installed the 18.104.22.168 version of UnityVS. Now, i just can't debug anymore, the debugging process seem very instable.
What occur very often is that the debugging functionnality work the first time when you launch Unity and Visual Studio. Then if you try to attach a second time Visual Studio for debugging, Attach will succeed but if i press play in Unity, Unity will totally crash, with the Fatal Error Submitting window on the screen.
Since, i can't debug my code anymore.
I reversed back to 22.214.171.124. Everything work like before, but it seem that i can't use the Android Debugging functionnality now on 126.96.36.199 (188.8.131.52 was working to detect that).
I'm using Unity 4.5.3.
Thanks in advance for your support.
Everything was working fine until today when I allowed VS to upgrade the UnityVS extension to 184.108.40.206 ( I assume that was the update ) and all my project files in the solution became incompatible.
"UnityVS.FallingLetters.CSharp.csproj: The application which this project type is based on was not found"
I have uninstalled UnityVS and re-installed plus removed it from my Unity project with the same result. ( and deleted all the project files )
I'm currently installing VS2013 to see if it works there but I'd prefer to have it working in all verisons
Can you delete all UnityVS* files (*.suo, *.csproj, *.sln) from the root folder of your Unity project, and recreate them from Unity (using the menu Visual Studio Tools -> Generate Project Files) ? Hopefully that should fix it.
I'm using the VSTU with the new Unity 4.6 beta. There are now a new DLL to be deployed to UnityAssemblies folder: UnityEngine.UI.Dll. Without it, there will be a reference error in the generated VS project.
I was able to fix this manually (getting the missing dll from [Unity install folder]\Editor\Data\UnityExtensions\Unity\GUISystem\4.6.0\Standalone) and copying it to ([Unity project folder]\Library\UnityAssemblies) but it will be awesome if you could release an updated version of this extension.
I've updated to 1.9 and it seems pretty unstable compared to 1.8.2. I've seen some of the reviews commenting the same thing and one of the responses is to report bugs at the Connect website, but that website doesn't seem to work for me (at least on Chrome)
The three main broken pieces I've found so far:
1) attaching to already playing instance will lockup Unity
2) setting a breakpoint while player is running will block in VS
3) watch is broken
There are also several bugs that I've previously reported from earlier versions that are still not fixed. Some of these I thought would be fixed in 1.9, but they are not, and not sure what the ETA is. Also, there was an interchange of ideas resulting in good solutions for these, but I don't know if that's been lost in the acquisition.
4) console logging does not work
5) [DebuggerDisplay] does not work
6) Project Inclusions/Exclusions are not user friendly
What can we do to get the stability issues addressed, and to resolve some of the older defects and suggestions?
Connect is the preferred way, but you can also send this as an email to vstusp AT microsoft.com
We already fixed some issues in the upcoming 1.9.1. But i want to check more about "3-watch is broken".