With XML messaging and DOM - server software is no longer linked to the tool for the GUI.

It doesn't matter.

I purchased a domain service that included ASP. So for that one, I use ASP. I am doing a project using foxISAPI and a VFP server (MTDLL). The VFP server transacts with JavaScript/HTML GUIs. Two of my VFP desktop apps comminicate with an ASP server. Go figure.

It doesn't matter - unless you sell LINUX or NET services - most of the web services - in 90% of the market - need little more than plain manilla ASP.

The nice thing about a VFP server (foxISAPI) is that all the neat things about VFP are available - like DBF cursors - XML messaging - DBF or SQL table transactions.

There are also products, like ActiveVFP and West Wind that include ASP and NET handles.

But most off the rack DNS shops have very good deals with ASP - and it does a great job. You can google around and get "scripts" for the kinds of ASP service you need. For NET as well!

But - it really doesn't matter - and - when your capacity gets to the point it does matter - you can notch it to the next level.

>Our marketing department wants to create a new website to promote our business. They seem to think that using ASP to create this site is the best way to go. Most of the informaion is static, but I know that their long term goals are to make the pages dynamic by reading and writing information to tables etc...
>
>How viable would it be to write the website using Active Server Pages vs Asp.Net?
>
>I know everyone has their favorite technologies, but is ASP still being developed? For a brand new website, is ASP the best choice long term?
>
>Thanks,
>
>Jerry