Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a6
Issue ID
1016929
Regression
No
CompilationPipeline.GetAssemblyNameFromScriptPath returns the wrong assembly name when you pass in the true path to a script
How to reproduce:
1. Open the attached project
2. Open the Test Runner
3. Run the 'NewTestScriptsimplePasses" test, it fails
Actual result: CompilationPipeline.GetAssemblyNameFromScriptPath("Packages/test-cs@0.0.2/Test.cs") returns string "Assembly-CSharp.dll".
Expected result: CompilationPipeline.GetAssemblyNameFromScriptPath("Packages/test-cs@0.0.2/Test.cs") should return "test-cs.dll".
Reproducible with: 2018.2.0a6, 2018.1.0b12, 2017.4.0f1, 2017.3.2f1.
Notes:
Couldn't test 2017.2 and less because CompilationPipeline namespace doesn't exist.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment