>It sounds like you're further along than most in terms of learning VS .NET.

Yea... I am on page 2 of chapter 1 ...< bg >... Seriously, I am at the beginning like everybody else.

>
>Perhaps we could start a thread somewhere in UT on learning VS .NET.
>

hmmm this may have to take a back seat to the new awards..< bg >... It would be a worth while topic...


>For example, even after having read through and tried many examples and tutorials, I have not been able to figure out how to easily drag/drop data-bound controls on a web form. One would expect that there would be a table or view or dataview or dataset or something that lists the fields in a DB table/view. One could then drag/drop these DB fields onto a Web Form, and the textbox controls would be automatically created bound to the DB, and labels created on the Web Form based on the DB field name.
>
>I'm pretty sure you could do this with Visual InterDev 6. But I can't figure this out with VS .NET.
>

Right now, I am concentrating more on Windows Forms. Rick has been diving into Web Forms more (I believe). For the most part, you are dealing with the same designers - althrough you do steal with the limitations of the browswer with web forms.

>More to the point, I have searched the Internet for a good VS .NET forum, and have not found one. I have tried the MSFT public newsgroups on vsnet and dotnet, but the response is very poor.
>

It is still early on. Developers are really left to their own devices. This is a void I am helping to fill.


>UT has forums combining the old ASP and VB with .NET. But it seems like it would be better to have forums dedicated to .NET.
>

I agree... Especially when it comes to building web services in ASP .Net


>
IAC, I would greatly appreciate it if you can point me to resources, books, examples, tutorials on learning VS .NET. I had been leaning more toward VB.NET (since I know nothing about VC++), thinking it would be easier to learn than C#.net. But maybe not.
>

C# is pretty easy. You don't need to know C, C++, or Pascal to understand C#. The key is this: the object model is in the .Net framework - not the language. Think of the language that you use to implement the .Net framework. Right now, I am switching back and forth between VB and C#. Working in the form designer, VB is fine. Building classes - C# is nicer to worth with. With this go around, you cannot mix and match languages in a VS project. It really does not matter because you can create classes in a project and implement them in other projects - regardless of langauge. I am not there yet - but it all looks pretty cool!