MasterPages issue

[Sean]

We have a Master page problem that comes around time and time at work and
it’s a problem that has been confirmed by other developers on the project I
have been on. Additionally I have had the exact problems happen on my
personal project at home. Myself and the team I have been on are pretty
experienced with master pages and themes however now it is time for us to get
a deeper understanding then we have been able to find in books currently on
the market so we can be more prepared the next time we encounter this problem.

OK enough of that now the issue.
If you set up your masterpage with plenty of nice content and then as your
application grows and you have a good amount of content pages then make some
large changes to your masterpage content (ie table structures maybe change
some graphics etc) you not only run the chance of some very bizarre behavior
which seems like caching issues only if you close VS 2005 and even reboot
your machine and delete all temporary internet files it still has these
bizarre problems.
Problems can be things like rendering old content despite the new changes
and sometimes even rendering graphics that no longer exist! Other problems
can include not being able to access your content pages at all until you
remove all content from the masterpage and re-build it and when I say
re-build it I mean you CANT cut content and then paste it back in you have to
literally re-type the content back in (ie tables etc )
Now what we DON’T do is have content in the content placeholder of the
master page and then set the masterpage itself as the starting object of the
project which is an example I have seen. The example I saw basically
structured the main page as the default content of the masterpage and perhaps
that is our problem?
We are currently not having any issues but a few weeks ago I made a change
to my menu layout on my masterpage and ended up spending most of the day
rebuilding the entire masterpage content.
Thanks!

[Peter Bromberg [C# MVP]]

Sean,
from what you describe, this "sounds" like assemblies from a previous build
hanging around and being used. Try deleting the contents of the Temporary
ASP.NET files folder and doing a new build. I am not sure if the "Clean"
option on the build menu does this, but you could experiment with that too.
--Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com

[Sean]

Thanks I printed this and am going to file it for future reference because
currently we dont have a problem and not really wanting to try and create a
problem.

Its an issue that we are always aware so we wont forget we put this in file.