WCF Binary Message Inspector no longer working (Fiddler4)?

[Brian Sayatovic]

I'm running Fiddler 4 (v4.4.5.6) and my previously working WCF-Binary-Message-Inspector is no longer showing up in the inspectors tabs.

The inspector is an open source project: https://github.com/waf/WCF-Binary-Message-Inspector

My colleague is still running 4.4.5.1 and his inspector works fine.  Did something change in recent Fiddler's that would break this?

[EricLaw]

Find your DLL in Windows Explorer. Right-click it. Click "Unblock."

If you package your extension in an executable installer rather than a ZIP file, the "Mark of the Web" won't be set on the DLL when it's extracted, which avoids this problem.

As to the question of whether "something changed"-- probably. I took a specific fix in the past to attempt to prevent the .NET Framework from caring about the "Mark of the web" but it appears that this fix no longer works.

[Brian Sayatovic]

I double-checked that my DLL was unblocked.  I assumed it had been since i twas working prior to recently updating to the latest Fiddler4.  After moving it to my desktop (can't Unblock files in Program Files tree), I verified it was already unblocked, and moved it back.  I ran again to make sure it was still not working.

I also ran with DbgView alongside in hopes of catching an error message.  I also looked in Event Viewer but found nothing.  Is there some place else I could check for errors?

Alternatively, is there a place to download older versions?

[EricLaw]

to confirm, you're putting this in the Inspectors folder, right? I tried the latest bits from http://archive.msdn.microsoft.com/wcfbinaryinspector/Release/ProjectReleases.aspx?ReleaseId=4252 and they work fine in the latest Fiddler v4

Using the black QuickExec box below the Web Sessions list, type

 

prefs set fiddler.debug.extensions.showerrors True

…hit Enter, and then type

prefs set fiddler.debug.extensions.verbose True

 

and hit Enter, then restart Fiddler.

 

Fiddler will subsequently emit verbose add-on related information to the LOG tab, including listing all of the assemblies it tried to load.

[Brian Sayatovic]

Wow, that's some awesome diagnostic tools!  And it highlighted my problem when I saw that my assembly wasn't being loaded because it was looking in *the wrong folder*.  And that was because somehow my old Fiddler2 (where I never had the inspector) folder got moved under my Fiddler4 folder and my start menu shortcut to Fiddler was pointed at Fiddler2, not Fiddler4.  Once i ran Fiddler4, it was working fine (I even made sure I updated that Fiddler4 to the latest and greatest and it worked).

Sorry for the confusion, but thank you for showing me some even more powerful tools in Fiddler!