.NET (Core and Framework)

Using connection As New SqlClient.SqlConnection(My.Settings.MyConnectionString)
         Using cmd As New SqlClient.SqlCommand("select * from smartasses where name = @name", connection)
            cmd.Parameters.Add("name", SqlDbType.VarChar, 50).Value = GetUserFromPostAbove()
            connection.Open()
            Try

               Using reader As SqlClient.SqlDataReader = cmd.ExecuteReader
                  While reader.Read
                     Dim gridRow As New DataGridViewRow
                     gridRow.CreateCells(gridSmartAsses)

                     gridRow.Cells(gridSmartAsses.Columns("name").Index).Value = reader.Item("name")
                     gridRow.Cells(gridSmartAsses.Columns("age").Index).Value = reader.Item("age")
                     gridRow.Cells(gridSmartAsses.Columns("message").Index).Value = reader.Item("message")
                     gridRow.Cells(gridSmartAsses.Columns("funny").Index).Value = reader.Item("funny")
                     ' ... Up to about 20 columns.

                     gridSmartAsses.Rows.Add(gridRow)
                  End While
               End Using

            Finally
               connection.Close()
            End Try
         End Using
      End Using

gridRow.Cells(gridSmartAsses.Columns("name").Index).Value = reader.Item("name")

Naerling wrote:

Actually we're all kind of tired of having to type:

I are Troll

Naerling wrote:

These controls can do a lot, but some of them require databinding.

Naerling wrote:

This is something I am not familiar with and neither is my company.

I are Troll

Naerling wrote:

We don't use the settings tab Smile

Naerling wrote:

And I'm not really against code generation as long as I know it is good code.

Naerling wrote:

But selecting two datasources for two datagrids (master/detail) (from the datasources wizard in the designer) generates 6 items on my form and SQL statements such as "DELETE from SomeTable WHERE (every field in that table) = (every field in that table-variable)" even if there is a PK on that table. If I switch datasources in my grid I could end up with identical items called 'DataBindingItem' and 'DataBindingItem1'. And if I use a BindingNavigator I can use a 'Save' button which gives me exceptions rather than messageboxes if I leave some values empty, so I'd still have to write all validation logic (even though it's known from the datasource).
So that's why I was wondering if this wizard for datasources is all that good.

Naerling wrote:

The documentation of our third party tool uses it all the time. Although they give some code examples using DataAdapters too.

Naerling wrote:

Nice MSDN article btw Smile

I are Troll

Eddy Vluggen wrote:

You think that Microsoft would put a generator in Visual Studio that would generate code that would look like it's written by a student?

Naerling wrote:

Pro's: Microsoft generates code for you, it gets the data for you, it only updates rows that are altered, even my boss can do it, it's fast.
Cons: none.

Naerling wrote:

By the way, if I would build up a dataset in code and I wanted to bind, let's say 50 controls to 50 fields, do I have to bind each one of them seperately?

I are Troll