I will look into that, but I really have to use something that is available
and not in beta. What I'd like to do is still allow the graphics designer to
generate the pages and HTML, and just put "[skin]" in the HTML anywhere the
skin name has to be written out. For example:
## BEGIN CODE ##
<html>
<body>
<h1>Hello, world</h1>
<img src="/images/[skin]_logo.jpg">
</body>
</html>
## END CODE ##
It would be nice if in an some event in my base page class I could somehow
replace all instances of "[skin]" in the HTML with the skin name the user
has selected. I know if I set all of these tags to "runat=server" I could do
this, but then I also have to recompile everytime I add one, etc., and
changes will not be easily handled by someone that's not a developer.
Shawn
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:#m**************@TK2MSFTNGP14.phx.gbl...
For some reason none of the other replies to you can be read by me today
but I would encourage you to get started with ASP.NET 2.0 and learn about its
support for skins, themes and master pages.
--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
"Shawn Berg" <sh***@saeweb.com> wrote in message
news:uM****************@TK2MSFTNGP12.phx.gbl... A web site I am working on is built completely in classic ASP, and
allows the user to choose different "skins" for the site. The term "skin" being
used very generically. When a user selects a Skin it controls what
stylesheet is sent to their web browser, and also changes some images
that display.
For example, in a classic ASP page we may have the following:
## BEGIN CODE ##
<img src="/images/<%= UserSkin %>_logo.jpg">
## END CODE ##
What would be the best way to convert these pages to ASP.NET, and use an
OOP approach?
Any help would be appreciated.
Thanks.
