Search Issue Tracker
Fixed in 2018.2.X
Won't Fix in 2018.1.X
Votes
0
Found in
2018.1.0a1
2018.1.0f2
Issue ID
1041115
Regression
Yes
VS2015 cannot debug Unity project due to multiple assemblies with equal identity after swithching from .NET 3.5 to 4.6
How to reproduce:
1. Open user-submitted project (cannotdebug.zip)
2. Set Visual Studio 2015 as a default IDE
3. Open script "NewBehaviourScript.cs"
4. Debug the project via Visual Studio
5. Stop Debug session
6. Change project .NET version from 3.5 to 4.6
7. Open script "NewBehaviourScript.cs" and try to start a debug session again
Expected result: Unity successfully starts a new debug session
Actual result: Unity fails to start a new debug session due to multiple assemblies with equal identity being present in the project references
Reproducible with: 2018.1.2f1, 2018.1.0a1, 2018.2.0a1, 2018.2.0a8
Not reproducible with: 2017.1.0a6, 2017.1.4f1, 2017.2.0a1, 2017.4.4f1, 2018.2.0a9, 2018.2.0b6
Could not test with: 2017.1.0a1, 2017.1.0a5 (.NET 4.6 was not introduced yet)
Notes:
* Workaround - delete excessive references by hand
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Add comment