Link to fiddler.exe dynamically

[Jared]

Hello,

I'm looking to write a fiddler extension following this article: https://docs.telerik.com/fiddler/extend-fiddler/createextension

In this article it suggests linking to fiddler at a hard coded local path.

Is there any way to link to fiddler from a nuget feed, git sub-module or other way or is it best practice to bundle the Fiddler.exe with your application so it can be built without hard-coded paths to locally installed tools? How is this normally done?

Thanks

[Nick Iliev]

Hello Jared,

 

The Fiddler Classic application is an executable that uses DLLs. That said, you can only use libraries from a static folders as explained in the documentation articles:

https://docs.telerik.com/fiddler/extend-fiddler/loadextension 

 

Regards,
Nick Iliev
Progress Telerik

[Jared]

Hey Nick, I don't think the question was fully understood. I hope I can clarify.

The executable can be linked and delivered any number of ways; this is not a limitation of Fiddler: it works fine. Rather than submitting Fiddler.exe to a plugin's source control (not even sure if that's compliant with the license): I'm looking for the officially supported way to take a dependency on Fiddler.exe.

I'm hoping the answer isn't that every contributor and build machine needs to install Fiddler to the exact same file path.

[Nick Iliev]

You can install Fiddler Classic from Chocolatey. This way, you can automate the process without the need to adding the Fiddler executable to your source control.

https://community.chocolatey.org/packages/fiddler 

choco install fiddler

Otherwise, you can install Fiddler on your build machines and refer to it manually where needed.

[Jared]

That solution works for me. I appreciate it, Nick.