Nov 06, 2006 01:59 PM|shados|LINK
Oh, I'd like to put things into perspective, too:
Even with ALL these hurdles... VWD is pretty user friendly, comparatively speaking. Sorry web development is a mess, but compared to what we've been dealing with, this is easy:
Lets take, let say, PHP/MYSQL: If i take one of the free editors out there, and want to test it locally. Typically (maybe something new recently came out, but I'm going from my own experience with it), you have to manually install a AMP kit (apache/mysql/php)
separately. Then code in your IDE. Copy your files to the server. Test. Code some more. Copy again, test. (I guess you can have your project straight in your web directory, but how friendly is that). Then when you need to export to your server, need to make
sure all versions are compatible. Then you need to script your database, execute the script there, paste the files, edit your connections, pray it works.
Its a far cry from being able to run your app by just hitting F5, having a full blow database and database management tools for free handy, and the possibility to just copy paste the whole deal (including the database!) to www.vwdhosting.net/ for -FREE-
(see? its time limited, but its free and made for newbies) and have it work virtually on first try.
So no matter what hassles you would get into, you're gonna get them in other environments. So VWD is -very- newbie friendly, relatively to what the industry is making us deal with =P Hell, in Visual Studio 2003 you could only do web debugging if you had
Windows XP -Professional- (no home!) or Win2k, and had to install IIS locally to boot! Oh, and you didn't have any good tools to manage your database, which you had to install separately (MSDE).