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
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Resetting Quality Levels in Project Settings adds new Quality Levels instead of restoring default ones
- UI builder uxml files retain reference to non-existing assembly definition file when a assembly definition file is deleted
- Animator Entry and Base Layer Transitions links to the documentation aren’t working
Add comment