IE9 Blank Page after deployment

[softmachine2011]

Hi,

In our previous Ext.NET 1.X version, when we run our application against IE9 and Login or Main pages are loaded, there were a lot of times where web page appears in blank, and a refresh was needed in order to load web page as required.

So in this way, we had this hack code just for IE9 browser to avois this problem:

     <script runat="server">
        protected void Page_Load(object sender, EventArgs e)
        {
            // HACK: Parche para pantalla en blanco en IE9            
            if (Request.Browser.Browser == "IE" && Request.Browser.MajorVersion == 9)
                resManager.InitScriptMode = InitScriptMode.Inline;
        }
    </script>

    <ext:ResourceManager ID="resManager" runat="server" ViewStateMode="Disabled" />

Now, with Ext.NET 2.1 version, it looks that this hack is not working and we have the same problem just after a new deployment is performed.

At the moment, we can solve this issue just setting this code for all browsers:

<ext:ResourceManager ID="resManager" runat="server" ViewStateMode="Disabled" InitScriptMode="Inline" />

But, is there any performance drawback using Inline mode for all browsers instead of Linked?

If code is rendered in the same page and not as a separated javascript file, would we loose recource's cache capability of some browsers?


Thanks.

[geoffrey.mcgill]

But, is there any performance drawback using Inline mode for all browsers instead of Linked?

There is no performance drawback using inline init script, instead of linked. In fact it should actually be faster using inline instead of linked as a separate http request would not be required.

If code is rendered in the same page and not as a separated javascript file, would we loose recource's cache capability of some browsers?

Neither the inline or linked init scripts are cached.

[softmachine2011]

Ok,

Thank you very much for your kind your assistance.