RootedPathValidator Class

Validates the rules governing the use of the tempFilesLocation configuration switch.

System.Object
  System.Configuration.ConfigurationValidatorBase
    System.Xml.Serialization.Configuration.RootedPathValidator

Namespace:  System.Xml.Serialization.Configuration
Assembly:  System.Xml (in System.Xml.dll)

public class RootedPathValidator : ConfigurationValidatorBase

The RootedPathValidator type exposes the following members.

  NameDescription
Public methodRootedPathValidatorInitializes a new instance of the RootedPathValidator class.
Top

  NameDescription
Public methodCanValidateDetermines whether the type of the object can be validated. (Overrides ConfigurationValidatorBase.CanValidate(Type).)
Public methodEquals(Object)Determines whether the specified Object is equal to the current Object. (Inherited from Object.)
Protected methodFinalizeAllows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)
Public methodGetHashCodeServes as a hash function for a particular type. (Inherited from Object.)
Public methodGetTypeGets the Type of the current instance. (Inherited from Object.)
Protected methodMemberwiseCloneCreates a shallow copy of the current Object. (Inherited from Object.)
Public methodToStringReturns a string that represents the current object. (Inherited from Object.)
Public methodValidateDetermines whether the value of an object is valid. (Overrides ConfigurationValidatorBase.Validate(Object).)
Top

When adding a WebReference object to a Web service in the .NET Framework, files are created by the Web service discovery process.

Web service clients learn where to find the Web service description (WSDL) document by adding a WebReference object. The Web service clients then save the discovered documents to the disk by using the WriteAll method. For example, the discovered documents may be .xsd schema files or service descriptions. At the end of the process, the client deletes the files. You can change the default location of the files in the temporary folder by using the tempFilesLocation switch in the <xmlSerializer> element, specified in the Machine.config configuration file, as in the following example.

<configuration>
  <system.web>
  <system.xml.serialization>
    <xmlSerializer tempFilesLocation=".."/>
  </system.xml.serialization>
</configuration>

The value of tempFilesLocation must be an absolute path. If the path specified is not absolute, the .NET Framework generates a ConfigurationErrorsException exception when the configuration section is referenced.

The value of the property is truncated to remove leading and trailing white spaces.

If value of the tempFilesLocation property is composed of white space, the default %TMP% location is used for the compilation. The same default behavior occurs when no tempFilesLocation switch is specified.

The SerializationXmlSerializer does not check to see whether the path exists. If it does not, a DirectoryNotFoundException is generated. This is identical to the default behavior of the XmlSerializer if the %TMP% path does not exist.

.NET Framework

Supported in: 4, 3.5 SP1, 3.0 SP1, 2.0 SP1

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft