Re: Design flow for Code-behind
From: Jeff Davis (jeffscottdavis_at_hotmail.com)
Date: 03/01/05
- Next message: Nic: "Enable ASP.Net perfmon counters"
- Previous message: John Dalberg: "Re: Client validation not firing"
- In reply to: tshad: "Design flow for Code-behind"
- Next in thread: tshad: "Re: Design flow for Code-behind"
- Reply: tshad: "Re: Design flow for Code-behind"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Mar 2005 15:09:39 -0500
I have worked in situations where the designer created the UI first and then
passed the html on to the coder. This works ok, but can cause the coder to
wait on the designer.
I have also worked with a different system where we used controls that were
skinned. This approach requires a solid roadmap for each UI via written
requirements, but it allows the coder to create the code behind and the
controls while the designer works on the html that will be placed in the
skin control. The designer passes the html to the coder when it's complete
and the coder replaces the html control tags with the aspnet control tags in
the html when it gets put together. The custom control that loads up the
skin control simply uses the page.findcontrol("blah") function.
I don't think one is better than the other, but this is how I've dealt with
these challenges in the past.
HTH
-- Jeff Davis .NET Application Developer remove_jeffscottdavis@hotmail.com --------------------------------------------------------------- Life is 90% what happens to you and 10% how you react. "tshad" <tscheiderich@ftsolutions.com> wrote in message news:eY9ZM9oHFHA.2356@TK2MSFTNGP12.phx.gbl... > Many (if not most) have said that code-behind is best if working in > teams - which does seem logical. > > How do you deal with the flow of the work? > > I have someone who is good at designing, but know nothing about ASP. He > can build the design of the pages in HTML with tables, labels, textboxes > etc. > > But then I would need to change them to ASP.net objects and write the code > to make the page work (normally I do this as I go - can't do this if I > work in a team environment). > > Do you typically let the designer build the page first (aspx file) with > the html objects? Then later come along and change the ones you need to > asp objects and then build the code-behind page? > > At this point, I assume you would work with both files and the designer > can't be working with the aspx page while you are working with the > code-behind. As you change html objects to asp objects you would need to > work with both files to add the references to the object in the code > behind page. > > Also, how would the designer work with the design page while you are > making changes to the code-behind page as the page would probably fail > while you are making changes to the code-behind since the aspx file would > refer to it. > > Just trying to understand the logistics to this. > > Thanks, > > Tom >
- Next message: Nic: "Enable ASP.Net perfmon counters"
- Previous message: John Dalberg: "Re: Client validation not firing"
- In reply to: tshad: "Design flow for Code-behind"
- Next in thread: tshad: "Re: Design flow for Code-behind"
- Reply: tshad: "Re: Design flow for Code-behind"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
