Hi;

I don't know if VS.Net will be better than DreamWeaver for VFP/SQL - I probably won't install it 'till it's finally released. I suspect it'll be OK for SQL. A client recently used ASP.Net to put together an in-house app in two weeks which I coulda put together in two days using DreamWeaver, VFP7 and WebConnect.

So... I cannot speak to .NET yet - but DreamWeaver really allows you to create great visually designed pages, and easily insert ASP or VFP scripting into them.

I share your assessment of FrontPage. It really adds a lot of garbage to the HTML, and requires those bulky server extensions ... yech.

>Hi All
>
>I am new to web dev (other than an unsatisfactory trial of FrontPage). I am doing a little research to figure out what authoring tool I should use. Macromedia's Dreamweaver seems like an odds on favorite.
>
>But then I started wondering about Visual Studio.Net and InterDev. It seems to me that maybe VS is probably a better tool for building non VFP COM objects and non VFP server side scripting. But since I will build VFP COM objects and use VFP and SQL for datastores, do I really gain any benefit from VS.Net?
>
>Also it seems that the actual web page creation and maintenance may is faster and easier in Dreamweaver. ...or do I have it completely wrong?
>
>Anybody have an thoughts on this? Would appreciate having your opinion.
>
>Thanks
>Don Lowrey