You searched for the word(s): userid:651178

More Search Options

RSS Available

• Re: The name 'Profile' does not exist in the current context

  haha, yeah, my response hasn't posted yet but I just saw your response. I basicly did the same thing, as you should see in the code. My major issue was I didn't know enough about the Profile object, how and when it was getting generated. But, I have it under control now. Thank you very much for your time in this. It was starting to drive me mad, lol.

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• Re: The name 'Profile' does not exist in the current context

  http://www.odetocode.com/Articles/440.aspx The above site answers ALL the questions I had in regards to Profiles. In fact it is a very handy article if you ever intend on using Profiles I suggest you read it. The solution to my issue basicly looks like this: using System; using System.Web; using System.Web.UI; /// <summary> /// Summary description for ManagePage /// </summary> public class ManagePage : Page { public ManagePage() { PreInit += new EventHandler(ManagePage_PreInit); } void

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• Re: The name 'Profile' does not exist in the current context

  It's nearly the same as membership. What I've discovered, however, is you can't access it from a custom base class. It has to be used on the actuall aspx page. It all has to do with when the user gets athunticated (I'm using integrated auth). If the user hasn't been athunticated it can't find the Profile for that user yet. I tried a work around, all be it a little odd, but I didn't like the results. You can create an new aspx page remove all the code from the .aspx except for the necessary header

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• Re: ContentPlaceHolders and CSS layout settings

  Here's an example of a Master Page doing something similar: < div id= "mainbody" > < div id= "localtools" > < asp:contentplaceholder id= "localtool" runat= "server" ></ asp:contentplaceholder > </ div > < div id= "extras" > < asp:contentplaceholder id= "extra" runat= "server" ></ asp:contentplaceholder > </ div > < div id= "content" > < asp:contentplaceholder id= "contents" runat= "server" ></ asp:contentplaceholder > </ div

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• Re: The name 'Profile' does not exist in the current context

  I did explictly state it, and it's no longer out of context. However, I can not access the custom varaibles associated with the current profile. It's like the actually profile object isn't being built yet.

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• Re: The name 'Profile' does not exist in the current context

  http://msdn2.microsoft.com/en-us/library/2y3fs9xs(VS.80).aspx this is what I'm refering to. which I believe is HttpContext.Profile

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• Re: The name 'Profile' does not exist in the current context

  I believe so, yes. Should I explictly sate it as such?

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/31/2006

• The name 'Profile' does not exist in the current context

  Basicly, I'm trying to create a custom base page and inherit it to all of my aspx pages. I'm getting the above error: The name 'Profile' does not exist in the current context The custom base page looks like this: using System; using System.Data; using System.Configuration; using System.Web; using System.Web.Security; using System.Web.Profile; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.IO; using System

  Posted to Master Pages, Themes and Navigation Controls (Forum) by triadfate on 3/30/2006