Tricky Exception Message while Remoting...

re: Tricky Exception Message while Remoting...

William — Mon, 27 Sep 2004 18:04:00 GMT

Thanks for the tip Beth - much appreciated

re: Tricky Exception Message while Remoting...

William — Mon, 27 Sep 2004 17:26:00 GMT

FYI.. you can also just flip the formatter to SOAP in the server and client config files and the real message will come through.

Client:
<channels>
<channel ref="http" useDefaultCredentials="true" port="0">
<clientProviders>
<formatter ref="soap" />
</clientProviders>
</channel>
</channels>

Server:
<channels>
<channel ref="http">
<serverProviders>
<formatter ref="soap" />
</serverProviders>
</channel>
</channels>

re: Tricky Exception Message while Remoting...

William — Mon, 27 Sep 2004 10:18:00 GMT

Fortunatelly for us there are only four main areas in ado.net that we are worried about when it comes to cross version serialization. The DataSet/datatable (huge, I am so glad I don't own this!) the SqlTypes (also not on my plate), managed provider exceptions and managed provider code access permissions. Exceptions are currently broken and I don't think anybody cares about code access security...

I must have missed the blog on session state datareaders *shudders* that must have been interesting. At least you can't serialize datareaders

re: Tricky Exception Message while Remoting...

William — Mon, 27 Sep 2004 03:10:00 GMT

Hi Angel:

You know, that's a really interesting point that I didn't even consider - it would be pretty darned important that my remotable object in v.X can be consumed by v.Xa for instance. Ingo Rammer is pretty much the man from what I've come across and his book on Advanced .NET REmoting (http://www.apress.com/book/bookDisplay.html?bID=47) is the best resource I've found. Similarly, Matthew MacDonald has a pretty good discussion in his enterprise development book but Ingo's is dedicated to Remoting and totally a must have. ALso, Paul Kimmel who is another dude I pretty much respect the heck out of has a really good discussion in his Visual Basic .NET for Advanced developers book. If you head over to www.thinktecture.com (Ingo's company) he's got some pretty good stuff. The only reason I found the problem was from his site which gave me the info I needed to track it down. The thing that makes this one tricky is that IT'S not a serialization problem but it says it is. And it's not a bug in the framework - it's based on what comes back from the remote machine however it's really misleading in that you're naturally inclined to hunt down something with formatting when in fact it's something else making itself look like its a formatting problem.

This is definitely something that's got my interest up - when I have time tomorrow I'll give it a try. I don't know how far you've gone with it so far, but Remoting ADO.NET objects is particularly interesting b/c in many cases, you just create an interface and use it to grab the remote object. But with a typed dataset for instance, creating an interface for it would be too much of a pain in many cases. But you can return it as a regular dataset and then just set the tablemappings/columnmappings to a locally created typed dataset and use it from there.

When I have some time I might try to use the 1.1 framework to pass a SqlDataReader remotely and access the connection from 5 different threads and see what happens just for giggles. WHat the heck, if Caustic Phil worked with a dude that advocated storing datareaders in session state, why can't I remote one <Hopefully no one will actually take this last nonsensical paragraph seriously).

I'll drop you a line tomorrow evening when I get home b/c this is a pretty interesting thing to look into

re: Tricky Exception Message while Remoting...

William — Mon, 27 Sep 2004 01:32:00 GMT

Bill,
I have just started working with cross version serialization (trying to make sure our ado.net serializable objects can serialize across frameworks) and I hate it <grin> I am glad to hear that getting this right is somewhat important.

Any good resources on Remoting you can point me to?