StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2436744
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-13T00:33:00.253
FavoriteCount
0
LastActivityDate
2010-03-13T00:55:05.483
LastEditDate
2010-03-13T00:55:05.483
LastEditorUserId
31434
OwnerUserId
31434
ParentId
2436586
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
In addition to my previous answer, since you prefer to indicate not to add the columns manually, I suggest you another option: using custom attributes in your properties definition. First, you have to code your custom attribute: MyPropertyAttribute class <pre><code>[AttributeUsage(AttributeTargets.Property)] public class MyPropertyAttribute : Attribute { public enum VisibilityOptions { visible, invisible } private VisibilityOptions visibility = VisibilityOptions.visible; public MyPropertyAttribute(VisibilityOptions visibility) { this.visibility = visibility; } public VisibilityOptions Visibility { get { return visibility; } set { visibility = value; } } } </code></pre> You could use it in your classes, just like this: Foo class <pre><code>public class Foo { private string name; private string surname; [MyPropertyAttribute(MyPropertyAttribute.VisibilityOptions.visible)] public string Name { get { return name; } set { name = value; } } [MyPropertyAttribute(MyPropertyAttribute.VisibilityOptions.invisible)] public string Surname { get { return surname; } set { surname = value; } } } </code></pre> You could write a method, that iterates the properties in your binded objects, using reflection, and test if they are marked as visible or invisible, in order to add or don´t add columns. You could even have a custom DataGridView with this behavior, so you don´t have to repeat this everytime. You´ll only to use your custom DataGridView, and mark the visibility in the properties. Something like this... <pre><code>public class MyCustomDataGridView : DataGridView { public MyCustomDataGridView() { this.AutoGenerateColumns = false; } public void Load<T>(ICollection<T> collection) { foreach(object myAttribute in typeof(T).GetCustomAttributes(typeof(MyPropertyAttribute).GetType(), true)) { if (((MyPropertyAttribute)myAttribute).Visibility == MyPropertyAttribute.VisibilityOptions.visible) { //... } } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODatabind List Of Objects To A WinForms DataGridView, But Not Show Certain Public Properties
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJavier
UserOwnerUserId
1. USJavier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.