Convert obsolete properties after upgrading to v16.1 ASP.NET

Posted by: The ASPx Blog, on 24 Jun 2016 | View original | Bookmarked: 0 time(s)

In the v16.1 release, we decided to mark older properties of several of ASP.NET controls as obsolete. And for properties older than couple of years, they're marked explicity as IsError:... the compiler will treat usage of the obsolete program element as an error. -MSDNWhy?Over time, some properties of our ASP.NET controls get moved, replaced, or removed. This happens when we introduce a new feature or refactor old code. Usually, we'll add a recommendation in the release notes for you to...

Category: .NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 248 | Hits: 7

Similar Posts

  • Quick and painless Byte Array to Image converter for RadGridView for Silverlight more
  • Exposing Custom WCF Headers through WCF Behaviors - Part 2 more
  • Silverlight IValueConverter vs. TypeConverter more
  • Using the power of binding to animate changes more
  • 4.6.0 A Sneak Peek (3) - IHydratable part 1 more
  • Web Application Project Conversion more
  • Web Application Project Conversion on Orcas more
  • Looking Forward to next AjaxPro Release more
  • Finally - ASP.NET AJAX Control Toolkit Released more
  • List<T>.ConvertAll<>() more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | 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