Search Issue Tracker
Fixed in 2017.2.X
Votes
1
Found in
2017.1.0b1
Issue ID
902369
Regression
No
Namespace collision when using static directive and enum types with .NET 4.6
Reproduction steps:
1. Open project attached(New Unity Project 3.zip)
2. Inspect console.
Expected result: There will be no error and compilation will succeed.
Actual result: Errors appear:
Assets/UsingStatic.cs(14,23): error CS0023: The `.' operator cannot be applied to operand of type `method group'
Assets/UsingStatic.cs(15,24): error CS1061: Type `int' does not contain a definition for `Up' and no extension method `Up' of type `int' could be found. Are you missing an assembly reference?
Note: Investigate scripts "CodeFile1" and "UsingStatic" for more information. According to user, it is a valid 4.6 code. Removing "using static TestClass;" makes it work as expected.
Reproduced on: 2017.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment