J
Joe Hughes
Hi All
I'm a seasoned ASP programmer and have been writing ASP for years. I've
decided now to stop writing ASP and jump onboard the ASP.NET bandwagon
(albeit a bit late).
I've been programming in C# for a while but have only done some very
basic ASP.NET projects. The main hurdle I'm having trouble with is
finding a good method of laying out pages, I guess templates.
I've tried user controls, base page inheritance, dynamic controls,
dragging user controls on etc. But I still haven't decided on the best
way of doing things.
In traditional ASP I used Server.Execute/Transfer or the <!--Include-->
directive, typically with the commonly used Header/Footer layout.
So - What methods to people typically use to build their ASP.NET site
whilst reducing the page design overhead? I quite like the page
inhertiance method but I'd like to here other peoples' opinions. (I've
read about MasterPages briefly too)...
(Accidently posted this in the general CSharp group previously, sorry!)
I'm a seasoned ASP programmer and have been writing ASP for years. I've
decided now to stop writing ASP and jump onboard the ASP.NET bandwagon
(albeit a bit late).
I've been programming in C# for a while but have only done some very
basic ASP.NET projects. The main hurdle I'm having trouble with is
finding a good method of laying out pages, I guess templates.
I've tried user controls, base page inheritance, dynamic controls,
dragging user controls on etc. But I still haven't decided on the best
way of doing things.
In traditional ASP I used Server.Execute/Transfer or the <!--Include-->
directive, typically with the commonly used Header/Footer layout.
So - What methods to people typically use to build their ASP.NET site
whilst reducing the page design overhead? I quite like the page
inhertiance method but I'd like to here other peoples' opinions. (I've
read about MasterPages briefly too)...
(Accidently posted this in the general CSharp group previously, sorry!)