«

Hi,


Ok I was reading an old ASP 3.0 Book and I noticed that when designing web
applications. Everything that us windows form and vb programmers would do was
to put all functions relating to a certain area in one form. Like for example
I would have an employee timesheet that in a window form would do the
adding/updating/deleting etc. in one form. But from my reading of this ASP
book adding a timesheet would be put on one page, updating in another and
deleting in another. So my question to you guys is this the way I should be
design my apps in ASP.net? Should I brake out the different functionality
related to one particular task into different aspx pages? How do you guys
design your web apps?

Thanks,

JJ

These days we more often put related functionality into a single page.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net


"JJ" <> wrote in message
news:C48985AC-6341-47A8-9F40-...
> Hi,
>
>
> Ok I was reading an old ASP 3.0 Book and I noticed that when designing
> web
> applications. Everything that us windows form and vb programmers would do
> was
> to put all functions relating to a certain area in one form. Like for
> example
> I would have an employee timesheet that in a window form would do the
> adding/updating/deleting etc. in one form. But from my reading of this ASP
> book adding a timesheet would be put on one page, updating in another and
> deleting in another. So my question to you guys is this the way I should
> be
> design my apps in ASP.net? Should I brake out the different functionality
> related to one particular task into different aspx pages? How do you guys
> design your web apps?
>
> Thanks,
>
> JJ

Ok So you do like adding/updating/deleting of related functionality in one
page now. No Separation like in the good old days of ASP. Correct?

What do you do if the one page runs slow for someone that doesn't have a
cable connection to the internet. It's Satellite. Would you then create a
separate break out of pages for those individuals?

JJ

"Steve C. Orr [MVP, MCSD]" wrote:

> These days we more often put related functionality into a single page.
>
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://SteveOrr.net
>
>
> "JJ" <> wrote in message
> news:C48985AC-6341-47A8-9F40-...
> > Hi,
> >
> >
> > Ok I was reading an old ASP 3.0 Book and I noticed that when designing
> > web
> > applications. Everything that us windows form and vb programmers would do
> > was
> > to put all functions relating to a certain area in one form. Like for
> > example
> > I would have an employee timesheet that in a window form would do the
> > adding/updating/deleting etc. in one form. But from my reading of this ASP
> > book adding a timesheet would be put on one page, updating in another and
> > deleting in another. So my question to you guys is this the way I should
> > be
> > design my apps in ASP.net? Should I brake out the different functionality
> > related to one particular task into different aspx pages? How do you guys
> > design your web apps?
> >
> > Thanks,
> >
> > JJ
>
>
>

If the problem was that the page was too big, then maybe I would.
But there are other things that could be the problem, such as an
unnecessarily large ViewState or long running database queries.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net


"JJ" <> wrote in message
news:34D02B91-8DB1-4D9C-8192-...
> Ok So you do like adding/updating/deleting of related functionality in one
> page now. No Separation like in the good old days of ASP. Correct?
>
> What do you do if the one page runs slow for someone that doesn't have a
> cable connection to the internet. It's Satellite. Would you then create a
> separate break out of pages for those individuals?
>
> JJ
>
> "Steve C. Orr [MVP, MCSD]" wrote:
>
>> These days we more often put related functionality into a single page.
>>
>> --
>> I hope this helps,
>> Steve C. Orr, MCSD, MVP
>> http://SteveOrr.net
>>
>>
>> "JJ" <> wrote in message
>> news:C48985AC-6341-47A8-9F40-...
>> > Hi,
>> >
>> >
>> > Ok I was reading an old ASP 3.0 Book and I noticed that when designing
>> > web
>> > applications. Everything that us windows form and vb programmers would
>> > do
>> > was
>> > to put all functions relating to a certain area in one form. Like for
>> > example
>> > I would have an employee timesheet that in a window form would do the
>> > adding/updating/deleting etc. in one form. But from my reading of this
>> > ASP
>> > book adding a timesheet would be put on one page, updating in another
>> > and
>> > deleting in another. So my question to you guys is this the way I
>> > should
>> > be
>> > design my apps in ASP.net? Should I brake out the different
>> > functionality
>> > related to one particular task into different aspx pages? How do you
>> > guys
>> > design your web apps?
>> >
>> > Thanks,
>> >
>> > JJ
>>
>>
>>

Hi Steve,

I am developing an asp.net application using c# and asp.net 2.0 beta 2. I
started developing this page usign beta1. In beta 1 I have written some code
in Page_LoadComplete(object sender, EventArgs e) events of page. It was
working fine. But after I installed beta 2.0 Page_LoadComplete events is not
firing at all. Can u guide me how can I achieve this goal?

Thankx in advance.
Shailesh.

"Steve C. Orr [MVP, MCSD]" wrote:

> These days we more often put related functionality into a single page.
>
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://SteveOrr.net
>
>
> "JJ" <> wrote in message
> news:C48985AC-6341-47A8-9F40-...
> > Hi,
> >
> >
> > Ok I was reading an old ASP 3.0 Book and I noticed that when designing
> > web
> > applications. Everything that us windows form and vb programmers would do
> > was
> > to put all functions relating to a certain area in one form. Like for
> > example
> > I would have an employee timesheet that in a window form would do the
> > adding/updating/deleting etc. in one form. But from my reading of this ASP
> > book adding a timesheet would be put on one page, updating in another and
> > deleting in another. So my question to you guys is this the way I should
> > be
> > design my apps in ASP.net? Should I brake out the different functionality
> > related to one particular task into different aspx pages? How do you guys
> > design your web apps?
> >
> > Thanks,
> >
> > JJ
>
>
>