[CLOSED] Is Ext.NET conflict with glimpse?

  1. #1

    [CLOSED] Is Ext.NET conflict with glimpse?

    hello,

    while we are trying to use glimpse to do profiling, we found ext.net will fail if glimpse is turned on.
    (the failed request is url like this http://localhost:57511/extnet/extnet...adaf4e9e19d4d0)

    chrome console network
    Click image for larger version. 

Name:	extnet with glimpse on-network.jpg 
Views:	37 
Size:	96.7 KB 
ID:	24911

    below is the url response while i get it by browser
    Click image for larger version. 

Name:	extnet with glimpse on-error_url.png 
Views:	37 
Size:	74.0 KB 
ID:	24912


    while turn off glimpse, everything is ok.
    Click image for larger version. 

Name:	extnet with glimpse off-network.jpg 
Views:	39 
Size:	102.3 KB 
ID:	24913

    the response of the url while i get it by browser.
    Click image for larger version. 

Name:	extnet with glimpse off-url.jpg 
Views:	38 
Size:	105.9 KB 
ID:	24914

    My environment:
    MVC 4.0.40804,
    Ext.NET 4.1.0
    Glimpse 1.8.6
    Glimpse.Ado 1.7.3
    Glimpse.AspNet 1.8.0
    Glimpse.EF6 1.6.5
    Glimpse.Mvc4 1.5.3

    Is that a known issue of glimpse compatable?

    Ted
    Last edited by fabricio.murta; Apr 13, 2017 at 2:21 AM.
  2. #2
    Hello @u8621011!

    Unfortunately we can't guarantee Ext.NET is compatible with other 3rd-party extensions/profilling tools that manipulate the contents. We strive to make Ext.NET compatible with all modern browsers and that alone is a challenge. It seems your tool tries some specific fetches we can't just support. While we believe it is possible for you to make your tool work with Ext.NET it is not supposed to work out-of-the-shelf, some intermission from you would be necessary.

    To try to help you a little with it, it seems the Glimpse tool tries to include the shared resource and interpret it in a separate context which does not link the init script with the requested page, breaking the supported life cycle. When the init script is fetched, code behind has to know which page is related to that query.

    You have two lines of work in order to overcome this:
    1. figure out a way for glimpse to let Ext.NET know its context while fetching the init script (harder)
    2. change your web.config (maybe temporarily) to use initScriptMode="Inline" so that the init script is output in the page itself instead of a linked resource.

    For 2, you can alternatively just set up this setting (instead of site/folder-wide Web.config) on the resource manager itself -- @Html.X().ResourceManager().InitScriptMode(InitScriptMode.Inline)

    I hope this helps!
    Fabrício Murta
    Developer & Support Expert
  3. #3
    Fabricio,

    It works fine, thanks.

    Ted
  4. #4
    Glad it worked for you! Thanks for the feedback!
    Fabrício Murta
    Developer & Support Expert

Similar Threads

  1. Replies: 4
    Last Post: Dec 18, 2014, 9:42 AM
  2. [CLOSED] Ext is conflicting with Glimpse
    By leonardm in forum 2.x Legacy Premium Help
    Replies: 1
    Last Post: Aug 21, 2013, 5:30 PM
  3. Style sheet conflict
    By Dallas Morrison in forum 1.x Help
    Replies: 3
    Last Post: Feb 20, 2012, 3:43 AM
  4. Namespace Conflict for Class X?
    By mbean in forum 1.x Help
    Replies: 9
    Last Post: May 25, 2011, 1:31 PM

Posting Permissions