J
JJ
[I'm fairly new to asp.net]
I want to create a web site with the page content being driven by my sql
database. This would form the basis of a simple content management system.
i.e. a particular page may be accessed by the url
www.xyz.com/default.aspx?pageid=34
I can achieve this when each page is identical - e.g. contains my custom
text/html control.
The bit I am having problems with is:
How do I deal with adding my other custom controls to one page and not
another.
The one way I could come up with (which doesn't seem very efficient) is to
have some sort of logic built into the default page for each and every
control I write:
i.e. If (database says this page contains xyz control)
Then
(programmatically add control to page in location specifiied, in this order)
- there must be a more logical and efficient way than this. And I'm not
entirely sure how I'd deal with the physical location of the control on the
page.
[I did think about going down the web parts route, (my personalization
provider does take into account the querystring and treats it as a seperate
page) but:
a) I don't really want a user to customise the pages individually.
b) I also though one approach was to use a custom text/html editor in the
web part (when in edit mode) to allow the user 'personalization' of the
text, but I want to keep the page content data in my own tables in the
database and not in the webparts/personalization tables.
If I could get the web part to store the text peronalization information in
my tables, then I guess I could stop a standard user being able to
personalize the site....?]
I'd really appreciate any comments/help anyone can give,
JJ
I want to create a web site with the page content being driven by my sql
database. This would form the basis of a simple content management system.
i.e. a particular page may be accessed by the url
www.xyz.com/default.aspx?pageid=34
I can achieve this when each page is identical - e.g. contains my custom
text/html control.
The bit I am having problems with is:
How do I deal with adding my other custom controls to one page and not
another.
The one way I could come up with (which doesn't seem very efficient) is to
have some sort of logic built into the default page for each and every
control I write:
i.e. If (database says this page contains xyz control)
Then
(programmatically add control to page in location specifiied, in this order)
- there must be a more logical and efficient way than this. And I'm not
entirely sure how I'd deal with the physical location of the control on the
page.
[I did think about going down the web parts route, (my personalization
provider does take into account the querystring and treats it as a seperate
page) but:
a) I don't really want a user to customise the pages individually.
b) I also though one approach was to use a custom text/html editor in the
web part (when in edit mode) to allow the user 'personalization' of the
text, but I want to keep the page content data in my own tables in the
database and not in the webparts/personalization tables.
If I could get the web part to store the text peronalization information in
my tables, then I guess I could stop a standard user being able to
personalize the site....?]
I'd really appreciate any comments/help anyone can give,
JJ