<p>As I browse through the site, I find a lot of terms that many developers just starting out (and even some advanced developers) may be unfamiliar with.</p>

<p>It would be great if people could post here with a term and definition that might be unknown to beginners or those from different programming backgrounds. </p>

<p>Some not-so-common terms I've seen are 'auto boxing', 'tuples', 'orthogonal code', 'domain driven design', 'test driven development', etc.</p>

<p>Code snippets would also be helpful where applicable..</p>

[{'answer_id': 15717, 'author': 'Matt Hamilton', 'author_id': 615, 'author_profile': 'https://Stackoverflow.com/users/615', 'pm_score': 0, 'selected': False, 'text': '<p>Just so I\'m clear, you\'ve done something like this, right?</p>\n\n<pre><code>public ListView MyListView { get { return this.listView1; } }\n</code></pre>\n\n<p>So then you are accessing (at design time) the MyListView property on your UserControl?</p>\n\n<p>I think if you want proper design-time support you\'re better off changing the "Modifier" property on the ListView itself (back on the original UserControl) to Public - that way you can modify the ListView directly on instances of the UserControl. I\'ve had success doing that anyway.</p>\n'}, {'answer_id': 15803, 'author': 'Fredrik Kalseth', 'author_id': 1710, 'author_profile': 'https://Stackoverflow.com/users/1710', 'pm_score': 4, 'selected': True, 'text': "<p>You need to decorate the ListView property with the DesignerSerializationVisibility attribute, like so:</p>\n\n<pre><code>[DesignerSerializationVisibility(DesignerSerializationVisibility.Content)]\npublic ListView MyListView { get { return this.listView1; } }\n</code></pre>\n\n<p>This tells the designer's code generator to output code for it.</p>\n"}, {'answer_id': 15832, 'author': 'Rob Cooper', 'author_id': 832, 'author_profile': 'https://Stackoverflow.com/users/832', 'pm_score': 1, 'selected': False, 'text': '<p><a href="https://stackoverflow.com/questions/15716/design-problems-with-net-usercontrol#15803">Fredrik</a> is right, basically, when you need to enable the designer to persist the property to page so it can be instantiated at run time. There is only one way to do this, and that is to write its values to the ASPX page, which is then picked up by the runtime.</p>\n\n<p>Otherwise, the control will simply revert to its default state each and every time.</p>\n\n<p>Always keep in the back of your mind that the Page (and its contents) and the code are completely seperate in ASP.NET, they are hooked up at run time. This means that you dont get the nice code-behind designer support like you do in a WinForms app (where the form is an instance of an object).</p>\n'}]
['https://Stackoverflow.com/questions/15729', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/1693/']