re:
If you only work on web applications, is there any compelling reason to go with VS'05 over VWD
Express? I'm still fuzzy on the specific differences between them.
You can't develop desktop and console apps with VWD.
Here's a list of the main differences between VWD and VS 2005 :
a) Class Library Project Support (note: you can build classes with VWD
-- but you can't compile them into a standalone assembly directly in the IDE).
b) Web Compilation Support (note: you get full intellisense and compilation checking on
F5/Ctrl-F5 with VWD -- you just can't pre-compile the site into a single set of compiled DLLs
for deployment without source files).
c) Source control support (integrated IDE support is only available in higher VS skus)
d) Mobile Web Support (no WYSIWYG support for mobile controls)
e) Accessibility checker (ASP.NET will emit 508/WCAG accessible markup
-- but express doesn't include the built-in accessibility checker for the IDE)
f) Localization support (this is provided at runtime by ASP.NET -- but express doesn't
include the built-in resource stripping functionality to easily localize sites; note that VWD
itself will be localized into 8 separate languages).
g) Unit Testing support (both class and web project unit testing are only available in the higher
skus).
h) Class Designer
i) Web Load Testing
j) Remote Debugging (note: local debugging - including to IIS -- is fully supported)
k) Windows Forms and Console Library Support
HTH...
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================