thanks.

Check out the MSDN Library.  Along with the API, it has a lot of good references and tutorials.

http://msdn.microsoft.com/en-us/library/default.aspx

If you can't find what you need by doing a Google search, you can always just ask here, or on the MSDN or CodeProject forums:

http://social.msdn.microsoft.com/Forums/en-US/categories

http://www.codeproject.com/script/Forums/List.aspx

NotSoTragicHero said:

A few places.

 

Check out the MSDN Library.  Along with the API, it has a lot of good references and tutorials.

http://msdn.microsoft.com/en-us/library/default.aspx

 

If you can't find what you need by doing a Google search, you can always just ask here, or on the MSDN or CodeProject forums:

http://social.msdn.microsoft.com/Forums/en-US/categories

http://www.codeproject.com/script/Forums/List.aspx

Ok. I just went to the MSDN and looked up DataTable and it gave me this:

Dim workTable as DataTable = New DataTable("Customers")

And says the new DataTable is now called Customers. So what does that make workTable? Why can't I just say:

Dim Customers as DataTable.

Contrary to some older languages, like VB6, most functions in .NET are in the class that they work on. So where in VB6 you'd call UCase$("hello") to get "HELLO", in .NET you'd say Dim s as String = "hello", s.ToUpper() to get "HELLO". Intellisense is great for discovering these things. Just make a variable and type a dot after it. The list of functions will pop up and you can hover over them to get basic descriptions.

edit: for your question about DataTables,

Dim workTable as DataTable = New DataTable("Customers")

creates a new DataTable object, referenced by the variable "workTable", with a Name property of "Customers". If this table was in a DataSet referenced by ds, you could then type ds.Tables("Customers") to get a reference to the table.

Dim customers as DataTable

doesn't create any object at all.

Dim customers as New DataTable() (or Dim customers as DataTable = New DataTable(); same thing)

creates a new DataTable that has nothing in its Name property.

It sounds like you're not too experienced with object-oriented programming. This is required knowledge for understanding and programming with the .NET platform.

I'm sure somebody here can recommend a good book to get you started on .Net and OO concepts.

Sven Groot said:

To be honest, it sounds like you'd benefit from some tutorials or introductory books rather than trying to learn from reference materials. Just using reference materials is possible if you have a reasonable understanding of the fundamentals, but it sounds like you're not quite there yet.

 

I'm sure somebody here can recommend a good book to get you started on .Net and OO concepts.

That makes sense. I really don't get to do much new stuff at work. Once I told them I wanted to learn the .Net programming they gave me existing programs to maintain. So when I go look at them I really don't see much I understand. I think a book that gave you projects to complete so that instead of just reading about how it works I would have projects to complete that would allow me to use the new techniques. So like, read a chapter on some feature, then here's a project that makes you code using that feature. Something like that I think would work well.

pdcjlw1 said:

Sven Groot said:

*snip*

That makes sense. I really don't get to do much new stuff at work. Once I told them I wanted to learn the .Net programming they gave me existing programs to maintain. So when I go look at them I really don't see much I understand. I think a book that gave you projects to complete so that instead of just reading about how it works I would have projects to complete that would allow me to use the new techniques. So like, read a chapter on some feature, then here's a project that makes you code using that feature. Something like that I think would work well.

Wrox's Beginning series tends to do that, building up an app or two as you go through the chapters. Well, excluding Beginning ASP.NET Security, because that approach didn't fit.

So the way you know might work, but your app's future coders will hate you for it.