Reply

skagen00 Posted: Mon, Aug 14 2006 8:24 AM

rated by 0 users

I'm sure this is a no-brainer to some of you but I'm not exactly sure where to look and I'm just trying to get past this item quickly.

When I fire up the project from within Visual Studio, the URL is:

http://localhost:4268/<myproduct>/Login.aspx

The error I get is:

Server Error in '/<myproduct>' Application.

---

Type is not resolved for member 'MyCompany.CoreSystem.Library.ProPrincipal,MyCompany.CoreSystem.Library,

Now, if I omit the :4268, I can run it just fine. But I can't seem to hit my breakpoints in the debugger, which is a real problem.

Would anyone have a suggestion for me, please?

Reply

Chris Dearing replied on Mon, Aug 14 2006 9:13 AM

rated by 0 users

<Now, if I omit the :4268, I can run it just fine>

Your web server must be set up to listen on port 4268 instead of port 80.

< But I can't seem to hit my breakpoints in the debugger, which is a real problem>

You will not be able to debug server side code. Try testing locally first.

Reply

Andy replied on Mon, Aug 14 2006 9:24 AM

rated by 0 users

Misled:

You will not be able to debug server side code. Try testing locally first.

Reply

skagen00 replied on Mon, Aug 14 2006 9:30 AM

rated by 0 users

The thing is, I'm not doing remoting yet... that's why I'm a little confused about the serialization error.

And thanks, Misled, though I'm not entirely sure where to configure this. I see in IIS admin there is a TCP port and HTTPS port 80 and 443 respectively... Could you give me a pointer as to where to look at this?

Reply

skagen00 replied on Mon, Aug 14 2006 9:59 AM

rated by 0 users

My stack trace is (if it helps):

[SerializationException: Type is not resolved for member 'MyCompany.CoreSystem.Library.ProPrincipal,MyCompany.CoreSystem.Library, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.]
   Microsoft.VisualStudio.WebHost.Connection.get_LocalIP() +0
   Microsoft.VisualStudio.WebHost.Request.GetLocalAddress() +58
   Microsoft.VisualStudio.WebHost.Request.GetServerName() +27
   System.Web.HttpRequest.get_Url() +168
   System.Web.UI.WebControls.Menu.OnPreRender(EventArgs e, Boolean registerScript) +1389
   System.Web.UI.WebControls.Menu.OnPreRender(EventArgs e) +49
   System.Web.UI.Control.PreRenderRecursiveInternal() +148
   System.Web.UI.Control.PreRenderRecursiveInternal() +233
   System.Web.UI.Control.PreRenderRecursiveInternal() +233
   System.Web.UI.Control.PreRenderRecursiveInternal() +233
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4436

Reply

skagen00 replied on Mon, Aug 14 2006 10:18 AM

rated by 0 users

Thanks for taking the time to answer, Andy.

Rocky has a post on this in his blog...

http://www.lhotka.net/WeBlog/CommentView,guid,cfcaf6c4-63cf-4cf1-8361-ed3db07496a4.aspx

I tried to implement ISerializable on my custom Identity but that didn't alone do the trick. I'm going to try to implement it on my custom Principal (as it looks like one person needed to do this.) I sure hope it solves the problem - not having the debugger is a pain.

So it sounds like it's not likely a matter of changing the listening port and it has to do with this Cassini crap. :)

Reply

skagen00 replied on Mon, Aug 14 2006 10:31 AM

rated by 0 users

Thank goodness. OK, the solution posted in the blog works in terms of making both the custom identity and principal serializable (thus far, at least - I'm not sure what to instantiate in terms of GenericPrincipal as I don't know how to get a list of the roles for my custom principal, but I haven't built in really any authorization yet so I'll worry about that later).

I was pretty excited to hit my breakpoint :).

Thanks!

Chris

Reply

skagen00 replied on Mon, Aug 14 2006 1:27 PM

rated by 0 users

So I just read Xal's message, and changed the base url of the custom server to be the virtual folder in my IIS - disabled the ISerializable interface implementation (as suggested in a reply to Rocky's blog), and everything works swell.

Thanks Xal.

Reply

sydneyos replied on Thu, Sep 14 2006 9:47 AM

rated by 0 users

For those of us who are still having this problem, could you say more about the solution?  I don't know what you mean by "changed the base url of the custom server..." or disabling the ISerializable interface.  Do you mean that you had made your custom principal inherit from ISerializable before and then removed that? 

Right now, my custom principal just has the [Serializable] attribute.  I assume I should keep that . . .

Thanks

Reply

skagen00 replied on Thu, Sep 14 2006 11:59 AM

rated by 0 users

Hiya -

Yes, I was talking just about the ISerializable interface implementation - I found I didn't need to do that. My principal and identity are still marked as [Serializable()] though, of course.

I'm not sure how much this is going to help you as I made a copy of my application so that I would freeze "what I had" for a demonstration, but I noticed I didn't need to do a thing in my new web application.

On my old one, if i go into the properties of the web site (from VS 2005) and go to the start options, and look in the Server section, I am not using the default web server - I am instead selecting use custom server, and then on my base url I have: http://localhost/<myapp>/ 

Let me know if you get that solution (or another to work). Thanks!