Universal Windows Platform: Missing .NET Types on .NET Scripting Backend

The .NET scripting backendA framework that powers scripting in Unity. Unity supports three different scripting backends depending on target platform: Mono, .NET and IL2CPP. Universal Windows Platform, however, supports only two: .NET and IL2CPP. More info
See in Glossary that is used on Universal Windows Apps is a special .NET version for this platform, which is not entirely compatible with Mono. In particular some data types are missing and some other classes don’t have certain methods, that the same classes do have in Mono.

To make porting existing games to Universal Windows PlatformAn IAP feature that supports Microsoft’s In App Purchase simulator, which allows you to test IAP purchase flows on devices before publishing your application. More info
See in Glossary easier, some of the missing .NET types are provided by Unity. In addition some extension methods and replacement types were added to make migration easier. These types are placed in PlaybackEngines\metrosupport\Managed\WinRTLegacy.dll.

Types, provided by Unity include:

• System.Collections.ArrayList
• System.Collections.Hashtable
• System.Collections.Queue
• System.Collections.SortedList
• System.Collections.Stack
• System.Collections.Specialized.HybridDictionary
• System.Collections.Specialized.ListDictionary
• System.Collections.Specialized.NameValueCollection
• System.Collections.Specialized.OrderedDictionary
• System.Collections.Specialized.StringCollection
• System.IO.Directory
• System.IO.File
• System.IO.FileStream
• System.Xml.XmlDocument
• System.Xml.XmlTextReader
• System.Xml.XmlTextWriter

In addition to these a namespace WinRTLegacy is added to provide additional classes and extention methods. Among there are:

• Extention methods Close() for most System.IO classes (alternatively you can use Dispose(), which is available on both Mono and .NET for Universal Windows Platform)
• WinRTLegacy.TypeExtensions has methods GetConstructor(), GetMethod(), GetProperty() for System.Type
• WinRTLegacy.IO.StreamReader class, that is compatible with Mono System.IO.StreamReader
• WinRTLegacy.IO.StreamWriter class, that is compatible with Mono System.IO.StreamWriter
• WinRTLegacy.Xml.XmlReader class, that is compatible with Mono System.Xml.XmlReader
• WinRTLegacy.Xml.XmlWriter class, that is compatible with Mono System.Xml.XmlWriter

The simplest way to use the replacement classes from WinRTLegacy if the namespace doesn’t match is via using directive:

#if NETFX_CORE
using XmlReader = WinRTLegacy.Xml.XmlReader;
#else
using XmlReader = System.Xml.XmlReader;
#endif

This way you can use XmlReader class, which will be taken from WinRTLegacy.Xml namespace on Universal Windows Platform and from System.Xml namespace elsewhere.

• 2017–05–16 Page amended