Re: Rerouting Requests via a Proxy because of .NET "bug"

From: John Saunders (johnwsaundersiii)
Date: 12/03/04 

Date: Fri, 3 Dec 2004 12:43:16 -0500

"Codex Twin" <codex@more.com> wrote in message
news:OmIOmhV2EHA.3132@TK2MSFTNGP14.phx.gbl...
>
...
> John
>
> The scenario is this: The server application I have built uses the ChartFX
> (by SoftwareFX) control. This control causes the download of half a dozen
> or
> so "client-side components". These are nothing more than .NET assemblies
> which allow all the fancy dynamic chart customisation tools on the
> browser.
> One of the conditions for the client-side dlls to work is that the client
> machine has to have the .NET framework installed.
>
> These same machines, being behind the firewall, uses the automatic proxy
> discovery script to determine the proxy server settings.
> Now, because of the problem detailed in the first article
> (http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;307220) and
> the
> fact that the .NET Framework does not support proxy discovery scripts, the
> client machine cannot see get the proxy server settings and the charts
> fail.

Please be more specific. Exactly what do you mean when you say "the charts
fail"?

> When the machine.config file is amended as the article explains, then it
> works. I do not have access to their machine.config files, hence the
> programmatic way of supplying proxy server settings as detailed in the
> second article, which as you have rightly said, only deals with Web
> Services.
>
> My problem has been where to impose this programmatic code, and what the
> correct code is.

Whatever the solution is, it will be client-side.

Have you spoken to SoftwareFX about this? You may not be the first to have
this problem.

John Saunders