Search Issue Tracker
Fixed in 2018.4
Votes
0
Found in
2018.4.14f1
Issue ID
1205800
Regression
Yes
[Visual Studio] SyntaxTree namespace cannot be referenced when using 2018.4.14f1 and above
How to reproduce:
1. Open the user's attached project ("SyntaxTree.zip")
2. Open the 'Editor\ProjectFileHook.cs' script
3. Notice that 'SyntaxTree' namespace is not accessible
Expected results: SyntaxTree is accessible
Actual results: SyntaxTree namespace is not accessible
Reproducible with: 2018.4.14f1, 2018.4.17f1
Not reproducible with: 2017.4.36f1, 2018.4.13f1, 2019.2.21f1, 2019.3.1f1, 2020.1.0a22
Workaround: Manually importing VS Tools package fixes this issue ("Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Visual Studio Tools for Unity" and double-click the "Visual Studio 2017 Tools.unitypackage")
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
- Duplicating a Prefab instance in the Scene will cause instances of the same Prefab to be disabled and re-enabled
- GUI.Button and GUILayout.Button stay in the normal GUIStyleState even when the normal GUIStyleState is changed to another one
- Particle System mesh UV coordinates change when mesh's geometry layout is changed on import
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
Resolution Note (fix version 2018.4):
Manually importing VS Tools package fixes this issue ("Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Visual Studio Tools for Unity" and double-click the "Visual Studio 2017 Tools.unitypackage")
No longer reproducible on 2019.2.21f1, 2019.3.1f1, 2020.1.0a22
Resolution Note (fix version 2018.4):
Fixed in 2018.4.23f1