Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
3.0.7
Issue ID
RIDER-14
Regression
No
Rider creates inaccessible project references
How to reproduce:
1. Extract the attached project named "case_1324901-Mirage.zip"
2. Open Mirage.Editor.csproj using Rider
3. Expand the Dependencies tab and check the Projects folder
Expected results: Generated project references can be interacted with
Actual results: Generated project references are not accessible
Reproducible with: 2019.4.28f1(1.0.2), 2020.3.12f1(2.0.7), 2021.1.11f1, 2021.2.0a20(3.0.7)
Could not test with: 2018.4.35f1(Rider package was not available)
-
citizenmatt
Oct 12, 2021 14:34
Hi. Can you provide some more details, please? What do you mean by "interacted with" and "not accessible"? I'm not sure what you're expecting to happen. The project dependency nodes in the Solution Explorer view can be right clicked, and you can view properties, delete, find dependent code, navigate to the actual project in Solution Explorer and so on. You can also right click on the Projects node itself and add more project references.
However, please note that generated projects are not expected to be edited by users, as the next time something changes in Unity, the project files will be regenerated and any changes will be overwritten. So any changes made - adding or deleting a reference, for example - will be lost with the next change made in Unity.
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
- Asset Database warning is being logged continuously when creating a script in an embedded package
- Build process only shows Initializing when building for Android
- TileMap Palette preview flickers when scaled
- Shader Graph Blackboard "plus" sign is not centered within the button
- [URP] When Rendering Layers are enabled, the DepthNormalPrepass is enabled even if not used
Resolution Note:
Issue is being investigated as RIDER-95929 by JetBrains