UPDATE - *** 10/11/2014 - Now using 1.9.2 of the extension with 4.5.4 of Unity and I can hit breakpoints again, thank goodness. Sebastien, thanks for the hard work.
If I discover any weirdness I'll be sure to let you know ;).
Have been using UnityVS for years, surprise, the first version after their acquisition from Microsoft (1.9) freezes Unity entirely and crashes Visual Studio 2010.
Initially tried the migration instructions - crash. Tried removing UnityVS from my project completely, then adding it back - crash. Tried completely uninstalling UnityVS from machine, removing entirely from project, clearning, rebooting, re-downloading, re-installing, re-importing, CRASH...
Where can I download the old UnityVS 1.8 ?(used to work great). I updated to last version which I painfully regret.
Crashes on every breakpoint. Repro: - New Unity project, add monobehaviour script. - Open the script in VS, add Debug.Log("blabla") in OnUpdate, attach unity debugger, - Run Unity - add a breakpoint on said line, watch it crash.
Microsoft connect does not have a project with "Unity", "Visual Studio 2010 Tools for Unity" or any subkeyword.
When it works it's nice but it crashes Unity a lot. Here's a 100% reproducible crash for me: 1. Open a source file that's used in the scene in Visual Studio 2. Edit that file. Press Save. 3. Press Debug. 4. Go to Unity - it has crashed while compiling.
I wanted to use VS to debug my unity project.
I imported the VS Tools in Unity and reloaded my Solution in VS.
However, when I press "Attach to Unity" the play button becomes grey for a moment and then green again without attaching and without any related output.
Where can I download older versions of Visual Studio 2015 Tools for Unity to try them out?
I confirm that VSTU 2.2 is working with Unity 5.3.5f1. I just manually tested it with VS 2010 and we have a full automated test suite, running every day, to ensure that everything is fine.
- You don't need to import the VSTU package in Unity anymore, because now we provide a native integration: check this website for more information:
- Seems like a timeout issue, can you double check that both Unity and Visual Studio are able to properly communicate ? (firewall, AV rules). We use TCP for connecting to the debugging layer and UDP for a custom message based communication with the Unity editor.
Sebastien Lebreton [MSFT]
Hosnkobf just uninstall xamarin extension in your VS 2015 and you will be able to debug through VS.
i am installed VS 2015 community only with unity tools and everything work fine, then i installed all other extension and catch problem with press attacj and nothing happens.
resolution: uninstall xamatian it might help.
Indeed, we found that when both VSTU and XamarinVS are installed, we cannot connect our debugger to the Unity process.
Hopefully we fixed this and we will release very soon a new VSTU version.
As a temporary workaround you can uninstall XamarinVS.
Sebastien Lebreton [MSFT]
I really like the Native VSTU, but I'm having trouble loading a project from Unity while Resharper 9.2 is enabled.
When I open VS 2013 on it's own, disable Resharper, Open Unity and Open C# solution, everything loads fine. It's a workaround for now, but I was hoping there might be a solution.
I've encountered an issue in visual studio where only some of my classes cannot be navigated to via ReSharper. I've posted a question in their forums about this already, but I just discovered that all of the classes (actually, it looks like it's the files they're in, not the classes themselves) affected are contained within folders that have an incorrect icon in the Unity Project Explorer window. (See "DevIL", "General", and "PartsDoll", in the below image)
Also note that the files/folders underneath the affected folders are missing icons altogether! I suspect that whatever it is that's affecting these folders is the cause of my problems with ReSharper being unable to navigate into the files contained within them.
So I ask: What is it that would decide to give a folder that "document" icon instead of the folder icon? If I can fix this, I suspect my woes will be gone~
After some back-and-forth with Sebastien via email, we've discovered that the problem comes from a corrupt Extensions Filter setting in VSTU.
Specifically, the first entry, which should appear as ".xml;" was appearing like "l;" in mine, which was causing all folders with a "l" in their names to exhibit this problem.
Resetting my Extensions Filter to the default ".xml;.shader;.cginc;.glslinc;.txt" fixed this issue for me.
What is the right way to do this. Everytime Unity regenerates the project files, The projects loses all source control bindings, causes the user to have to rebind the project. Is there some way to avoid this?
We are working on this. As a workaround you can use our file generation API hook to persist SC bindings. Add and customize the following file in an editor folder:
No it is not compatible with Express editions.
But since November 12, 2014, a new free Visual Studio edition is available, and VSTU is compatible with it.
This is a great product!
However all is still not well in Unity+VS land:
Do you guys think it would be possible to fix the issue with Unity removing .resx and .tt files from the solution every time you tab into unity (and the solution files gets overwritten)?
Just thought I would ask as I would REALLY appreciate it if such a feature was doable!
Having to re-add these files several times a day is truly an irritating and unproductive chore! :(
...with UnityVS and Unity crashing. I can pretty much predict when it is going to happen.
When everything is working fine I will make changes in VisualStudio, build, and a half second later I can see the Unity console window display that Unity detected a change and is building on its side.
When I know that VisualStudio is going to crash on a breakpoint is when I make a change in the code in Visual Studio, build, and Unity DOES NOT react to this occurrence. The, guaranteed, it crashes right when it gets to the breakpoint.
This might be a Unity issue, I'm not sure, but for some reason Unity doesn't realize that the files have changed and this leads - ALWAYS - to a crash if a breakpoint is set.
This doesn't solve my "hang on startup" issues; however, I have mitigated them by not using a networking resources for 3 seconds after startup (the editor seems to have resource contention issues if you use the network to soon after pressing play.)
Thanks Sebastien, looking forward to the update.
VSTU is a critical resource as I find myself using Unity for more and more things outside of gaming projects (e.g. https://www.youtube.com/watch?v=cJj7p4FhC_k#t=19 )
I am building dashboards for middleware and backend server products, and other complex interactions. Being able to step through is a HUGE timesaver.
Thanks for the update! I am getting frequent periodic freezes in visual studio, where it will lag for multiple seconds randomly. Is there an easy way to profile Visual Studio to see what's going on? Maybe a log for UnityVS that would be useful?
Jeremy, i saw for months lots of comments about this behavior related to antivirus programs. Unity3D is putting a lot of I/O pressure on project files. Can you try to setup an antivirus exclusion for your project + devenv instance + Unity executables ? Then retry after restarting Unity & VS. Same thing can happen if you use encrypted files for your project (files in green in your windows explorer).