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
- Crash on SpriteAtlas::PopulatePackedTexturesAndRenderData when changing Import Settings on a Sprite that has been added to a Sprite Atlas while in PlayMode
- Empty lists can be applied in Additional Compiler Argument list in Project Settings
- [Vulkan][OpenXR] SRP Foveation Regions Not Centered when eye-tracking is not used
- Long Color Library name overflows outside input field bounds
- Shader Graph validation and Metal threadgroup memory warnings thrown when installing HDRP package in Universal 3D Template
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