C
Chris Kettenbach
Hi I am designing an ASP.net app. Just wanted some opinions on code behind
options. My idea is to have a code behind file that the controls will
reference and have ascx files for the controls. Then have the aspx pages
call the controls. Is this a good approach? I wanted to throw all my
business logic in to the code behind file and then on the aspx pages that
use the controls just refernce the ascx files. Is this the correct
approach? Should I bypass the ascx controls if they are not fancy customer
controls just like a datagrid? Also I connect to SQL back end in the app
and get different data for some of the datagrids that will be on the main
page? Is it better to put the ADO.net connection logic in to the ascx
files? or better to use the Code Behind? Thanks for any opinions.
Regards,
Chris
options. My idea is to have a code behind file that the controls will
reference and have ascx files for the controls. Then have the aspx pages
call the controls. Is this a good approach? I wanted to throw all my
business logic in to the code behind file and then on the aspx pages that
use the controls just refernce the ascx files. Is this the correct
approach? Should I bypass the ascx controls if they are not fancy customer
controls just like a datagrid? Also I connect to SQL back end in the app
and get different data for some of the datagrids that will be on the main
page? Is it better to put the ADO.net connection logic in to the ascx
files? or better to use the Code Behind? Thanks for any opinions.
Regards,
Chris