Manager. Create File Based Resource Manager(String, String, Type) Method
Returns a ResourceManager object that searches a specific directory instead of an assembly manifest for resources.
public: static System::Resources::ResourceManager ^ CreateFileBasedResourceManager(System::String ^ baseName, System::String ^ resourceDir, Type ^ usingResourceSet);
public static System.Resources.ResourceManager CreateFileBasedResourceManager (string baseName, string resourceDir, Type? usingResourceSet);
public static System.Resources.ResourceManager CreateFileBasedResourceManager (string baseName, string resourceDir, Type usingResourceSet);
static member CreateFileBasedResourceManager : string * string * Type -> System.Resources.ResourceManager
Public Shared Function CreateFileBasedResourceManager (baseName As String, resourceDir As String, usingResourceSet As Type) As ResourceManager
The root name of the resources. For example, the root name for the resource file named "MyResource.en-US.resources" is "MyResource".
The name of the directory to search for the resources.
resourceDir can be an absolute path or a relative path from the application directory.
A new instance of a resource manager that searches the specified directory instead of an assembly manifest for resources.
resourceDir parameter is
This method returns a resource manager that retrieves resources from a .resources file that is not embedded in an assembly. You can use this ResourceManager object to load resources for an ASP.NET page or to test a ResourceSet implementation. For an example that retrieves resources from a standalone .resources file, see the Retrieving Resources article.
This method lets you specify a ResourceSet implementation. If you do not want a specific ResourceSet implementation, but would like to use a custom resource file format, you should derive from the ResourceSet class, override the GetDefaultReader and GetDefaultWriter methods, and pass that type to this constructor.
Using standalone .resources files in an ASP.NET app will break XCOPY deployment, because the resources remain locked until they are explicitly released by the ReleaseAllResources method. If you want to deploy resources with your ASP.NET apps, compile your .resources files into satellite assemblies.