Replacing deprecated System.Net.WebProxy.GetDefaultProxy() in .NET 2.0

Posted by: Rick Strahls WebLog, on 11 Jul 2005 | View original

I’m in the final stages of getting my West Wind Web Store app ported over to 2.0 by getting rid of all of the obsolete function calls and other non fatal messages. Frankly most of these deprecated APIs changes are lame and for the most part simple name changes or attaching the same logic to some other object. While I think cleaning up interfaces is not a bad idea, deprecating many of these old apis in this ways is a pain. I know, I know I can turn this off, but this code ships to customers...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.

Similar Posts

  • Vista glass answers and DwmEnableBlurBehindWindow more
  • Transaction support in Workflow Foundation more
  • Adding Master Page Support to Dynamically Created Pages more
  • Monitoring a web site on the local server with a Windows Service more
  • ClientBlocker 1.0 more
  • A generic serialization method more
  • Breaking some rules more
  • My KWhoIs component version 1.0 more
  • Solving "The underlying connection was closed" when using WSE more
  • Writing Custom Webparts for Sharepoint 2007 more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD