Checking Fiddler into a source tree

[kingces95]

Hello! Can I check fiddler into our SVN tree to simplify deployment to
our dev team and unify which version we are all using? Is it as simple
as XCOPYing the binaries that were put into the program files
directory or is it more involved. Maybe there some registry keys or
code that needs to execute to hook into IE and FireFox etc.

Thanks!
Chris

[EricLaw]

For IE, you don't really need to check in any registry keys-- you
won't get the "launch" button in IE, but that's about it.

To get the FiddlerHook extension working in Firefox, you must write a
registry key pointing at the FiddlerHook folder...

WriteRegStr HKLM "Software\Mozilla\Firefox\Extensions"
"fiddl...@fiddler2.com" "$INSTDIR\FiddlerHook"

[kingces95]

Thanks! And I'd also like to automatically set up the filters for each
dev environment. How can I automate setting the "Use Filters" switch,
set "Show only the following hosts", and the including their local
machine name in the list of hosts to allow?

Thanks,
Chris

On Mar 10, 8:19 pm, EricLaw <bay...@gmail.com> wrote:
> For IE, you don't really need to check in any registry keys-- you
> won't get the "launch" button in IE, but that's about it.
>
> To get the FiddlerHook extension working in Firefox, you must write a
> registry key pointing at the FiddlerHook folder...
>
> WriteRegStr HKLM "Software\Mozilla\Firefox\Extensions"

> "fiddlerh...@fiddler2.com" "$INSTDIR\FiddlerHook"

[EricLaw]

You need to deploy the Default.ffx XML file to \documents
\fiddler2\Filters folder.

> > > Chris- Hide quoted text -
>
> - Show quoted text -

[kingces95]

Thanks Eric! Thanks worked. Is there a way to make Fiddler open by
default to the Inspector tab with raw views selected for both inbound
and outbound traffic?

Thanks,
Chris

[EricLaw]

Yes, but it's non-trivial; you'd basically need to write script within
the OnBoot() handler within the FiddlerScript file inside \documents
\Fiddler2\scripts.

FiddlerObject.UI.ActivateRequestInspector("RAW");
FiddlerObject.UI.ActivateResponseInspector("RAW");

> > > - Show quoted text -- Hide quoted text -

[kingces95]

Thanks, cool! That worked. Is there a bit of script I can insert in
OnBoot so that the inspector tab itself active on strartup?

Thanks,
Chris

[EricLaw]

hrm.

FiddlerApplication.Prefs.SetStringPref("fiddler.ui.lastview",
"Inspectors")

But that's going to override the behavior where Fiddler remember's the
user's last tab.

[kingces95]

Great! That's what I was looking for. Great tool! Thanks Eric!

[kingces95]

Eric, can fiddler run side by side? I've checked a copy into our build
but some folks already have one installed. When they start the one I
checked into the build I'd like that copy to pick up a separate set of
configuration settings so the checked in copy is totally isolated. Is
there a command switch to point fiddler at a configuration directory
other than "%USERPROFILE%\Documents\Fiddler2"?

Thanks,
Chris

[EricLaw]

Interesting scenario; there's no good way to do exactly that today.

Fiddler respects the "UserPath" registry key to load its files from a
different folder, but there's nothing in Fiddler today that allows you
to tell Fiddler to get its registry settings (and, by extension, that
UserPath registry key) from some other path in the registry.

Can you elaborate a little bit on what settings you'd want isolated in
your "Build Version"? Or, stated another way, why is it a problem
that the "Build Version" and the default install share settings? Your
answer may shape the solution. :-)

thanks!

[kingces95]

Settings like having Fiddler open up to Raw for example. I'd prefer
that behavior only be the case if they launch the build version. If
they installed a version I'd prefer their installed version continue
to behave in the default manner. Setting the filters are a bit
trickier because they are specific to the users machine. For that case
I guess I'd update the scripts that set up the cmd.exe build\tools
environment to also spit out some custom Fiddler files everytime it's
launched.