>>I'll agree on the help system to an extent. The ability to have tabbed documents, however, is pretty cool. My biggest dislike (at least in VB.NET) is the fact that the event's and methods (at least at the form level) aren't easily available.
>
>George,
>
>If you go into a VB form, then right click on it, and 'View Code' you are brought into the code editor. On the top of the editor there are two combo boxes. Open the one on the left and choose 'base class events' then in the right combo there is a list of all the forms events. The ones that have code in them are bold (not moved to the top like in VFP). If you want to add code to respond to/handle an event choose the event from the combo and VB will create a procedure to handle that event.
>
>I don't know how much easier you want it. Granted, they aren't on the property window like in VFP, but there are also ALOT more base events in VB.Net.
>
>BOb

BOb;

Thank you for your helpful hints. I can use them and a lot more! I have a long way to go with this product.

I have begun with ASP.NET and I am using a Web form, with HTML and Web (ASP) Controls. The HTML objects are referenced as you pointed out however no ASP.NET objects are referenced in either combo box. Is this the way it should be? I would think consistency would be an objective of an IDE.

Having the PEM’s on one form separate from your code has advantages in my book! If I want to be in Design mode and look at a method too bad! The code takes over the screen and I loose the Design view. Picky, picky, I know but I am spoiled rotten to the core!

I truly thing that the people who developed Visual Studio .NET should have taken a close look at how the developer interface works with Visual FoxPro. Using VFP is still much more efficient. And then there is the HELP System! Oh Lord!

I must remain positive at all times. Well, most of the time would be nice!

Tom