By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,657 Members | 862 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,657 IT Pros & Developers. It's quick & easy.

very weird display issue

P: n/a
Hi;

Ok, I will be the first to agree that this should be impossible - except we
are able to keep repeating it.

Our login page - which has moderately complex html and uses <LayoutTemplate>
to get the look we want - looks exactly right when running on IIS.

But when I run from VS 2005 using the integrated web server, it looks very
different - background color in a div is gone, it's in the upper left of the
page rather than centered, and more.

How can the display be different? Shouldn't it be the same html & css sent
to the browser? You can see the correct display at
http://beta.windward.net/portal if you are curious.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm
Nov 15 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Hello Dave,

From your description, your ASP.NET web appliation's login page display
incorrectly when running under VS 2005 test server while works well in
IIS(some UI elements such as images doesn't display ),correct?

Based on my experience, this could be caused by using forms authentication
in ASP.NET application that host in VS 2005/.NET 2.0 test server. Because
in the integrated testserver, all the requested no matter asp.net page or
static resource files like CSS, JPG are processed by ASP.NET runtime.
Therefore, if those static files are in directory which protecte from being
visited by unauthenticated user or require some certain role, it can not be
displayed. Does this fit your case? I assume some of the image display on
the login form is in a directory which will prevent unauthenticated user
according to your authorization setting. This won't be the case when it is
hosted in IIS because IIS will directly serve those static file's requests
instead of let ASP.NET handle them.

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 16 '06 #2

P: n/a
Bingo.

Ok in App_Themes\Windward\default.css I have:

body
{
background: url(Images/portal_logo_alum.jpg) repeat-x top right;
}

Where the jpg is in App_Themes\Windward\Images - what is the proper way to
point to theme images in the theme css file?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"Steven Cheng[MSFT]" wrote:
Hello Dave,

From your description, your ASP.NET web appliation's login page display
incorrectly when running under VS 2005 test server while works well in
IIS(some UI elements such as images doesn't display ),correct?

Based on my experience, this could be caused by using forms authentication
in ASP.NET application that host in VS 2005/.NET 2.0 test server. Because
in the integrated testserver, all the requested no matter asp.net page or
static resource files like CSS, JPG are processed by ASP.NET runtime.
Therefore, if those static files are in directory which protecte from being
visited by unauthenticated user or require some certain role, it can not be
displayed. Does this fit your case? I assume some of the image display on
the login form is in a directory which will prevent unauthenticated user
according to your authorization setting. This won't be the case when it is
hosted in IIS because IIS will directly serve those static file's requests
instead of let ASP.NET handle them.

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 16 '06 #3

P: n/a
It's a security issue - for the VS 2005 webserver I have to allow access to
unauthenticated users to App_Themes/Windward and App_Themes/Windward/Images.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"Steven Cheng[MSFT]" wrote:
Hello Dave,

From your description, your ASP.NET web appliation's login page display
incorrectly when running under VS 2005 test server while works well in
IIS(some UI elements such as images doesn't display ),correct?

Based on my experience, this could be caused by using forms authentication
in ASP.NET application that host in VS 2005/.NET 2.0 test server. Because
in the integrated testserver, all the requested no matter asp.net page or
static resource files like CSS, JPG are processed by ASP.NET runtime.
Therefore, if those static files are in directory which protecte from being
visited by unauthenticated user or require some certain role, it can not be
displayed. Does this fit your case? I assume some of the image display on
the login form is in a directory which will prevent unauthenticated user
according to your authorization setting. This won't be the case when it is
hosted in IIS because IIS will directly serve those static file's requests
instead of let ASP.NET handle them.

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 16 '06 #4

P: n/a
Thanks for your reply Dave,

Have you tried explicitly grant <allow user="*" /for the App_Themes
folder in your ASP.NET application through <locationelement in the
web.config (or put a separte web.config file in App_Themes folder to add
the authorization setting). Though it is not necessary for IIS hosted
scenario, it will help avoid the behavior I mentioned when in VS 2005 test
server hosting scenario.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '06 #5

P: n/a
yep - doing that now.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"Steven Cheng[MSFT]" wrote:
Thanks for your reply Dave,

Have you tried explicitly grant <allow user="*" /for the App_Themes
folder in your ASP.NET application through <locationelement in the
web.config (or put a separte web.config file in App_Themes folder to add
the authorization setting). Though it is not necessary for IIS hosted
scenario, it will help avoid the behavior I mentioned when in VS 2005 test
server hosting scenario.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.