Masterpages/themes woes

[Sean]

My experience now working with master pages on and off for 6 months is that
they can be very dangerous when working with themes.
One example in particular is the changes I made to my banner menu which now
work just fine with all my themes on my development machine but on my
production server my non-standard themes are showing effects that are no
longer in place even with a complete re-copy of my project.
Problems like this with masterpage/themes is so common for my project as
well as the project I have at work that when I need to make a change I make a
full backup.
So the question I guess is this. Is there some advanced feature I am missing
that will clear out the old themes settings that are hiding someplace that is
comepletly beyond my understanding? The only place I can think that these
things are being stored is in the IIS itself and yes I have deleted all my
temp files in my browser and even tried accessing the same pages from
different machines!
Today I had to basically totally rebuild my banner. It wouldn’t even accept
a cut and re-paste!

[clintonG]

An explicit answer depends on your implementation which you say nothing
about in detail which is typical.

Are you using a Theme or a StyleSheetTheme ? Skins? Separate stylesheets?
Where might those stylesheets be located? How are they being loaded? Do you
attempt to apply style inline?

I use MasterPages myself and IIS (of course) neither of which generally
speaking has any adverse impact on styling content. Granted, CSS can impact
the page layout but again, you say nothing specific about your
implementation. For me, the key to understanding 2.0 Themes and Skins has
been learning how Themes and Skins or the StyleSheetTheme supports the css
class inheritance model.

Finally, I'm a one man band and don't use source control (yet) and have a
time or two or three realized I was not in fact using the files I thought I
had deployed. It sounds like you've simply blundered in the same way.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee. com
URL http://www.metromilwaukee.com/clintongallagher/
"Sean" <Se**@discussio ns.microsoft.co mwrote in message
news:9D******** *************** ***********@mic rosoft.com...

>
My experience now working with master pages on and off for 6 months is
that
they can be very dangerous when working with themes.
One example in particular is the changes I made to my banner menu which
now
work just fine with all my themes on my development machine but on my
production server my non-standard themes are showing effects that are no
longer in place even with a complete re-copy of my project.
Problems like this with masterpage/themes is so common for my project as
well as the project I have at work that when I need to make a change I
make a
full backup.
So the question I guess is this. Is there some advanced feature I am
missing
that will clear out the old themes settings that are hiding someplace that
is
comepletly beyond my understanding? The only place I can think that these
things are being stored is in the IIS itself and yes I have deleted all my
temp files in my browser and even tried accessing the same pages from
different machines!
Today I had to basically totally rebuild my banner. It wouldn't even
accept
a cut and re-paste!

[Sean]

My implementation of themes is specific and exactly "by the book" for the new
..Net 2.0 feature and when I say "by the book" I mean EXACTLY as Micrsoft
iteself says to use it as well as the book "Proffesion al ASP.Net 2.0" which
also happens to be the exact way another developer was doing it independent
of myself and was experiencing the same problems

"clintonG" wrote:

An explicit answer depends on your implementation which you say nothing
about in detail which is typical.

Are you using a Theme or a StyleSheetTheme ? Skins? Separate stylesheets?
Where might those stylesheets be located? How are they being loaded? Do you
attempt to apply style inline?

I use MasterPages myself and IIS (of course) neither of which generally
speaking has any adverse impact on styling content. Granted, CSS can impact
the page layout but again, you say nothing specific about your
implementation. For me, the key to understanding 2.0 Themes and Skins has
been learning how Themes and Skins or the StyleSheetTheme supports the css
class inheritance model.

Finally, I'm a one man band and don't use source control (yet) and have a
time or two or three realized I was not in fact using the files I thought I
had deployed. It sounds like you've simply blundered in the same way.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee. com
URL http://www.metromilwaukee.com/clintongallagher/
"Sean" <Se**@discussio ns.microsoft.co mwrote in message
news:9D******** *************** ***********@mic rosoft.com...

My experience now working with master pages on and off for 6 months is
that
they can be very dangerous when working with themes.
One example in particular is the changes I made to my banner menu which
now
work just fine with all my themes on my development machine but on my
production server my non-standard themes are showing effects that are no
longer in place even with a complete re-copy of my project.
Problems like this with masterpage/themes is so common for my project as
well as the project I have at work that when I need to make a change I
make a
full backup.
So the question I guess is this. Is there some advanced feature I am
missing
that will clear out the old themes settings that are hiding someplace that
is
comepletly beyond my understanding? The only place I can think that these
things are being stored is in the IIS itself and yes I have deleted all my
temp files in my browser and even tried accessing the same pages from
different machines!
Today I had to basically totally rebuild my banner. It wouldn't even
accept
a cut and re-paste!

[Sean]

ADDED:

I am using both skins and sytlesheets located in the theme directory with
its proper name. Images are dictated by sytlesheets in the themes while
server controls are dictated by skins.

