title: Using ASP.NET they way it's designed to be used
body: <p>A couple of weeks ago I asked a question and I got totally slammed for using an ancient datastructure. I got questions why I didn't use ado.net and stored procedures, and many others. This had acctually been bothering me for a month, as I'm not very used to ADO.NET, or stored prodcedures. I have only done php programming when coding for the web. </p>
  
  <p><em><strong>Therefore would you please tell me(dont have to do it in detail) how I should structure/model my ASP.NET page.</em></strong> </p>
  
  <p><strong>Today it works like this.</strong></p>
  
  <ul>
  <li><p>I have a webservice file filled with all my methods, these methods INSERT, UPDATE, DELTE and FETCH data. From my codebehind file I invoke the webserive class, and pass things from the webform. </p></li>
  <li><p>I do use a stored procedure for checking the login and password.</p>
  
  <ol>
  <li>Should I only be going for stored procedures?</li>
  <li>SHould I add something if that's the case what?</li>
  <li>Shoudl I let the webforms go directly from the codebehind to the database?</li>
  <li>How whould I implement ADO.NET?</li>
  </ol></li>
  </ul>