A. Please use a more relevant subject line in future. I almost had this one flagged for spam. It's lucky I check each suspicious mail.
1. Create a separate page and then redirect the user to the second page upon postback (after you have processed inputs). 2. Who goes where first ? Onto the page ? The position on the page of a control is determined by the HTML you write. Assuming that you aren't using CSS to place a control at a specific location on the page, you will find that the browser will render controls as it encounters them in the HTML source (top to bottom, flow layout). 3. Don't let yourself be overwhelmed by the size or complexity of the .NET framework (or for that matter, the MSDN documentation). Hardly anyone can claim more than a passing familiarity with the entire framework. Start out learning small and just be concerned about the namespaces and classes that you encounter each time you learn a little bit more. In other words, don't try to learn everything at once. As Brandon suggested, reading a book on the subject would be a great way to learn a little at a time. And to answer the question, I doubt if there is any such reference because usefulness and relevance of a class or namespace is relative to the type of work you are doing. For instance, if I was working on Windows forms, I wouldn't be too concerned about the System.Web namespace, however, there is no one who can dispute the crucial nature of that namespace. 4. Hmmm... this is more complicated, given your present skill level. Also, parsing an HTML resource for relevant data is not a trivial task. It's better to find a webservice that will return you this data as Brandon suggested. 5. Each page does have a different URL. The URL stays the same between postbacks only because pages by default, postback to themselves. When you redirect to another page or use the PostBackUrl property of a Submit button, you will see the URL change to the new page. On May 6, 12:32 am, Rui <[email protected]> wrote: > Very basic stuff,, they don't intend to be very specific questions, so > if you think they are, then it means i'm probably trying to solve a > general issue in a non-standard way without realising :D, so feel free > to point me straight to what matters :P > > 1) How can I design the webpage the user sees after a postback with > html and or the design view? Example, he clicks a button, submits > stuff, so now i want another thing to appear,,, All I can do is code > in C#/VB for the objects that would then render into the html code? > > 2) in any case, how does .net know when 2 controls (excuse me if i > misuse the words :D ) are siblings, who goes first? for example, if i > wanted a panel to have 2 whatevers inside > > 3) Where can I find a reference of only the most useful (or at least > sorted by relevance) classes in the .net framework for web > development? I'm getting kinda lost and overdosed with the msdn help, > hehehe > > 4) I would like the server to have in a database a more or less > updated value of some currency exchange rates. Main question is... > should i place in the global.asax a code to get it, and a timer to > repeat every X hours? or there's some better way with a windows > service to schedule the task? and if so, can it happen in a shared > server? > secondary question: to get the html of a site, as text, its like > opening a file but with the url instead of the name? any better way? > > 5) In the most standard logical way to code a website with asp.net, > the url stays the same between postbacks? Is there any way, for > example, to code a site with partial refreshing (ajax i guess, > updatepanels, blah) in which each page has a different url? > > thankss > promise i'll help you all when i have the knowledge :)
