Hi John,

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

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

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.

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.

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.

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.

Best Regards,
jmu



>I see VS .Net as being at the beginning of an evolutionary path. With respect to windows apps, do I think it abandoning VFP in favor or VS .Net for windows/desktop apps is warranted in the next 12 months? No. Do I think folks, for learning purposes give it a shot? Yes.
>
>Having used VB for about 8 years, the form designer in VS .Net is light years ahead of VB 6. The fact that a full OO model has been implemented is enough to grab my attention. While a containership model does not exist ala VFP's, I think that is a minor speed bump. With respect to binding, the best way of handling that may be yet to be determined. Still, there is a lot to be excited about. The integration with the OS, ability to build windows services, etc. There is usually a marked difference between how the inventor envisions a tool being implemented and how the tool will be implemented.
>
>As far as the languages are concerned, I am backing off my stance that VB .Net would be a better alternative. Looking at the language spec, I think C# does look appealing. After all, looking at a simple variable declaration, which would you prefer: