brooksr wrote:
Thanks so much for that post, Bob, it's excellent. Probably going to
take some time for me to absorb it all.
Let me ask some follow up questions:
So VBScript and (plain) ASP are 'classic ASP', while VB.NET and
ASP.NET are 'modern' ASP?
Pretty much, yeah.
>
I understand that VB.NET is a part of Visual Studios and that a free
version, VB Express, is available for download and may meet many
developers' needs ...
So server side code resides on a web hosting site that I would use.
If you are not using FP, how do you get the code onto the server? Do
you still 'publish' it somehow?
I do intranet development, so I simply use Visual Interdev to work with my
pages on servers that have Frontpage Server Extensions installed, and simple
filesystem copy/paste for servers that don't. I have heard people saying
they use FTP to publish files to internet web servers. I haven't used VWD (I
use Visual Studio) but I think I heard that it has a publish-via-ftp
function builtin.
>
When you speak of client side, you basically mean a user accessing the
internet via a browser, like IE, correct?
Exactly. The browser is the client.
>
I read that many VB developers and even some book authors were angry
at how Msft changed VB in moving from VB6 to VB.NET, but it seems
like a moot point not worth wasting time on. Also, maybe drastic
changes were necessary to move to a full internet environment ...
No. MS responded to the demads for a more object-oriented VB for VB7, but
found that they could not deliver it without sacrificing backward
compatibility. That is why there was no VB7: it is practically a new
language. Code that worked fine in VB6 will break if attempted to be run
without modification i VB.Net. This is what so many developers are still
upset about
: millions of lines of existing codebase, with millions of
dollars in both time and money, is in jeopardy. Sure, people can still use
VB6 to maintain that code, and, while MS has made a commitment to making
sure the VB runtimes will continue working in new operating systems, the
trust has been broken
>
So is ASP.NET a language?
No. Neither classic ASP nor ASP.Net is a language. They are both "platforms"
that support the use of multiple languages, providing interfaces and classes
(Server, Application, Session, Request and Response objects) that can be
used by these languages. Classic ASP supports the use of scripting languages
such as vbscript, jscript and perlscript. ASP.Net is provided by the .Net
framework and supports the use of any .Net language. You should go to
www.asp.net to read more.
Does it have a wysiwyg interface that can
replace FP's?
WMD has a wysiwyg interface, as does Visual Studio 2005 if you can afford
it.
>
I'm still a little unclear how VWD and VBE relate to one another? If
I learn VWD do I still need VBE? If I need both, which should I learn
first?
WMD provides wizards and functionality to make ASP.Net develpment easy. Any
..Net language can be used. I think VBE is an IDE for VB.Net develpment.
You'll need to ask the experts at
www.asp.net.
>
What is dhtml and how does it differ from html?
html is static markup language.
dhtml = dynamic html. It is a library (actual many libraries) provided by
browsers to provides interfaces for working with html elements in
client-side scripting code. There is a standard DOM (document object model)
library published by the w3c body, but different browsers may or may not
adhere to this standard DOM. IE is notorious for its lack of adherence to
standards. IE7 is suppoed to be better, but they did not want too many
things that worked in IE6 to break in IE7. However, due to security
improvements, many appplications that worked in IE6 need to be rewritten to
work in IE7.
Here is a link to the MS DHTML reference:
http://msdn.microsoft.com/workshop/a...iews_entry.asp
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
