[mapguide-internals] Autodesk.MapGuide.Studio.Site.LayerInfo.Save

[Kenneth Skovhede, GEOGRAF A/S]

I still cannot guess where exactly the problem occurs.
Is it when you load the page?
Is it when you save a layout from Maestro?
Is it when you create a temp layout in custom .Net code?
Is it in the viewer code?
Is it in a sample application?

Regards, Kenneth Skovhede, GEOGRAF A/S



ljv skrev:
> Thx, i will check with em.
>
> But the server has the same problem, without the culture set (as default)
> all text search and replace takes very long time (used when parsing
> layouts).  To use the map without setting culture is impossible. The problem
> is in the dotnet code.  If a create an  empty web  app that search and
> replaces text in the same manner as the mapserver the  response is also
> slow.  It's around 1000 times slower than if you set the culture.  
>
>
>
> ljv wrote:
>   
>> I find this (Autodesk.MapGuide.Studio.Site.LayerInfo.Save) functions slow,
>> 2-4 seconds to save 2kb. 
>>
>> There is no problem with server or network, most functions are fast.
>>
>>  Except for this: In web.config globalization Culture="xxxx" must be set.
>> Unless the culture is explicite set all strings functions like search
>> become so slow that the application is useless. Both maestro and mapstudio
>> benefit from adding culture to web.config. we have used our
>> culture="sv-SE" and English variants and setting the culture speeds the
>> viewer and application.
>>
>>     
>
>