Here you have it in "one line":



You can put at the top of Guest.aspx inside the server script tag.

But I didn't include the dropdown. ASP.NET server controls aren't great here because the culture has to be changed so early in the page life-cycle. You could always use straight HTML select elements with some javascript.

How about just a couple of links somewhere on the page for your different languages? :



Or you can put the links on your feeder page. Or if you have users typing in URLs, you can use a different URL for each language (eg ensup.mycompany.com and desup.mycompany.com)?

That dropdownlist isn't going to work well unless you use it to set session state or something like that. The point in the page load where we have to set the culture is way too early to interact with the dropdownlist. That's the main problem with that solution.

Your iframe URL could be something like this: http://domain.com/?Theme...edded&Language=en-US

Looks interesting...

If I apply the line:


What do I need to to now?

Somewhere on the guest.aspx place this i guess:


But now what where to get the strings I need to translate and how to store them?

Update:
Got the Simple Resx Editor...

saved a copy of Default.resx named da.resx.

Made some translations...

What now?

This is great :)