Hi there,
Currently running version Csla 4.5.501 and some weeks ago a new customer from Germany reported an issue with number conversions.
We are running in a deployment scenario where the application server is a location and connected to enterprise databases and ERP systems. It is a requirement that all these pieces "talk" the same culture, "de-de" (German) for instance.
But clients applications
(win forms, workstations or browsers) can be (and are free to) running in any
culture. English commonly.
We would like to understand why the Csla in methods SetThreadContext() insist
in syncing the client request culture into the actual running thread culture.
Even when the thread is on the other side of the data-portal (This
overrides IIS settings in the application server). ?
Thread.CurrentThread.CurrentCulture = request.CurrentCulture;
Thread.CurrentThread.CurrentUICulture = request.CurrentUICulture;
And also if there is a
visible risk removing those synchronization and let each part use its own
culture configuration?
So far we haven't found inconvenient but any concern or comment is appreciated.
Thanks.
