Ext.NET controls will not rended in IE

[infotex]

Hey guys,

I have an issue with IE9 (did not check with older versions). The ext.net controls will not render at all.
After doing some basic debugging I found out that all the ext.axd scripts are rendered with weird characters in IE (something to do with the encoding I guess?).

Here is the configuration i have on the page resource manager

<ext:ResourceManager runat="server" RenderScripts="Embedded"  RenderStyles="Embedded" ClientIDMode="Static" InitScriptMode="Inline" ScriptMode="Release"/>

and here are the relevant parts on my web.config file

<extnet theme="Gray" locale="el-GR" directMethodNamespace="PF.Direct"/>

...

<pages enableSessionState="true" validateRequest="true" >
.....
      <controls>
        <add assembly="Ext.Net" namespace="Ext.Net" tagPrefix="ext" />
      </controls>
....
    </pages>
    
    <httpHandlers>
      <add path="*/ext.axd" verb="*" type="Ext.Net.ResourceHandler" validate="false" />
....
</httpHandlers>
    
    <httpModules>
      <add name="DirectRequestModule" type="Ext.Net.DirectRequestModule, Ext.Net" />
...
    </httpModules>

 <system.webServer>
    <modules>
....
      <add name="DirectRequestModule" preCondition="managedHandler" type="Ext.Net.DirectRequestModule, Ext.Net"/>      
    </modules>

    <handlers>
...
      <add name="DirectRequestHandler" verb="*" path="*/ext.axd" preCondition="integratedMode" type="Ext.Net.ResourceHandler" />
..
    </handlers>
...  
  </system.webServer>    

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
        <bindingRedirect oldVersion="1.0.0.0-4.5.9" newVersion="4.5.10" />
      </dependentAssembly></assemblyBinding>
  </runtime>

[geoffrey.mcgill]

Hello,

Does the page render correctly if you remove the .locale setting from the Web.config?

locale="el-GR" <-- remove this

There was some encoding issues with the Locale .js files, but I believe we have fixed and will be available with the next release (2.2.0).

[infotex]

Hey Geoffrey,

Removing the locale setting as well as the <globalization> setting did not seem to fix the problem.

However, I played with the resource manager settings and I found out that settings the renderer to CacheFly CDN works ok.

<ext:ResourceManager runat="server" RenderScripts="CDN"  RenderStyles="CDN" ClientIDMode="Static" InitScriptMode="Inline" criptMode="Release"/>

Any ideas why this could be happening?

[Baidaly]

Hello!

Can you check does IE9 work in compatibility mode because ExtJS doesn't support compatibility mode? http://www.sevenforums.com/browsers-...ml#post1235105 Also, can you check in other browsers?

[infotex]

Hello!

Can you check does IE9 work in compatibility mode because ExtJS doesn't support compatibility mode? http://www.sevenforums.com/browsers-...ml#post1235105 Also, can you check in other browsers?

Hello Baidaly,

Yes i have already checked a about compatibility mode in IE9 and the problem still remains. I have checked in firefox, chrome and safari and all three seem to be rendering ext.net controls properly.

I have managed to get the controls to render in IE9 (i.e. get the .axd scripts to be delivered correctly) by changing the renderer from "embedded" or "file" to CDN (see previous post).

I also checked if gzip compression had something to do with it, but turning gzip off didn't help either...

[Vladimir]

Did you define Ext.Net http handler in web.config
Please check ext.axd requests in Fiddler to ensure that reponse is valid (just remove CacheFly mode)

[infotex]

Did you define Ext.Net http handler in web.config
Please check ext.axd requests in Fiddler to ensure that reponse is valid (just remove CacheFly mode)

Hey Vladimir,

Yes i think I do define an ext.net http handler in my web.config correctly. Here it is:

<httpHandlers>
      <add path="*/ext.axd" verb="*" type="Ext.Net.ResourceHandler" validate="false" />
    ...
</httpHandlers>

Here is the fiddler resutls. The highlighted sessions are from IE9 and the response seems to be valid but not parsed by IE correctly (see IE Developer Tools screenshot)

[Vladimir]

If you set CleanResourceUrl=false in ResourceManager then does it work?

[infotex]

If you set CleanResourceUrl=false in ResourceManager then does it work?

That worked great Vladimir, thanks. If you have time can you please elaborate a bit on this? what was going on?

Thanx again, Yiannis