Dec 10, 2009, 9:52 AM
[CLOSED] [1.0] ResourcePlaceHolder is ignored
Hi,
We have ext:ResourcePlaceHolder placed in the header to specify the exact position of Ext.NET scripts (the ones with objects construction and initialization). That's where so far they were rendered . I just updated from SVN and now the scripts are rendered at the end of the page inside of the <Ext.Net.InitScript> tag, which breaks out custom scripts because they are rendered and executed earlier now and they depend on Ext.NET scripts.
I suspect that's because we have RenderScripts="None" set for ResourceManager, but we need to have it set this way, because we are including Ext.NET scripts manually for combining and minimizing of all scripts.
The change that caused this is in ResourceContainer.cs, starting from line 57:
How can we have the Ext.NET object creation scripts rendered in the place of ResourcePlaceHolder and at the same time have RenderScripts set to None?
Regards,
Tadeusz
We have ext:ResourcePlaceHolder placed in the header to specify the exact position of Ext.NET scripts (the ones with objects construction and initialization). That's where so far they were rendered . I just updated from SVN and now the scripts are rendered at the end of the page inside of the <Ext.Net.InitScript> tag, which breaks out custom scripts because they are rendered and executed earlier now and they depend on Ext.NET scripts.
I suspect that's because we have RenderScripts="None" set for ResourceManager, but we need to have it set this way, because we are including Ext.NET scripts manually for combining and minimizing of all scripts.
The change that caused this is in ResourceContainer.cs, starting from line 57:
ResourceManager rm = ResourceManager.GetInstance(this.Page);
and then: if(rm == null || rm.RenderStyles != ResourceLocationType.None)
How can we have the Ext.NET object creation scripts rendered in the place of ResourcePlaceHolder and at the same time have RenderScripts set to None?
Regards,
Tadeusz