The MyAccount.aspx page is throwing the error 'Specified cast is not valid' for the line:

Dim currentUser As New AccBusiness.User( _
                      CType(Context.User, SitePrincipal))

Any thoughts on why this might be?
Id really appreaciate any help on this one, thanks.

I had the same problem. It worked when I first started using the site.

I fixed it by adding the MyAccount.aspx and MyAccount.aspx.vb from the original download into the project overwriting the existing files. Re-booted my computer and re-built the solution. Works fine now.

Scratch that! Problem started again.

I'm getting the same error when I try to cast the context.user.identity object to a SiteIdentity object in the siteheader.ascx user control. The line that causes the issue is

Dim id As SiteIdentity = CType(Context.User.Identity(), SiteIdentity)

Below is the stack trace. If anyone knows how to resolve this a solution would be greatly appreciated. In the mean time I'll keep banging my head on the keyboard.

[InvalidCastException: Specified cast is not valid.]
   home.Opydcom.Web.Controls.User.SiteHeader.Page_Loa d(Object sender, EventArgs e) in C:\Inetpub\web\opyd\wwwroot2\html\home\Controls\Us er\SiteHeader.ascx.vb:57
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Control.LoadRecursive() +98
   System.Web.UI.Control.LoadRecursive() +98
   System.Web.UI.Page.ProcessRequestMain() +725

Check out this thread, I'm sure that is what is happening to you.

I've email wrox and the authors to try and fix this error. They either don't know how to fix this or just don't care.

http://p2p.wrox.com/topic.asp?TOPIC_ID=1361

I tried the fix with the initialize sub and althought my code did seem to be altered changing back to the orignial code did not correct the invalid cast error.

I have found a work around to the problem I was having. I have posted an updated page_load sub below. Changes from the original are in BOLD. Note that I have added a couple of trace.write statements for debug purposes to check the object type of my Context.user object. The two trace.write lines can be omitted with no ill effects.


 Private Sub Page_Load(ByVal sender As Object, _
          ByVal e As EventArgs) Handles MyBase.Load

            Greeting.Text = "Welcome, "
           Dim id As SiteIdentity
            If Context.User.Identity.IsAuthenticated Then

                Trace.Write("is SitePrincipal:" & (TypeOf context.User Is SitePrincipal).ToString)
                Trace.Write("User is Authenticated: " & Context.User.Identity.IsAuthenticated.ToString)

               If Not (TypeOf context.User Is SitePrincipal) Then
                    id = New SiteIdentity(Context.User.Identity.Name)
                End If
                Greeting.Text = Greeting.Text & "<b>" & id.name & "</b>"
                UserLink.Text = "My Account"
                UserLink.NavigateUrl = _
                "/home/WebModules/Accounts/MyAccount.aspx"
                SignOut.Visible = True

            Else

                Greeting.Text = Greeting.Text & "Guest User."
                UserLink.Text = "Click to Login"
                UserLink.NavigateUrl = "/home/WebModules/Accounts/Login.aspx"
                SignOut.Visible = False

            End If

        End Sub

You need to make your pages inherit the general page class. Make sure your MyAccount.apsx.vb code page has:

The code was regenerated when any control is added/removed on the ASPX to:

    Private Sub InitializeComponent()
    End Sub
    Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

THEREFORE, the PhilePage.PhilePage_Load was not run. We should just changed them back like:
    Private Sub InitializeComponent()
      AddHandler Me.Load, AddressOf Page_Load
    End Sub
   Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

I DON'T known if we can disable this code regeneration option!

I find I only get this error if I log out of my current principal and try to visit the account page without being logged in you know by just going to the page directly. Its as if the page needs a "You need to be logged in to view the "My Account" page.