How to place resx files in App_GlobalResources folder using solutions (wsp)???

Question

Hi everybody,

I've made a lot of solutions (wsp) for SharePoint 2007 and I have almost automated all installation steps needed, but there is one thing I cannot automate.

How can I make a solution that places resources (resx) files in the App_GlobalResources folder of the virtual application?

Thanks in advance.

Answer 1

You'll need to write a Feature Receiver that copies the files, because there's no way to deploy them directly through SharePoint configuration files.

I found this blog post useful when I had to do this: SharePoint Resources, Types, Use and Deployment

Answer 2

The solution framework don't support deployment to the App_GlobalResources folder.

You need to write a SharePoint timerjob that copies the files. A timerjob runs on all servers i the farm, so every server will get the resource files copied. What you should be aware of is the context (Domain account) you run your timerjob. To start the timerjob you need to use a farm account - the account who runs the web application isn't enough (This includes RunWithElevated...) - long story short - start the timerjob from af Farm feature or a hidden SiteCollection feature (Hidden features runs as the farm account).

Find more inspiration here:

Creating Custom Timer Jobs in Windows SharePoint Services 3.0

SharePoint Resources, Types, Use and Deployment (The link DylanW referred to)

Answer 3

You could use the stsadm command CopyAppBinContent that copies files frpm 12/Resources to App_GlobalResources. So your WSP (VS project) need to place your resx files in that folder. I´m using a solution where I actually place my resx files in a folder called Resources in the .csproj root (just to avoid the weird namespaces that come with placing them in 12/Resources) and then XCopy them (the resx files) to 12/Resources when I build.

CopyAppBinContent is then added to the deploy process (a step in a .bat file).

CopyAppBinContent has some issues when run on a farm and to come around that I use a custom SPJobDefinition that handles starting that command in the farm.