bizzydint Posted July 18, 2003 Posted July 18, 2003 My site (set up by someone else) is made up of a bunch of asPx pages, each containing controls specified in asCx files. Now i'm guessing the "C" means there's code involved???? unless someone wants to enlighten me? :) It's annoying me that the asPx files are essentially just templates which tell the page which Title control, footer control and main control to use. So i want to get rid of the asPx files, and make the ascx files contain a link to the Title and footer controls and the actual content of the main control (am i making sense??) I'm pretty sure it's possible, so i really just want to know if it's a particularly inefficient/frowned upon way of doing things.... cheers m'dears, van Quote Grant me the serenity to accept the things I cannot change, the courage to change the things I cannot accept and the wisdom to hide the bodies of those people I had to kill today cos they pi**ed me off.
wyrd Posted July 18, 2003 Posted July 18, 2003 ASCX means it's a control. ASPX means it's an ASP.NET page. Quote Gamer extraordinaire. Programmer wannabe.
bizzydint Posted July 18, 2003 Author Posted July 18, 2003 but is there any *actual* difference? can i make the changes i want to?? Quote Grant me the serenity to accept the things I cannot change, the courage to change the things I cannot accept and the wisdom to hide the bodies of those people I had to kill today cos they pi**ed me off.
Administrators PlausiblyDamp Posted July 18, 2003 Administrators Posted July 18, 2003 ASCX files are designed to be placed within ASPX pages, they are missing several vital HTML tags (, , , ) and as such cannot be rendered by browsers. Using them is a form of code / UI reuse and quite a good practice. Is there any particular reason why you desire to change how things are currently being done? Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
bizzydint Posted July 21, 2003 Author Posted July 21, 2003 The reason is..... We currently have a "skin" feature on our site - its meant for teenagers, who are notoriously picky! The way it works atm is that for *each* skin we have a set of ASPX files and just one universal set of ASCX files containing the core controls which get reused for each skin. Now you can imagine that this is a pain to update (although we rarely need to change the aspx files) and really these files dont have any vital info in them, so i wanted to do away with them. But it seems that they are required. So I'll probably have to work out a way of having *one* set of ASPX which knows which skin style sheet, title bar and footer it's meant to use....must be possible ;) Thanks for helping - you've just confirmed what i already thought! Quote Grant me the serenity to accept the things I cannot change, the courage to change the things I cannot accept and the wisdom to hide the bodies of those people I had to kill today cos they pi**ed me off.
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.