Properties vs Fields Why Does it Matter? (Jonathan Aneja)

Posted by: The Visual Basic Team, on 04 Sep 2009 | View original | Bookmarked: 0 time(s)

The other day I got an email from a developer asking an interesting question about VB10s Auto-implemented Properties feature. I am, however, somewhat confused regarding the properties feature you mentioned - i.e. turning 11 lines of get/set/backing variable into one line. Wouldn't this be exactly the same as the existing functionality of creating a public variable? I see no benefit for using a property in this case, except perhaps for the sake of what some would consider best practice. On...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: VB.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 733 | Hits: 62

Similar Posts

  • Using T4 Templates for Simple DTOs more
  • Visual Studio Add-In vs. Integration Package Part 1 more
  • VSTO: Office System Power Tools (VSTO Power Tool) more
  • Visual Studio Tools for Office Power Tools v1.0! more
  • ASP.NET Personal Web Site Starter Kit - Ajax Enabled with .NET Framework 3.5 and VS2008 more
  • Extending Visual Studio, and open source more
  • Open Source and Visual Studio more
  • Retrieving a CodeElement reliably in VS.NET 2005 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