Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have a sandbox solution that for the some of it I have german translations for, like the feature name and description.

However to make this a proper multi-lingual solution I need to do the same for the List Definition.

But I think, I'm pretty sure that the list Definition will not referefence the feature resource files, the only way to localise a sandbox I think.

So have I got the wrong end of the stick.

Is is possible to have alternate language for a list definition (field titles, list name etc) in a sandbox.

If So how?

To clarify a little more.

I can create the list in XML or Code. But in order for the list to be language specific at runtime, ie when a user switches langauges, the field names and list name must have a specific "$Resouce" entry against them. If I leave it without a dll prefix as you would for feature resources, it does not work. Lists work a little differently it seems.

So What I want to know is What $Resouce should I be using, if you are using Satellite assemblies then whats the entry in the list def you use.

Admittedly I have not tried satellite assmeblies yet as I wasnt sure about deploying them in the sandbox, so the articles on how to do this are of interest. This might work, I was hoping someone had done this.

share|improve this question
    
I've asked a similar question here: sharepoint.stackexchange.com/questions/30967/… –  Brian Apr 3 '12 at 19:17

3 Answers 3

up vote 2 down vote accepted

First of all, a very good MSDN article about localizing SharePoint Sandboxed solutions:

If you will unable to perform localization through XML, take a look at a code approach: we've done this in a real project, works fine and it is easy to maintain.

You will need to know:

Ok, this way you will have to write some code, but trust me, this is much better approach, then unpredictable and type-prone XML, especially when you have many custom lists.

Feel free to ask any futher questions, if you'll decide to go this way.

share|improve this answer
    
Hi thanks for the response. The msdn docs are new to me, well everyone as they are dated in feb I've been looking at this on and off since december. I've added more clarification to the question above. –  BinaryJam May 8 '11 at 10:02

This really depends how you're going to deploy this. But if you do go the Satellite Assembly route then I doubt it would work in a SandBox; since the assembly must be deployed on the web frontend itself.

Site variations however, may work.

share|improve this answer
    
thanks but this is for a standard solution not using variations –  BinaryJam May 8 '11 at 10:01

A first peek into this (As I will need to do something similar later this year) yields looking into Satellite Assemblies. First time I've even heard of this concept, but it looks like you compile your resx files into public classes, and reference them in your code as strongly typed objects.

http://www.mikhaildikov.com/2007/06/using-satellite-assemblies-in.html

share|improve this answer
    
I will give that a try. I already use compiled resources in my 2007 farm projects all the time, its how my 2007 list defs are multilingual. For anyone interested the blog post says you cant use the <%$Res in aspx pages, which is true but in code you can populate a label control by accessing the resource variable string directly. –  BinaryJam May 6 '11 at 9:22

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.