Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

ResourceManager.CreateFileBasedResourceManager Method

Returns a ResourceManager that searches a specific directory for resources instead of in the assembly manifest.

Namespace:  System.Resources
Assembly:  mscorlib (in mscorlib.dll)
public static ResourceManager CreateFileBasedResourceManager(
	string baseName,
	string resourceDir,
	Type usingResourceSet
)

Parameters

baseName
Type: System.String
The root name of the resources. For example, the root name for the resource file named "MyResource.en-US.resources" is "MyResource".
resourceDir
Type: System.String
The name of the directory to search for the resources. resourceDir can be an absolute path or a relative path from the application directory.
usingResourceSet
Type: System.Type
The Type of the custom ResourceSet to use. If null, the default runtime ResourceSet is used.

Return Value

Type: System.Resources.ResourceManager
The newly created ResourceManager that searches a specific directory for resources instead of in the assembly manifest.
ExceptionCondition
ArgumentNullException

The baseName or resourceDir parameter is null.

This method returns a ResourceManager that is not dependent on any particular assembly. The returned ResourceManager can be used to load resources for an ASP.NET page or for testing a ResourceSet implementation.

You can specify a ResourceSet implementation. If you do not need a specific ResourceSet implementation, but would like to use a custom resource file format, you should derive from the ResourceSet class, override GetDefaultReader and GetDefaultWriter, and pass that type to this constructor.

Caution noteCaution

Using standalone.resources files in an ASP.NET application will break XCOPY deployment because the resources remain locked until they are explicitly released by the ReleaseAllResources method. If you want to deploy resources into ASP.NET applications, compile your .resources into satellite assemblies.

.NET Framework

Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, 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.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.