Last post Mar 07, 2010 03:34 AM by KraGiE
Mar 05, 2010 03:42 PM|BitShift|LINK
Have a need to build a new web app soon. The app will be for dozens or more groups that will have their own group code or number. A common landing page will be used which the user enters their group# and then is presented with a page that is customized
to their group. Ok, no big deal. Now, there are a few forms that all groups share. Nothing special, just your standard input forms. However, some labels might need to be localized to a specific language and some groups might need to show additional fields
on a given form etc.
Here is how Im considering the approach to this:
- The common landing page grabs the group# and sets a session value
- An admin section for defining the specifics about each group (logo etc)
- The forms all use the same input fields, but some can specify fields that should be hidden
- For the localization, a common set of resx files are used
comments or better ideas ?
Mar 07, 2010 03:34 AM|KraGiE|LINK
Seems simple enough. It depends on how serious you are going to be on the localization. If you're going to provide the verbage, then sure why not go with the common set of resx files. As long as you maintain the same key across all languages, you should
be in good shape.
You could also stream in resx information on runtime, but if the values in the resx file aren't updated regularly, this is probably a bad idea. Resx files usually require a recompile if it's attached to the project directly. If it's read via file location,
it'll definitely cause an application reset when the new resx assemblies are deployed.