Hi,

I'm presented with the task of making a quick mockup of an entire
ecommerce site (with user administration, shopping basket and
whatnot).

I've previously been involved in developing a number of sites of the
same size, and have gotten used to a certain way of doing things, ie.
a number of steps to complete the task. Those steps would probably be
something like:

1) Make visual/UI presentation
2) Define database structure
3) Code CRUD pages
4) Code more Business Logic like pages

etc.

This was back in the scripting days...

Now I'm moving to aspx, and was just wondering, if this still is the
way of going about it. I'm mostly concerned that I will have to
develop an entire DataAccessLayer, BusinessLogicLayer etc. instead of
what used to be the case, where the database pretty much pushed data
directly into the UI.

So, what are your 10 steps when developing an aspx site?

btw. I'm pretty comfortable with typed datasets, databinding etc. from
regular winforms.

/bjarne

//
I'm presented with the task of making a quick mockup of an entire
ecommerce site (with user administration, shopping basket and
whatnot).
//

I think this is the entire reason MS created the
http://quickstarts.asp.net/QuickStar...atasource.aspx
SqlDataSource.

2 tiered, hack it out quick code.

I personally don't have much use for them.

...

You can also look at "Starter Kits"
http://www.asp.net/downloads/starter....aspx?tabid=62

and get some UI design ideas.





"stormogulen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I'm presented with the task of making a quick mockup of an entire
> ecommerce site (with user administration, shopping basket and
> whatnot).
>
> I've previously been involved in developing a number of sites of the
> same size, and have gotten used to a certain way of doing things, ie.
> a number of steps to complete the task. Those steps would probably be
> something like:
>
> 1) Make visual/UI presentation
> 2) Define database structure
> 3) Code CRUD pages
> 4) Code more Business Logic like pages
>
> etc.
>
> This was back in the scripting days...
>
> Now I'm moving to aspx, and was just wondering, if this still is the
> way of going about it. I'm mostly concerned that I will have to
> develop an entire DataAccessLayer, BusinessLogicLayer etc. instead of
> what used to be the case, where the database pretty much pushed data
> directly into the UI.
>
> So, what are your 10 steps when developing an aspx site?
>
> btw. I'm pretty comfortable with typed datasets, databinding etc. from
> regular winforms.
>
> /bjarne
>

PS

microsoft.public.dotnet.framework.aspnet

would probably be a better group.

But please "Close Out" this thread before moving over to another group with
the same discussion please.


...





"sloan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> //
> I'm presented with the task of making a quick mockup of an entire
> ecommerce site (with user administration, shopping basket and
> whatnot).
> //
>
> I think this is the entire reason MS created the
>
http://quickstarts.asp.net/QuickStar...atasource.aspx
> SqlDataSource.
>
> 2 tiered, hack it out quick code.
>
> I personally don't have much use for them.
>
> ..
>
> You can also look at "Starter Kits"
> http://www.asp.net/downloads/starter....aspx?tabid=62
>
> and get some UI design ideas.
>
>
>
>
>
> "stormogulen" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > I'm presented with the task of making a quick mockup of an entire
> > ecommerce site (with user administration, shopping basket and
> > whatnot).
> >
> > I've previously been involved in developing a number of sites of the
> > same size, and have gotten used to a certain way of doing things, ie.
> > a number of steps to complete the task. Those steps would probably be
> > something like:
> >
> > 1) Make visual/UI presentation
> > 2) Define database structure
> > 3) Code CRUD pages
> > 4) Code more Business Logic like pages
> >
> > etc.
> >
> > This was back in the scripting days...
> >
> > Now I'm moving to aspx, and was just wondering, if this still is the
> > way of going about it. I'm mostly concerned that I will have to
> > develop an entire DataAccessLayer, BusinessLogicLayer etc. instead of
> > what used to be the case, where the database pretty much pushed data
> > directly into the UI.
> >
> > So, what are your 10 steps when developing an aspx site?
> >
> > btw. I'm pretty comfortable with typed datasets, databinding etc. from
> > regular winforms.
> >
> > /bjarne
> >
>
>

On Apr 26, 7:04 am, stormogulen <bjarn...@gmail.com> wrote:
> Hi,
>
> I'm presented with the task of making a quick mockup of an entire
> ecommerce site (with user administration, shopping basket and
> whatnot).
>
> I've previously been involved in developing a number of sites of the
> same size, and have gotten used to a certain way of doing things, ie.
> a number of steps to complete the task. Those steps would probably be
> something like:
>
> 1) Make visual/UI presentation
> 2) Define database structure
> 3) Code CRUD pages
> 4) Code more Business Logic like pages
>
> etc.
>
> This was back in the scripting days...
>
> Now I'm moving to aspx, and was just wondering, if this still is the
> way of going about it. I'm mostly concerned that I will have to
> develop an entire DataAccessLayer, BusinessLogicLayer etc. instead of
> what used to be the case, where the database pretty much pushed data
> directly into the UI.
>
> So, what are your 10 steps when developing an aspx site?
>
> btw. I'm pretty comfortable with typed datasets, databinding etc. from
> regular winforms.
>
> /bjarne

I would think you'd follow the same steps, although to me its odd a
mock up would actually have to talk to a database. At that point
you're basically implementing the application, aren't you?

stormogulen <(E-Mail Removed)> wrote:
> I'm presented with the task of making a quick mockup of an entire
> ecommerce site (with user administration, shopping basket and
> whatnot).

Do you have to mock it up in ASP.NET? If you're willing to spend a
little bit of time learning Groovy or Ruby, you may well find that you
can *very* quickly get the mock website going with Grails or Ruby on
Rails. Of course, it might then take longer to go to production (if
that would be in ASP.NET), but it depends what the purpose of the
exercise is.

--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Hi,

I would like to introduce you to a new technology called http://www.visualwebgui.com
which provides a unique way to create AJAX applications by providing
full WinForms like development including design time support. The
architecture eliminates most of AJAX soft spots by simply
returning back to server based computing but still having a dynamic
AJAX based UI. It also has been said by developers to boost
productivity to R.A.D. levels with out limiting your options.

Guy