From: q0320811@mail.connect.usq.edu.au   
      
   In article <73c432dohq9dskl1hi7ihlsa90t1qkj0a4@4ax.com>,   
   StellaDrinker@REMOVE.ME.uboot.com writes...   
      
   > David Moss 's wild   
   > thoughts were released on Sun, 02 Apr 2006 00:25:05 GMT   
   > bearing the following fruit:   
   >   
   > >This seemed so easy at the beginning...   
   > >   
   > >I have a need to use xml data from a web server inside a vb.net program.   
   > >During development it worked great - then came the real world.   
   > >   
   > >Some of the people who will use my application use autoproxy.   
   > >They cannot access the web server directly, nor do they have proxy   
   > >server information hard coded in their registries.   
   > >   
   > >Oh, and I'm using the .net 1.1 runtime (Visual Studio .net 2003)   
   > >   
   > >Does anyone know how to get out through a web proxy, determined by   
   > >autoproxy, in vb.net and the 1.1 .net runtime?   
   >   
   > You need to ask in a dotnet group, this one if for VB6   
      
   If you mean microsoft.public.dotnet.vb my question seems to be the only   
   posting in there at this end. There has been no traffic in there for a   
   week.   
      
   I can't see any other .net specific newsgroups through my ISP.   
      
   Hence my posting to a group that has vb in the title but no other   
   qualifiers.   
      
   I'm actually very sorry I moved from vb5 to .net.   
   I was forced to do it for a Uni course I was doing.   
   Since then I have not been able to write MS Office interactions and now   
   there is this autoproxy issue. In vb5 I would have had this project done   
   in under a week. In .net it looks like not getting done at all.   
      
   I will probably have to fall back on plain old HTML and PHP to build the   
   user interface. Thats so 10 years ago, but it seems to be my only   
   option.   
      
   --   
   DM   
   personal opinion only   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|