What would be more benefical to learn 1st in .NET...any ideas?

OK, I've played with web services. Can use them.
Have played with IIS and ASP.NET can do that.
Can do basic DB stuff, only loading into Datasets and executing SQL string commands.

What I want to do is go right back to basics and look at one things and build up my skills in that area. Although what area I do not know.

Does anyone have any suggestions and what would be the most beneficial area to start learning? SQL, Datasets and databinding? Strongly typed datasets (that's somthing I will look at in a second), DLLs, more web service? Using datasets to update DB's??? or something else?

Woof

Datasets and databinding I guess....

Webservices are great, but in .Net they're pretty straitforward, so even if you know how to make a basic webservice, you pretty much have it nailed anyway.

As far as strongly-typed datasets....

They are faster than untyped datasets that do late-binding.

Early-binded untyped datasets are of course faster than strongly typed datasets. Early binding being a misnomer in this case, but anyway, you are directly mapping the resultant output to a field or variable, and using ordinal indexing for speed.


For instance, the below code runs faster than strongly-typed datasets...

VB Code:

Dim SqlConnection1 As New SqlClient.SqlConnection(Application("SQLConnectionString"))
            Dim SqlCommand1 As New SqlClient.SqlCommand
 
            SqlCommand1.CommandText = "dbo.[CitationSearch]"
            SqlCommand1.CommandType = System.Data.CommandType.StoredProcedure
            SqlCommand1.Connection = SqlConnection1
 
            SqlCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@fk_User", System.Data.SqlDbType.Int, 4))
            SqlCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@SearchString", System.Data.SqlDbType.VarChar, 50))
            SqlCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@DaysBack", System.Data.SqlDbType.Int, 4))
            SqlCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IsUnpaidPaidOnly", System.Data.SqlDbType.Bit, 1))
            SqlCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IsOverdueOnly", System.Data.SqlDbType.Bit, 1))
          
            With SqlCommand1.Parameters
                .Item(0).Value = Me.Session.Item("userguid")
                If Not Me.tbSearch.Text = String.Empty Then .Item(1).Value = Me.tbSearch.Text
                If Not Me.RadioButtonList1.SelectedValue.Length < 1 Then
                    If Not Me.RadioButtonList1.SelectedValue = "No Limit" Then
                        .Item(2).Value = Integer.Parse(Me.RadioButtonList1.SelectedValue)
                    End If
                End If
 
                .Item(3).Value = Me.cbUnpaidOnly.Checked
                .Item(4).Value = Me.cbOverDueOnly.Checked
            End With
            Dim dr As System.Data.SqlClient.SqlDataReader
            SqlConnection1.Open()
            dr = SqlCommand1.ExecuteReader(CommandBehavior.CloseConnection)
            Me.SearchResultsStatusPanel.Visible = True
            If Not dr.HasRows Then
                Me.lblNoResults.Visible = True
                Me.lblSearchResults.Visible = False
                Me.SearchResultsPanel.Visible = False
            Else
                Me.lblSearchResults.Visible = True
                Me.lblNoResults.Visible = False
                Me.SearchResultsPanel.Visible = True
            End If
 
            Me.SearchResultRepeater.DataSource = dr
            Me.SearchResultRepeater.DataBind()

I would say the OOD. There is alot of powering in mastering all aspects of it.