G
Guest
Hey all.
I'm fairly well versed in classic ASP, and I'm trying to teach myself
ASP.Net. I have a book - which isn't very good - and I'm kind of trudging
through. I haven't been working at this for very long, but I already have
some questions. If someone could help me out or point me in the right
direction, I'd appreciate it.
1) It seems like the philosophy of ASP.Net is to have one gigantic page that
constantly posts back on itself. Instead of moving from page to page, you
simply show and hide different parts of the same page using Panels. Is that
an accurate impression? If so, what is advantageous about that?
2) I'm still confused about these pseudo-HTML controls that have"<asp:" in
front of them. In the book I'm reading, they have one example -
<aspropDownList
id="List1"
runat="Server">
<asp:ListItem>Hour</asp:ListItem>
<asp:ListItem>Minute</asp:ListItem>
<asp:ListItem>Second</asp:ListItem>
</aspropDownList>
And then later on -
<select
id="MySelect"
size="1"
runat="server">
<option>Hour</option>
<option>Minute</option>
<option>Second</option>
</select>
It seems to me that these two things are identical. Why would you have a
need to use something like "<aspropDownList>"? It seems like it would be
harder to create CSS for all these wierd form controls or....whatever they
are....
3) Can a cookie set in ASP.Net be read in classic ASP, and vice versa? Or,
to be more general, are there any dangers in having a web app that contains
both classic ASP and ASP.Net?
Thanks!
I'm fairly well versed in classic ASP, and I'm trying to teach myself
ASP.Net. I have a book - which isn't very good - and I'm kind of trudging
through. I haven't been working at this for very long, but I already have
some questions. If someone could help me out or point me in the right
direction, I'd appreciate it.
1) It seems like the philosophy of ASP.Net is to have one gigantic page that
constantly posts back on itself. Instead of moving from page to page, you
simply show and hide different parts of the same page using Panels. Is that
an accurate impression? If so, what is advantageous about that?
2) I'm still confused about these pseudo-HTML controls that have"<asp:" in
front of them. In the book I'm reading, they have one example -
<aspropDownList
id="List1"
runat="Server">
<asp:ListItem>Hour</asp:ListItem>
<asp:ListItem>Minute</asp:ListItem>
<asp:ListItem>Second</asp:ListItem>
</aspropDownList>
And then later on -
<select
id="MySelect"
size="1"
runat="server">
<option>Hour</option>
<option>Minute</option>
<option>Second</option>
</select>
It seems to me that these two things are identical. Why would you have a
need to use something like "<aspropDownList>"? It seems like it would be
harder to create CSS for all these wierd form controls or....whatever they
are....
3) Can a cookie set in ASP.Net be read in classic ASP, and vice versa? Or,
to be more general, are there any dangers in having a web app that contains
both classic ASP and ASP.Net?
Thanks!