[ASP .NET] Custom Controls

Adron · November 15, 2003, 06:48 PM

Quote from: St0rm.iD on November 15, 2003, 06:42 PM
You can tell it what to run on the server and what on the client using the runat parameter of the listbox.

Of the listbox??

quasi-modo · November 19, 2003, 04:19 PM

ASP.NET its self is server side. It does not do anything client side. You can integrate it with dhtml javascript or vbscript to get some desired affects but ASP.NET is server side. Now, I am not quite clear on the problem here. Is this a problem in how it is displaying or working? If it is not looking good why not just ditch creating the html attributes and use a lil css? Now about the runat commands. If you want to use an html element do not even put the runat in there and just make the html element. To make an html element runat the server then you use runat="server". But do not try to make a <asp:listbox run at the client level, just go ahead and do that in html.

Banana fanna fo fanna · November 19, 2003, 04:56 PM

Quote from: peofeoknight on November 19, 2003, 04:19 PM
ASP.NET its self is server side. It does not do anything client side. You can integrate it with dhtml javascript or vbscript to get some desired affects but ASP.NET is server side. Now, I am not quite clear on the problem here. Is this a problem in how it is displaying or working? If it is not looking good why not just ditch creating the html attributes and use a lil css? Now about the runat commands. If you want to use an html element do not even put the runat in there and just make the html element. To make an html element runat the server then you use runat="server". But do not try to make a <asp:listbox run at the client level, just go ahead and do that in html.

It runs serverside, but decides what to send to the client and how to make it interact with the server correctly.

CupHead · November 19, 2003, 05:02 PM

Quote from: peofeoknight on November 19, 2003, 04:19 PM
ASP.NET its self is server side. It does not do anything client side. You can integrate it with dhtml javascript or vbscript to get some desired affects but ASP.NET is server side. Now, I am not quite clear on the problem here. Is this a problem in how it is displaying or working? If it is not looking good why not just ditch creating the html attributes and use a lil css? Now about the runat commands. If you want to use an html element do not even put the runat in there and just make the html element. To make an html element runat the server then you use runat="server". But do not try to make a <asp:listbox run at the client level, just go ahead and do that in html.

There is no problem, I was just demonstrating the ASP .NET stuff.

quasi-modo · November 19, 2003, 05:41 PM

Quote from: St0rm.iD on November 19, 2003, 04:56 PMIt runs serverside, but decides what to send to the client and how to make it interact with the server correctly.

The server outputs html generally with a little java script from time to time. I have not seen much java script other than the required feild validators. The whole point of using a server side language for scripting is to escape client side scripting which is not as accessable and not secure. You can type raw javascript, dhtml, css etc into your asp.net files after the </script><html> tags all you want and the server is not going to screw with it at all unless you are putting in includes or <asp: elements.

Here is the only server genorated java script that is on the default page for my clan's site
<script language="javascript" src="/aspnet_client/system_web/1_1_4322/WebUIValidation.js"></script>
Its just importing the validation sontrols etc.

Valhalla Legends Archive

[ASP .NET] Custom Controls

Adron

quasi-modo

Banana fanna fo fanna

CupHead

quasi-modo