• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 432
  • Last Modified:

login page not picking up theme

I have a login page which is not picking up the theme. The theme gets applied only after I login.

Since I know the URL of the css file, when I try to access it by typing its URL, the app takes me to the login page.

What's going on here?

The page directive of login.aspx is as follows:

<%@ Page MasterPageFile="~/SiteTemplate.master" Language="C#"  AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="Login" StylesheetTheme="MyTheme" Theme="MyTheme" Title="Login" %>
0
IUAATech
Asked:
IUAATech
  • 7
  • 5
1 Solution
 
Bob LearnedCommented:
What does the .skin file look like?

Bob
0
 
IUAATechAuthor Commented:
nothing much in there. I just have the following:

<asp:Button runat="server" BackColor=#FFFBD6 BorderColor="#CC9966" BorderStyle="Solid"
BorderWidth="1px" Font-Names="Arial" Font-Size="1.0em" ForeColor="#990000" />
0
 
Bob LearnedCommented:
Did you modify web.config to force the user to login.aspx?

Bob
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
IUAATechAuthor Commented:
yes.

Here is part of my web.config file

     <connectionStrings>
          <add name="ADConnectionString" connectionString="LDAP://myserver/DC=ads,DC=server,DC=com"/>
     </connectionStrings>
          <authentication mode="Forms">
               <forms name=".ADAuthCookie" timeout="10"/>
          </authentication>
          <authorization>
               <deny users="?"/>
               <allow users="*"/>
          </authorization>
          <membership defaultProvider="MyADMembershipProvider">
               <providers>
                    <add name="MyADMembershipProvider" type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, &#xA;             Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="ADConnectionString"/>
               </providers>
0
 
Bob LearnedCommented:
Then, you can't navigate to any other page but login.aspx.

Bob
0
 
IUAATechAuthor Commented:
That I understand.

But shouldn't css files be excluded from this rule? It seems stupid that you have to exclude the .css/.theme files using the web.config file.

Don't know what I am doing wrong.......
0
 
IUAATechAuthor Commented:
Bob,
this is exactly what I am encountering:

http://www.eggheadcafe.com/aspnet_answers/NETFrameworkASPNETsecurity/Jan2006/post25809353.asp

and currently I am also running the app using VS.NET's builtin Webserver. I will try running this in IIS and see if the problem goes away.

Raj
0
 
IUAATechAuthor Commented:
yep. running the project on IIS fixes this problem.
0
 
Bob LearnedCommented:
Hmmm, so Cassini has a problem with themes?

Bob
0
 
IUAATechAuthor Commented:
cassini?
0
 
Bob LearnedCommented:
.NET 2005 uses Cassini instead of IIS as the development web server.

Bob
0
 
IUAATechAuthor Commented:
ah ok.
0
 
RomModCommented:
Question closed - 200 points refunded.

Best regards,
RomMod
Experts Exchange
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now