Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
AllowUnassigned Property
Collapse the table of content
Expand the table of content

IdnMapping::AllowUnassigned Property

Gets or sets a value that indicates whether unassigned Unicode code points are used in operations performed by members of the current IdnMapping object.

Namespace:  System.Globalization
Assembly:  mscorlib (in mscorlib.dll)

property bool AllowUnassigned {
	bool get ();
	void set (bool value);

Property Value

Type: System::Boolean
true if unassigned code points are used in operations; otherwise, false.

A registered domain name cannot contain unassigned code points. Consequently, the default value of the AllowUnassigned property is false. The IDNA specification permits unassigned code points only in queries for matching strings (that is, in domain name lookup). For more information about the use of unassigned code points in domain names, see RFC 3454, "Preparation of Internationalized Strings (stringprep)" and RFC 5891, "Internationalized Domain Names in Applications (IDNA): Protocol".

Important noteImportant

If the AllowUnassigned property is false, the behavior associated with the property depends on the underlying operating system. On Windows 8, the IdnMapping class conforms to IDNA 2008, which is based on the Unicode 6.0 standard. On previous versions of Windows, the IdnMapping class is based on IDNA 2003, which is based on Unicode 3.x. Some code points that were unassigned in IDNA 2003 have been assigned characters and are supported in IDNA 2008. For example, U+0221 was introduced in Unicode 4.0. On Windows 8, it is encoded as "xn—6la". On previous versions of Windows, it throws an ArgumentException exception.

.NET Framework

Supported in: 4.6, 4.5, 4, 3.5, 3.0, 2.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1
© 2015 Microsoft