CoExistance with ASP.NET ScriptManager

[martins42]

Hi,

for some reasons we have the requirement to integrate SmartClient into a host page which already contains the ScriptManager of ASP.NET .

Both Frameworks do overriding of some methods in JavaScript String class, setting own function in String.prototype.
But this changes are incompatible. F.E. SmartClient sets (and expects later) a trim method accepting one parameter. But the trim()-method set by ASP.NET Client JS-Library does the opposite, Setting a trim()-method which throws exception if called with parameter.
Regarding Integration order in host page, one of the frameworks "loose", it's code does not work any longer as expected.

Any ideas for Workaround?

Tanks in advance for any Information.

Regards
Martin

[Isomorphic]

Generally speaking, loading SmartClient second is the right approach since we tend to preserve or be compatible with other libraries expectations. This would most likely resolve this trim() difficulty. Let us know of you discover issues running in this style and we may be able to provide workarounds.

[martins42]

Thanks a lot for the response.

In deed changing the order of inclusion of the libraries in the page solved the observed problem.
We had to move script references of SmartClient from head-section of the page into Body, because ASP-NET ScriptManager can't be placed in head-section, but hopefully this will cause no problems.

Thanks again.
Martin