Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0b5
Issue ID
837009
Regression
Yes
Can't compile some System.Net classes
To reproduce:
1. Open attached project
Observe the compile errors:
Assets/Test.cs(6,34): error CS0012: The type `System.Configuration.ConfigurationSectionGroup' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Assets/Test.cs(7,34): error CS0012: The type `System.Configuration.ConfigurationSection' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Assets/Test.cs(8,34): error CS0012: The type `System.Configuration.ConfigurationElement' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
These classes are not referenced in Test.cs. The classes actually referenced are, respectively:
System.Net.Configuration.MailSettingsSectionGroup, System.Net.Configuration.SmtpSection, System.Net.Configuration.SmtpNetworkElement
Reproduced on: 5.5.0b6
Not reproduced on: 5.4.1p1
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
FranzBr12
Jan 03, 2017 16:49
Same error still persisting in version 5.5.0p3
Any solution?