Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.0b8
Issue ID
965865
Regression
No
Unity generates wrong Visual Studio solution
To reproduce:
1. Create a new project
2. Create a C# script
3. Make sure that the External Script Editor is set to Visual Studio 2017
4. Open the script
5. Rename the script in Unity to anything else
6. Re-focus Visual Studio and it should prompt to reload the solution press "Reload Solution"
7. In the solution explorer Press Assets > on the script that you renamed
8. Observe the output as it states: [Failure] Could not find file 'C:\Users\"project loaction"\965865\Assets\NewBehaviourScript.cs'.
Notes: there is a workaround by deleting .vs folder in the project folder. Tested on .NET3.5 and .NET4.6 same result.
Reproduced on: 5.4.6f2 5.5.5f1 5.6.4f1 2017.2.0f3 2017.3.0b9 2018.1.0a4
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Resolution Note:
This is an issue with Visual Studio / Visual Studio Tools for Unity (VSTU). Please report the bug to VSTU team at vstusp@microsoft.com