Custom Inspector Never Appears

2 posts, 0 answers
  1. Jesse
    Jesse avatar
    2 posts
    Member since:
    Apr 2015

    Posted 18 Apr 2015 Link to this post

    I'm trying to write a response inspector, and after trying numerous things, I can't get it to appear on the Inspectors tab.

    I've tried this basic test, and it doesn't seem to get loaded into Fiddler:

    using System.Windows.Forms;
    using Fiddler;
     
    [assembly: RequiredVersion("2.3.0.0")]
     
    namespace Test
    {
        public class TestInspector : Inspector2, IResponseInspector2
        {
            public override void AddToTab(TabPage o)
            {
                o.Text = "TestInspector";
            }
     
            public override int GetOrder()
            {
                return 0;
            }
     
            public void Clear()
            { }
     
            public byte[] body { get; set; }
            public bool bDirty { get; private set; }
            public bool bReadOnly { get; set; }
            public HTTPResponseHeaders headers { get; set; }
        }
    }

    I've compiled this against Fiddler 4.5.0.0 and 2.5.0.0, and tried loading it into both. Neither seems to work.

    I know that my dll is being loaded by Fiddler though. If I add this to the DLL, my Message Box appears while the application is loading.

    public class TestExtention : IFiddlerExtension
    {
        public void OnLoad()
        {
            MessageBox.Show("Hello Fiddler!");
        }
     
        public void OnBeforeUnload()
        {}
    }

    I've even tried compiling / loading inspectors I've found on codeplex, but none of them seem to work.

    Any help would be greatly appreciated.

  2. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 20 Apr 2015 Link to this post

    Hello, Jesse--

    Based on the behavior you describe, the most likely explanation is that your assembly isn't placed in the correct folder. It needs to be in the Inspectors folder (from which Inspectors are loaded), not the Scripts folder (where IFiddlerExtensions are loaded).

    When building Inspectors or extensions, you should type the following in the QuickExec box below the Web Sessions list:

       prefs set fiddler.debug.extensions.showerrors True

    And hit enter, then type

       prefs set fiddler.debug.extensions.verbose True

    Hit enter, and restart Fiddler.

    Subsequently, Fiddler's LOG tab will show much more information about the loading of Inspectors and other extensions. 

    Tip: You should also bump your RequiredVersion to 2.4.9.0 or ideally 2.5.0.0 unless you really plan on testing it against the ancient and unsupported v2.3.

    All the best,
    Eric Lawrence
    Telerik
     

    See What's Next in App Development. Register for TelerikNEXT.

     
Back to Top