How to run Fiddler as a Windows Service with AlwysUp

[CoreTech]

Hi Fiddler folks,

My company makes a commercial run-anything-as-a-windows-service tool called AlwaysUp. One of our customers mentioned that he uses Fiddler, so we decided to write up a step-by-step tutorial to guide him (and future customers) in setting up Fiddler to run as a Windows Service. It is available here: http://www.coretechnologies.com/products/AlwaysUp/Apps/RunFiddlerAsAService.html

Now Eric has cautioned that "Fiddler isn't intended for service use", but so far Fiddler seems to be working OK as a service on our test PCs. Have I overlooked any gotchas? Any words of wisdom that I should add to the tutorial?

Thanks!

[EricLaw]

I think you have seen the highlights:

1> Fiddler expects to be able to show UI. You can suppress most UI when running Fiddler by using the -quiet command line argument.

2> Fiddler only registers as the proxy for the user-account that it is running under. To get applications in other accounts to send traffic to Fiddler, their proxy settings will need to be adjusted manually. It looks like your instructions show how to do this already for one user, but in many cases if the goal is to run as a service, you'd hope to share it across multiple users. 
3> Fiddler is designed with the expectation that a human user will be around to clear the traffic list once in a while, otherwise Fiddler's memory usage will grow unbounded. You can help ensure that Fiddler doesn't use crazy amounts of memory by using the "Keep only" dropdown in the toolbar to automatically trim the session list once it reaches a certain length.

[CoreTech]

Many thanks Eric! I have incorporated your comments into the tutorial. Please let me know if you think of anything else.