A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
From your description it does look like the update somehow went wrong and the Tools for Unity are indeed not registered with Visual...
We've updated the gallery with VSTU 22.214.171.124 for Visual Studio 2015 with the fix.
Yes, we're going to service our release for VS 2015 as well with the fix.
That being said, we strongly encourage you to switch over 2017, as...
We've fixed this in our latest servicing release of Visual Studio 2017 (version 15.8.5, comes with Visual Studio Tools for Unity 126.96.36.199), which...
Sorry about the inconvenience. We've been unable to reproduce locally, but with the help of a few customers we've been able to find the...
Make sure you're up to date with VS 2017. You'll need to have at least the 15.6.4 version to properly handle the changes of Unity 2018.
Thinking about it, another thing would be for you to request that Unity generates the csproj at the same location of the asmdef.
Ah I see what you mean.
Yeah we're currently working on revamping our project system based on the modern C# project system (we're currently using...
Why don't you simply use the Unity project viewer in VS? (View -> Unity Project Explorer). That will give you the project using the Unity folder...
188.8.131.52 will be available for Visual Studio 2015 and Visual Studio 2017.
FYI, the support for the project generator in Unity 2018.1 is scheduled to be released in Visual Studio 15.6.2, on or about this week.
I sure would like bi-directional support for csprojs, but it also sounds like a lot of work for Unity.
You should let them know, wink wink.
Thanks folks. I'll need to reach out to my core team to help investigate this, and I'll get back to you.
At this point I can’t even. We’re just trying to help users and be productive.
What’s with the attitude, Laurent?
I'm afraid filing Visual Studio bugs at Unity is completely unproductive for everyone involved.
For Unity it increases their QA workload instead...
Quick question: are you starting the debugger without a project loaded?
And of course I can't repro :(
Which version of Unity + VS are you using?
We've heard about this, but we've never been able to find a consistent repro. Do you folks have a project + method to consistently reproduce this?
I'm not exactly sure what I'm looking at. Are those Unity bug numbers? If so, I don't have access to those.
Are those bugs related to Visual...
You can wrap the script in a:
Let me check with my Intellisense people about code completion for compilation symbols.