Kevin I understood your post. Curt's response was more helpful and that
solved my problem than your reply.
I know asp.net is complex, but I am talking here about a simple page which
just has 2 words "hello world" its not using complex technology like COM
components, other framework calls, other stuffs like session, cookies,
session from asp to asp.net, viewstate etc...etc.....
I am an application developer who cares about my application....Microsoft is
there to take care of complex things for developers like me and I just need
to concentrate on my application....
My heading was pointed to experts acording to them its a simple issue.
anyway what ever you have said is true and I appriciate spending your time
for me.
cheers !
"Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
news:%23ZdPhQmoFHA.2904@TK2MSFTNGP14.phx.gbl...[color=blue]
> They were telling you what could be missing. I'll see if I can elaborate a
> little, but you've got a lot of work ahead of you.
>
> Your first mistake was in thinking that ANYTHING about ASP.Net is
> "simple." Your title says "asp.net simple question." Well, if it's so
> simple, why are you here? In your message you stated "I have a simple aspx
> page..." Again, there is nothing simple about ASP.Net. A console
> application that prints "hello world" to the screen is relatively simple.
> Everything happens in a nice little sandbox on your local machine. ASP.Net
> is an ISAPI (Internet Server Application Programming Interface) that
> resides on IIS, and handles HTTP requests over a TCP/IP network. So,
> you're already talking about something complex there. An ASP.Net
> application uses the Microsoft .Net Framework, which is multi-threaded,
> object-oriented, and network-oriented. So, add more complexity to the
> issue. Notice that I havent' even talked about an ASP.Net Page yet, much
> less one that prints "hello world" to an HTML document returned to a
> browser via an HTTP Request. HTTP is a stateless protocol, which
> complicates things MUCH further.
>
> To use ASP.Net, you first have to understand something about the
> environment in which it runs. Then you have to understand something about
> the platform it runs ON. Then you must understand something about the
> ASP.Net programming model, including the object-oriented aspects,
> maintaining state, and what a System.Web.UI.Control is, and how it
> behaves.
>
> Here's a good place to start:
>
http://msdn.microsoft.com/library/en...asp?frame=true
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> Expect the unaccepted.
>
> "abcd" <abcd@abcd.com> wrote in message
> news:ui7zwGdoFHA.3696@TK2MSFTNGP12.phx.gbl...[color=green]
>> its W2K with SP4 machine and it has IIS and .NET framework 1.1
>>
>> thanks
>>
>>
>>
>> Curt_C [MVP] wrote:[color=darkred]
>>> abcd wrote:
>>>> I am trying to set up client machine and investigatging which .net
>>>> components are missing to run aspx page.
>>>>
>>>> I have a simple aspx page which just has "hello world" printed....
>>>>
>>>> When I request that page like
http://machinename/dir1/hellp.aspx
>>>>
>>>> instead of running that page it starts downloding ...whats missing
>>>> here ...why the aspx engine not running the page....
>>>>
>>>> any clues
>>>>
>>>>
>>>>
>>>
>>> Or the .NET framework[/color]
>>
>>[/color]
>
>[/color]
