We have implemented Westwind.Globalization in a project that is multi-tenant. We also have handled tenant specific entries by creating custom cultures (much as was suggested in Issue 70 that since been closed). Lastly, we are using strongly typed classes
We append a unique tenant id to a culture and have a custom culture. so en-us become en-US-S2E001
This has worked great, on our dev machines (VS2017 iisexpress) and works great on a Azure app service that we test on.
We have other test and staging servers that are Windows 2012 R2 servers with IIS. They are virtual machines. On these machines, we noticed that tenant specific entries where rendering with the invariant values.
Upon further testing, we found that if we used DbRes.T on a view in place of a strongly types class, this throw a "Culture Not supported" error [@DbRes.T("Test", "Labeling", "en-US-S2E001") instead of @Labling.Test] (This is interesting in itself as is appears that the class handles this better than DbRes.T)
All the articles I have found (only a small handful) speak to adding the custom Culture via CultureAndRegionInfoBuilder. I thought that might not be to difficult to add to the Session_Start in the global.asax, thinking this is the earliest I might know the tenant id, but of course quickly found that this requires admin rights on the server to Windows/Globalization which is currently a challenge for us.
As part of troubleshooting this, we have upgraded all the Westwind components to your latest versions.
I was wondering if you have seen this and have a viable alternative,
Hello
We have implemented Westwind.Globalization in a project that is multi-tenant. We also have handled tenant specific entries by creating custom cultures (much as was suggested in Issue 70 that since been closed). Lastly, we are using strongly typed classes
We append a unique tenant id to a culture and have a custom culture. so en-us become en-US-S2E001
This has worked great, on our dev machines (VS2017 iisexpress) and works great on a Azure app service that we test on.
We have other test and staging servers that are Windows 2012 R2 servers with IIS. They are virtual machines. On these machines, we noticed that tenant specific entries where rendering with the invariant values.
Upon further testing, we found that if we used DbRes.T on a view in place of a strongly types class, this throw a "Culture Not supported" error [@DbRes.T("Test", "Labeling", "en-US-S2E001") instead of @Labling.Test] (This is interesting in itself as is appears that the class handles this better than DbRes.T)
All the articles I have found (only a small handful) speak to adding the custom Culture via CultureAndRegionInfoBuilder. I thought that might not be to difficult to add to the Session_Start in the global.asax, thinking this is the earliest I might know the tenant id, but of course quickly found that this requires admin rights on the server to Windows/Globalization which is currently a challenge for us.
As part of troubleshooting this, we have upgraded all the Westwind components to your latest versions.
I was wondering if you have seen this and have a viable alternative,
Thanks
Dan