Hi Arnt,

Firstly, it wont be that Umbraco is too fast for your code.  Your user-control is part of the ASP.NET page life-cycle, so your code will be hit when it needs to be hit - its not going to be skipped over.

I'm curious what the code/logic is within the GetStylesheet() method.  My feeling is that however you are accessing the member/user data, its not consistent? (that's just a wild guess).  If you could provide more details on GetStylesheet() we might be able to help?

Thanks, Lee.

Im sure you are right, Lee.
Beeing over this method a lot's of times with my debugger running, but can't seem to find my "jiffy".
This seems to relay on my C# skills (doh), and it's NOT an Umbraco issue. And im not asking you guys to be my debugger, but do really appreciate the tips.

Here goes:

 
 
 
/// <summary>
 
 
/// Gets the style sheet from user startpage for supplied stylesheet key
 
 
/// </summary>
 
 
protected string GetStyleSheet(string styleSheet)
{
 
 
try
{
 
 
//Get user start page
IQWDT2011.Util.
 
CurrentUser currentUser = IQWDT2011.Util.CurrentSettings.GetCurrentUser();
 
 
//Get style sheet
 
 
return ResolveUrl(currentUser.GetStyleSheet(styleSheet));
}
 
 
catch
{
 
 
return "";
}
}

So, looking into GetCurrentUser();
Remeber my comments, we are usually using a SignUp Site that validates the user by 2-factor login, and ISA redirects the user to correct site if valid with CurrentUserInfo in Session. But for development we just hardcode user credentials in global.asax Application_Start. Heres the CurrentSettings class with GetCurrentUser() method

public static CurrentUser GetCurrentUser() 
{
if (HttpContext.Current.Session["CurrentUser"] != null && HttpContext.Current.Session["CurrentUser"] is CurrentUser)
{
return HttpContext.Current.Session["CurrentUser"] as CurrentUser; 
}
else
 { 
CurrentUser cu = new CurrentUser(); 
HttpContext.Current.Session["CurrentUser"] = cu; 
return cu;
}


 

Ok, we got a CurrentUser.
Let's go back to GetStyleSheet() and really bring out the sheets :)
Remeber the GetStyleSheet on top of this post. When having the CurrentUser, it vil do a

 ResolveUrl(currentUser.GetStyleSheet(styleSheet));
 Let's do a dive into that:

 //currentUSer.GetStyleSheet 
public string GetStyleSheet(string styleSheet) //styleSheet beeing f.ex "Webdesktop"
try
{
 
 
XmlNode myNode = UserStartNode; //UserStartNode returns an XmlNode based on CurrentUser's cred's and properties value.  
 
 
string strAlias = "styleSheet" + styleSheet;
 
 
if (myNode.SelectSingleNode(strAlias).InnerText != null && myNode.SelectSingleNode(strAlias).InnerText.ToString() != "")
 
 
return myNode.SelectSingleNode(strAlias).InnerText; //Should now give you the value /css/group8/group8.css - or whatever value that are in this alias/property  
 
 
else
 
 
return "";
}
 
 
catch { }
 
 
return "";
}
 

   
So, this maybe just made this post worse, and maybe the explanation of the code is far fetched, but uf you see anything really Home Simpson dumb code, please let me know.

Woopdi doo.
Seems as I can't format my code in this editor even.
Maybe have a break, and re-think my issues :)

Ok writing the code in this forum, make me realise that depending on:

public
 
 
 string GetStyleSheet(string styleSheet)
{
 
 
try
{
 
 
XmlNode myNode = UserStartNode;
 
 
string strAlias = "styleSheet" + styleSheet;
 
 
if (myNode.SelectSingleNode(strAlias).InnerText != null && myNode.SelectSingleNode(strAlias).InnerText.ToString() != "")
 
 
return myNode.SelectSingleNode(strAlias).InnerText;
 
 
else
 
 
return "";
}
 
 
catch { }
 
 
return "";
}

was a bit to hasty. I know se that this function thows a cath know and then.
cool, found the jiffy, I'll probably find out why pretty soon.

Hmmm, first of all.
Lee: sorry to waste your time.
I found my jiffy.
The GetStyleSheet() method ask for userStartNode and itself triggers an assembly that do some funny stuff towards the db and AD.
When getting the userStartNode, it will put it in the HttpContext.Cache. This Cache get's the expiration time from a web.config appsettings key. Guess what.
The key did'nt exist i the web.config. So the object faild, and faild and worked, and fail, and fail, and worked.

The devil truly lies in the details.

Thanks Lee for forcing me to actually use my 2 braincells :)
Thanks :)

is working on a reply...