views:

2143

answers:

3

I'd like to enable the resource files to be editable after deployment. I read this post which suggests that this is possible, but I can't seem to figure out what settings I need to change to enable this.

I have added the App_GlobalResources folder to my ASP.NET 3.5 "Web Application" and added a resource file to this folder. I assume that the Build Action for this file needs to be changed, but no matter what I change the Build Action to, I cannot achieve the above stated functionality.

The App_GlobalResources folder and the resource file are copied into the bin directory. Once deployed, any edits to the .resx file are not being displayed.

Any ideas?

+3  A: 

A Web Application project is different than a Web Site project. I doubt you can achieve what you want with a Web Application project. You might check out this post:

http://stackoverflow.com/questions/398037/asp-net-web-site-or-web-application

Resources are generally meant to be static. They are items such as images, strings, and files that your program consumes and can rely on being present, (and therefore can be strongly typed in the case of strings/RESX files). The reason for using resources is simply to bundle them in with your DLL's so that distribution and referencing the resources becomes much easier.

Editable at runtime suggests you might want to use project or user Settings, or maybe a database? If you need to use RESX files you might need to write code to read/write them.

womp
A: 

You can achieve this, and I just did it.

Select the resource file in your project. Change the Build Action to content. Make sure that the Copy to Output Directory setting is turned OFF. When you deploy your project, the App_GlobalResources directory and your .resx file will get copied to the root of your web site. You can modify the .resx file and your live site will recognize the changes.

Mike C.
If you do this your application pool will recycle on your web ap
Dan
What are the negative repercussions of that happening?
Mike C.
A: 

this answer is non-sense!

Change the Build Action to content will cause your compilation to fail.