I am a Windows forms programmer and I am familiar with the VB and VBA programming. Thus, I would like to ask:
** Can I directly start ASP.net without any prior knowlege of the ASP ?
** What is the best material to get learning the ASP.net from introductory level to the advance level?
I have created a basic website using ASP.net VB in order to display a diary of various user inputs to a website, I have created a register page, home page and once the use logs in it will direct them to a user logged in page where the entire contents of the diary database table are displayed, however I want the option when the user logs in the user will be able to see the entries that they have been created or been added to
I have created the following code used to return the entries from the database, basically I am selecting (displaying) for project diary name, start date, the creator of the diary, the diary user from the diary table in the database that the username entry field in the home page is equal to the diary creator or diary user (from the database). I am not too sure how I can relate the usernText.Text in the home page to connect to this page user_logged_in_page.
Code:Code:
ConnectionString="<%$ ConnectionStrings:ConnectionString %>"
SelectCommand="SELECT [DiaryName], [StartDate], [DiaryCreator], [DiaryUser] FROM [Diary] WHERE '" & ~Home_Login/usernText.Text & = DiaryCreator or DiaryUser'">
PropertyName="usernText.Text" Type="String" />
I am a bit confused about the significance of the <form runat="server"> on a page, and its effect on Page and Control life cycles.
For long, I have eliminated any Postbacks or Viewstate from my web forms. I just use web forms to render (often very very complex) UI to the client (composed of server-side controls as well as ExtJs or jQuery widgets etc).
After the UI renders, all interaction with server is asynchronous through web-services or http handlers. So, lately I have started omitting the <form runat="server"> tage also from my web forms.
And to my surprise, the code has NOT broken. The life-cycle events are generated normally on all controls, they have access to normal ASP.NET processing pipeline, and they render perfect;y. As there are no Postbacks, I do not need ViewState or control events
like click etc.
So, can somebody tell me if there's any material difference that <form runat="server"> would make in my scenario, or to ASP.NET page/control life-cycle??