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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment