I am New of ASP.Net
What we can and should do client side and Server Side? What uses?
Please any one clear my doubt.
Thanking You
Endendrum Priyamudan
       P m R
  

Clientside is basically what a person can see and serverside is where actions get processed.
that's kinda simply puyt but thats the deal, you code serverside, and the html and javascript it generates let's the users for example click a button, then serverside you have coded what should happen when a button gets clicked for example turn text red. Then the server sends a new page with red text to the client (clientside) etc.
Greetings,

F.B. ten Kate

ps. Don't forget to mark helpfull replies as answer

Hi,
Client side refers to the browser which is viewing the web page delivered by the server.  This is HTML and Javascript, maybe Shockwave flash, maybe Silverlight.
Server side refers to the application on the web server which delivers the web page content.
In brief:
Server side: Create and deliver the HTML and Javascript
Client side: Request the page, receive the page from the server, then display the HTML and process the Javascript. 

Browsers are Client and your Application is Hosted on Server
When in the browser user types a URL of ur server 
The Server Accepts the Requests Procecess it and sends the Response Back . This is Server Side Processing (Generally C# or VB Code)
The Browser recieves the response and is displayed as a Page in the browser 
Along with the page some scripts are also downloaded from the server These scripts are loaded in the browsers memory and execute on ur Browser on ur machine without any interaction with server
This is Client Side Processing (Generally Javascript VB Script)
MAK
Mark as Answer if this reply helps you

MVP ASP/ASP.Net
ASP.Net Hosting : Host Depot
My Site : ASPSnippets

 http://www.motive.co.nz/glossary/client-server.php
http://www.websiteowner.info/articles/cgi/whichside.asp 
 Hope this will help you

Hi,
You will find that the controls when you move in the design to a form, they say runat="Server", to see this click in source.  Do not worry about that.  
What it means is that the ASP act as a server and will return you the a page in HTML to your browser with the information resolved for that control, and what you see in the browser is the client side.
I hope it help you to understand this issue.  Also yopu can check the ASP net videos that explain this, you can download them in the home page of this site.
Javier.
 

Difference between "Client Side" and "Server Side"
Explain the differences between Server-side and Client-side code?  
 
http://www.munishbhatia.com

 Mohanet:
What we can and should do client side and Server Side? What uses?
 
There are tons of articles in the net that talks about it, I would suggest you to google the term to get more information.
http://www.google.com/search?hl=en&q=Client+Side+VS+Server+Side+code+in+asp+net&btnG=Search 
 
Regards,Vinz

"Code, Beer and Music" that's my way of being a programmer!

How to get your Forum Question Answered | Blog | CodeASP.NET

 Wikkipedia has a relevant article on client-side/server-side at http://en.wikipedia.org/wiki/Client-server
Don't forget to click "Mark as Answer" on the post that helped you.
This credits that member, earns you a point and marks your thread as Resolved so we will all know you have been helped. 

simplest definition : ClientSide is where the browser request for a website, Server side is where the website is hosted.
Always remember to click “Mark as Answer” on the post that helps you. Thank you!

- Regards,
Paresh Jagatia
http://pareshjagatia.blogspot.com

Understanding the difference between "Client Side" and "Server Side" 

We get so many inane questions that revolve around this subject that I decided to try and be more helpful by providing a sort of "reference" document that will enable people who may be confused to read up a bit and save everybody some time. In fact, its more of a selfish move on our part, since now if I can get most of the information into this document, then the next time somebody asks another one of these questions, all we have to do is point them to this article. 

First, the simple explanation: 

Client side is what's happening on your computer in your browser. It has nothing to do with the server, or ASP or ASPX pages, or IIS, or the database, or ANYTHING ELSE. JavaScript in a web page would be an example of something client side. You don't need the server to help with the functionality of the script. If you can run it on your computer (without a server being installed) and it works, it's client side. In fact, when a web page is sitting in your browser after it has been processed by the server and sent "over the wire", there is absolutely no further connection with the server whatsoever at this point. NONE! ZERO! NADA, ZIP! The page in your browser has absolutely NO KNOWLEDGE of the server or what may be going on there, and conversely, the web server machine that served the page to your browser hasn't got the slightest idea of who you are or where you are, or whether you ever even visited the web site at all! The Web is Stateless, my son -- just like your mind on a Spring Saturday afternoon! May all your methods return, etc. etc. 

Server side is when the server is being used to process something. Script or code that is run on the server does NOT appear on or in the web page that is sent to your browser -- the web page that your browser receives is only the RESULT of the script or database code or processing that happened on the server. 

With these two beliefs firmly fixed in our minds like concrete sticking to the sides of the Grand Coulee Dam, let's take it down to the next level and get into a few more details. Client side code is usually (but not always) Javascript. Forget about writing to the user's hard drive, or saving a file somewhere, or writing to the user's Registry with client - side script. It ain't gonna happen. Browser vendors have tightened up security restrictions to the point where unless you are exploiting some security hole that hasn't been patched, you may as well forget about these types of things. Forget about downloading files and depositing them on the user's hard drive and having them run. No way, DUDE! 

Now let's say you have a textbox in a web page and you want to use client side code to make something happen. For example, every time somebody types another letter in a text field, you want to go out and search your database and come back and fill a listbox with the closest matches. Can you do this with client side code? 

Client side code triggering Server Side processing 

Well, yes and no. Remember the page doesn't have any further connection with the server that sent it to the browser. However the client side code CAN cause, for example, a form on the page to activate its submit method, and if the ACTION atttribute of the form points to a page that will receive the form posts and generate the return data, it can be done. However too many people continue to make the fallacious assumption that some client - side event, such as selecting a listbox item, or the onblur event of leaving the focus from one control is going to enable them to get server - side code or events to run. What it MAY do is create a post or "postback" event. This really means we have made a NEW TRIP to the webserver with some specific information that the SERVER SIDE code is prepared to react to, and it will regenerate the page and send it back to the browser. With Smartnavigation and other features, it may appear the page has not really been reloaded, but 99% of the time, it has. 


The only exception to the above is when we use COM components from the CLIENT, such as XMLHTTP, to issue their own GET or POST action to a receiving web page on the SERVER, which sends back new information. The component receives this without a page reload, and using DHTML, we can update client-side DOM items in the page. Another technique is to use hidden IFRAMES to perform similar actions "behind the scenes" and receive data. However, the data must be requested from the same domain the page was requested from, or security restrictions will prevent our access to the data in the IFRAME. Newer implementations of "Remote Scripting", which was invented by Microsoft about 1998 are using the term "AJAX". This is just a buzzword for remote scripting or "Script Callbacks" which are now built into ASP.NET 2.0. 


So! The next time you want to ask a question about an event or how to "do something in a web page" the very first thing you should be thinking about is whether this is a client side or a server side event we are dealing with. Happy Coding!
By
PT.Sivakumar
India

 hi ! 
      refer this site
      http://www.librarywebchic.net/wordpress/stories-tutorials-and-code-demonstrations/server-side-and-client-side-includes-explanations-applications-and-examples/
 

 ptsivakumar:
Understanding the difference between "Client Side" and "Server Side" 

We get so many inane questions that revolve around this subject that I decided to try and be more helpful by providing a sort of "reference" document that will enable people who may be confused to read up a bit and save everybody some time. In fact, its more of a selfish move on our part, since now if I can get most of the information into this document, then the next time somebody asks another one of these questions, all we have to do is point them to this article. 

First, the simple explanation: 

Client side is what's happening on your computer in your browser. It has nothing to do with the server, or ASP or ASPX pages, or IIS, or the database, or ANYTHING ELSE. JavaScript in a web page would be an example of something client side. You don't need the server to help with the functionality of the script. If you can run it on your computer (without a server being installed) and it works, it's client side. In fact, when a web page is sitting in your browser after it has been processed by the server and sent "over the wire", there is absolutely no further connection with the server whatsoever at this point. NONE! ZERO! NADA, ZIP! The page in your browser has absolutely NO KNOWLEDGE of the server or what may be going on there, and conversely, the web server machine that served the page to your browser hasn't got the slightest idea of who you are or where you are, or whether you ever even visited the web site at all! The Web is Stateless, my son -- just like your mind on a Spring Saturday afternoon! May all your methods return, etc. etc. 

Server side is when the server is being used to process something. Script or code that is run on the server does NOT appear on or in the web page that is sent to your browser -- the web page that your browser receives is only the RESULT of the script or database code or processing that happened on the server. 

With these two beliefs firmly fixed in our minds like concrete sticking to the sides of the Grand Coulee Dam, let's take it down to the next level and get into a few more details. Client side code is usually (but not always) Javascript. Forget about writing to the user's hard drive, or saving a file somewhere, or writing to the user's Registry with client - side script. It ain't gonna happen. Browser vendors have tightened up security restrictions to the point where unless you are exploiting some security hole that hasn't been patched, you may as well forget about these types of things. Forget about downloading files and depositing them on the user's hard drive and having them run. No way, DUDE! 

Now let's say you have a textbox in a web page and you want to use client side code to make something happen. For example, every time somebody types another letter in a text field, you want to go out and search your database and come back and fill a listbox with the closest matches. Can you do this with client side code? 

Client side code triggering Server Side processing 

Well, yes and no. Remember the page doesn't have any further connection with the server that sent it to the browser. However the client side code CAN cause, for example, a form on the page to activate its submit method, and if the ACTION atttribute of the form points to a page that will receive the form posts and generate the return data, it can be done. However too many people continue to make the fallacious assumption that some client - side event, such as selecting a listbox item, or the onblur event of leaving the focus from one control is going to enable them to get server - side code or events to run. What it MAY do is create a post or "postback" event. This really means we have made a NEW TRIP to the webserver with some specific information that the SERVER SIDE code is prepared to react to, and it will regenerate the page and send it back to the browser. With Smartnavigation and other features, it may appear the page has not really been reloaded, but 99% of the time, it has. 


The only exception to the above is when we use COM components from the CLIENT, such as XMLHTTP, to issue their own GET or POST action to a receiving web page on the SERVER, which sends back new information. The component receives this without a page reload, and using DHTML, we can update client-side DOM items in the page. Another technique is to use hidden IFRAMES to perform similar actions "behind the scenes" and receive data. However, the data must be requested from the same domain the page was requested from, or security restrictions will prevent our access to the data in the IFRAME. Newer implementations of "Remote Scripting", which was invented by Microsoft about 1998 are using the term "AJAX". This is just a buzzword for remote scripting or "Script Callbacks" which are now built into ASP.NET 2.0. 


So! The next time you want to ask a question about an event or how to "do something in a web page" the very first thing you should be thinking about is whether this is a client side or a server side event we are dealing with. Happy Coding!
 
Nice quote.
I feel it would have been simpler to reference (and possibly credit) the source article though:
http://www.eggheadcafe.com/PrintSearchContent.asp?LINKID=569

Thank You So much.
Ok What all we can do in Client side & what all in Server side
Endendrum Priyamudan
       P m R
  

Thank You.
Ok .Net has two type of controls Html and Asp.net Controls for design.
When are we using HTML & when is ASP.Net Controls Differenciate?
Endendrum Priyamudan
       P m R
  

 
 Mohanet:
Thank You So much.
Ok What all we can do in Client side & what all in Server side
What do you want to do? You can do loads on the client side, and much much more on the server side - it really depends what you want to do, that will determine whether it's client or server. 

hi !

    refer this for server side scripting
http://www.w3schools.com/web/web_scripting.asp
    refer this for client side scripting
http://htmlhelp.com/reference/html40/special/script.html
    if it helps you then mark it as a answer so others can make use of it...

the things which runs in browser are client side(Code like-ajax, Scripts) and server contains logic's and business functions....  

 Mohanet:
Thank You.
Ok .Net has two type of controls Html and Asp.net Controls for design.
When are we using HTML & when is ASP.Net Controls Differenciate?
 
ASP.Net controls generate HTML for you, and they make it easier to manipulate the HTML before sending it to the client.
You should have little/no requirement to use basic HTML controls when creating an ASP.Net web page. 

hi !

    refer this to get the basic idea about Html controls & asp.net controls

http://www.extremeexperts.com/Net/FAQ/DiffBetweenServerandHTMLControls.aspx