Re: start ASP net from very scratch

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Re:
<< Browser--> Server <--> MywebApp -->Browser, right? >>

Yes - more or less. The big point to understand is that ASP.NET Web
applications do not run inside of browsers. They run on Web servers...

Browser sends a request to the server (for myPage.aspx)
IIS is running on the Web server (it IS the web server) and it receives the
request.
IIS sees that the request is for an .aspx file - and so hands off the
request to ASP.NET for further processing.
ASP.NET then processes the request (any code-behind logic, etc).
ASP.NET ultimately returns plain old HTML back to the browser.

At the end of the day, all the browser is doing is (1) sending HTTP requests
to the server, and (2) receiving HTML. That's basically it. IF there is any
client-side programming going on, it will usually be client-side JavaScript.
Even when it runs, there is no live/ongoing connection with the Web server
and/or ASP.NET Web application.

This link explains it better than I:
http://aspnet.4guysfromrolla.com/articles/011404-1.aspx


Now, about your SQL Server problems.... sorry , I don't know. You might want
to post a new question to specifically address that.

-HTH




<pamelafluente@xxxxxxxxx> wrote in message
news:1134844139.090291.148580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Dear Jeff,
>
> thank you very much for the enlighting clarification.
>
> Probably these things may seems trivial to experienced web programmers,
> but when has only done win apps, they are not at all. So the most basic
> schema you are suggesting is Browser--> Server <--> MywebApp -->
> Browser, right?
>
> Actually, I have just begun playing with the VWD. I have got through a
> few lessons of the www.asp.net tutorial, which are really nice.
>
> I already have found my first problem. In fact I found no way to make
> SQLServer2005 work. It's like the service is not seen by the
> applications (I did run the script the create the PUBS db and it worked
> fine).
> Don't know if the people at Microsoft expect the poor thing starting
> its journey in this new world with the "Express" tools be also a
> SQLServer expert. I have tried to reinstall it 2 times and at last gave
> up.
>
> Reinstalled the old SQLServer2000 Prof. which works like a charm.
>
> I am probably missing something very basic. But the point now is that
> would not like to waste
> a couple of days to find what it is. I prefer to focus on the ASP net
> for now.
>
> But if anyone know what the problem is (I am sure I am missing
> something very elementary) please let me know!
>
> -Pam
>


.



Relevant Pages

  • Re: BASIC authentication Issues with IE - Part II - Solved but WHY?
    ... We have complete control of the Request and Response ... it is up to the browser to send the credentials. ... ASP runs internally on the server. ...
    (microsoft.public.inetserver.iis.security)
  • Re: client gets always every first time for every page a 401
    ... only the first request get 401. ... Why does my Browser in case 5 not submit the Basic Authorization String ... credentials as used in 3, because they have the same root. ... Explorer has established a connection with the server by using Basic or NTLM ...
    (microsoft.public.inetserver.iis.security)
  • Re: How to write something to a html textfield and send it?
    ... > No need for controlling any particular browser. ... I'm not familiar with HTTP user ... and building the request in your program. ... The server doesn't know anything about a textfield; ...
    (comp.programming)
  • Re: client gets always every first time for every page a 401
    ... When the browser makes a request, ... If the server does not accept Anonymous or if the Anonymous ... then the browser must support this method to communicate with the ...
    (microsoft.public.inetserver.iis.security)
  • [Full-Disclosure] Web Application DoS
    ... request for a specific web site on the server. ... Of course the result set will be limited in good search applications. ... set is very big and therefore the answer from the http daemon will also ...
    (Full-Disclosure)