What is troubling is that for for some themes I get a rendering of a div
layout that doesnt exist on my master page and I know this for a fact becuase
I had to rebuild it twice.

"clintonG" wrote:

An explicit answer depends on your implementation which you say nothing
about in detail which is typical.

Are you using a Theme or a StyleSheetTheme ? Skins? Separate stylesheets?
Where might those stylesheets be located? How are they being loaded? Do you
attempt to apply style inline?

I use MasterPages myself and IIS (of course) neither of which generally
speaking has any adverse impact on styling content. Granted, CSS can impact
the page layout but again, you say nothing specific about your
implementation. For me, the key to understanding 2.0 Themes and Skins has
been learning how Themes and Skins or the StyleSheetTheme supports the css
class inheritance model.

Finally, I'm a one man band and don't use source control (yet) and have a
time or two or three realized I was not in fact using the files I thought I
had deployed. It sounds like you've simply blundered in the same way.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee. com
URL http://www.metromilwaukee.com/clintongallagher/
"Sean" <Se**@discussio ns.microsoft.co mwrote in message
news:9D******** *************** ***********@mic rosoft.com...

My experience now working with master pages on and off for 6 months is
that
they can be very dangerous when working with themes.
One example in particular is the changes I made to my banner menu which
now
work just fine with all my themes on my development machine but on my
production server my non-standard themes are showing effects that are no
longer in place even with a complete re-copy of my project.
Problems like this with masterpage/themes is so common for my project as
well as the project I have at work that when I need to make a change I
make a
full backup.
So the question I guess is this. Is there some advanced feature I am
missing
that will clear out the old themes settings that are hiding someplace that
is
comepletly beyond my understanding? The only place I can think that these
things are being stored is in the IIS itself and yes I have deleted all my
temp files in my browser and even tried accessing the same pages from
different machines!
Today I had to basically totally rebuild my banner. It wouldn't even
accept
a cut and re-paste!

[clintonG]

I had some problems coordinating myself and I recall I may have also had an
empty div at one time. Since css and skin files are more or less text files
that can have contents in any order once I alphabetized declarations I
started finding it easier to coordinate and rid myself of some redundant
declarations. This is all guesswork but perhaps that strategy may be
helpful. I also went through my HTML source and built start and end comment
blocks around the source. That has also brought unused controls to my
attention from time to time. I hope you work it out but you know as well as
I that if you've been at this for any length of time its always going to be
something ridiculously stoopit staring you right in the face all alond ;-)

<%= Clinton

"Sean" <Se**@discussio ns.microsoft.co mwrote in message
news:37******** *************** ***********@mic rosoft.com...

ADDED:

I am using both skins and sytlesheets located in the theme directory with
its proper name. Images are dictated by sytlesheets in the themes while
server controls are dictated by skins.

What is troubling is that for for some themes I get a rendering of a div
layout that doesnt exist on my master page and I know this for a fact
becuase
I had to rebuild it twice.

"clintonG" wrote:

>An explicit answer depends on your implementation which you say nothing
about in detail which is typical.

Are you using a Theme or a StyleSheetTheme ? Skins? Separate stylesheets?
Where might those stylesheets be located? How are they being loaded? Do
you
attempt to apply style inline?

I use MasterPages myself and IIS (of course) neither of which generally
speaking has any adverse impact on styling content. Granted, CSS can
impact
the page layout but again, you say nothing specific about your
implementation . For me, the key to understanding 2.0 Themes and Skins has
been learning how Themes and Skins or the StyleSheetTheme supports the
css
class inheritance model.

Finally, I'm a one man band and don't use source control (yet) and have a
time or two or three realized I was not in fact using the files I thought
I
had deployed. It sounds like you've simply blundered in the same way.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee. com
URL http://www.metromilwaukee.com/clintongallagher/
"Sean" <Se**@discussio ns.microsoft.co mwrote in message
news:9D******* *************** ************@mi crosoft.com...

>
My experience now working with master pages on and off for 6 months is
that
they can be very dangerous when working with themes.
One example in particular is the changes I made to my banner menu which
now
work just fine with all my themes on my development machine but on my
production server my non-standard themes are showing effects that are
no
longer in place even with a complete re-copy of my project.
Problems like this with masterpage/themes is so common for my project
as
well as the project I have at work that when I need to make a change I
make a
full backup.
So the question I guess is this. Is there some advanced feature I am
missing
that will clear out the old themes settings that are hiding someplace
that
is
comepletly beyond my understanding? The only place I can think that
these
things are being stored is in the IIS itself and yes I have deleted all
my
temp files in my browser and even tried accessing the same pages from
different machines!
Today I had to basically totally rebuild my banner. It wouldn't even
accept
a cut and re-paste!