Hello,

             I have seen the latest update in WAP 1.0v that "Resource support with the App_GlobalResources directory:" feature is available now, but i don't know how to access the value from the resource file using the Proxy object?

For e.g : 'Constants.resx' resource file is created under 'App_GlobalResources' folder., So to access a value(HeaderMsg) from the resource file in a sample.aspx.cs code behind page would be like

string temp = Constants.HeaderMsg; or

string temp = Namespace.App_GlobalResources.Constants.HeaderMsg(using this syntax runs into runtime error saying an exception type of"'System.Resources.MissingManifestResourceException'  occured..

It would be really helpful, if someone helps me out?

Also, I assume 'Build Action' property value for 'Constants.resx' file to 'None' would help me to make any changes in the resource file without recompiling the application - Please correct me , if I am wrong.

Thanks,

Chandra

The syntax is the following:

string temp = Resources.Constants.HeaderMsg;

For resources in the App_GlobalResources directory the BuildAction should be "Content" and the CustomTool should be "GlobalResourceProxyGenerator".

You can make chages to the .resx files without recompiling.  However, if you remove or rename a resource the application could break at run-time.

Changes to constants.resx within VS will cause constants.designer.cs proxy class to update.  This will make the IDE recompile even though it may not be absolutely necessary.

Changes to constants.resx outside VS will not allow the constants.designer.cs proxy class to update.  As I stated before this is ok as long as you do not remove or rename a resource that the web app is using. It also means that if you switch back to VS intellisense will not reflect your changes.  To fix this right-click on constants.resx and "Run CustomTool."

Thanks Tim. It works fine.

BTW, What would be your suggestion, If I want to add a resource file to a "Class library" project and make use of the 'Strongly typed' proxy object to refer values from the resource file?

Should I apply the same settings on resource file(BuildAction should be "Content" and the CustomTool should be "GlobalResourceProxyGenerator) ? or ??

Thanks in advance for your help!

Chandra

TheGlobalResourceProxyGenerator was only designed to work with App_GlobalResources.  I don't think it would work with a client library.

When you add a .resx file to a Web Application Project outside of App_GlobalResources or App_LocalResources we treat it just like a client library. The BuildAction is set to EmbeddedResource and the CustomTool is set to ResXFileCodeGenerator.  The ResXFileCodeGenerator creates a strongly typed class for accessing the resource.  However, the class is internal.  This means that within the client library that contains the .resx you can access the resource strongly typed but not from a referencing assembly.

One way you can work around this is to use a different generator that creates a public class.  One exame of this is here: http://www.codeproject.com/useritems/ResXFileCodeGeneratorEx.asp.  Using this generator in your client library you should be able to access the resources in any project referencing it.  Note, there could be conflict with the resource namespaces that would have to be resolved with this approach.

There still seems to be a bug with the GlobalResourceProxyGenerator tool in WAP.

It works fine for strings, but if you try to use text file resources, the tool is looking for the resource files in the VS2k5 installation path instead of in the project folders.  (It looks like it's using a relative path from the project file, but it's being incorrectly resolved from either the VS executable or the DLL that the tool resides in.)

I haven't tried icons, images, etc.  I haven't had a need for them in WAP projects.

I was able to work around my immediate problem by switching to the ResXFileCodeGenerator and not use the App_GlobalResources folder, but it's still something that should be looked into.

Hi,

Is there a hot fix or patch available to fix this bug? Service pack 1 vs still has not addressed the problem.

Thanks

I am experiencing the same problem. Is there a hotfix fore this? It appears that the path of the first file resource in a .resx file is not processed properly.

 thanx,

rinze