Hello Christophe,
Thank you for posting.
From your description, you've developed an ASP.NET 2.0 web site application
which uses a single master page and some global Theme resources(skin and
css style). This works well in development machine but failed on the
production server, correct?
According to your application's structure and scenario, I've performed som
tests in my local test environment(windows 2003 server , .net framework
2.0/vs 2005...), however, failed to reproduce the same behavior.
Generally, such issue is likely environment specific. And I've also checked
the method involved in the error callstack you mentioned:
PageTheme.SetStyleSheet()
It just simply check the container Page's "Header" property and the
"Header" property should have been correctly assigned for your scenario.
BTW, is the problem specific to MasterPage based pages? If you creating a
non-Master page based page (which applies some Theme and stylesheet), will
it also suffer the problem? In addition, you can try testing it on some
other server machine to see whether it occurs(confirm whether it is project
specific issue), if only on that parituclar production server, we may need
to concentrate on the ASP.NET environment on that machine.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
