471,319 Members | 1,931 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,319 software developers and data experts.

Getting an exception when trying to set up a callback in remoting

What does this exception message mean?

Type System.DelegateSerializationHolder and the types derived from it (such
as System.DelegateSerializationHolder) are not permitted to be deserialized
at this security level.

This is being done after a connection has been made to a remote object and
I'm trying to setup a callback to the client.

TIA - Jeff.
Jan 16 '06 #1
4 7848
Jeff,

Since .NET 1.1 there is more strict security demands when serializing in
remoting scenarios. Some time ago I gave advice on this topic. You can see
the thread here

http://groups.google.ca/group/micros...feb58462b45bb7
(look out for line breaks).

Read the thread there I give a code how to work this out.
--

Stoitcho Goutsev (100)

"WinDev" <Wi****@discussions.microsoft.com> wrote in message
news:78**********************************@microsof t.com...
What does this exception message mean?

Type System.DelegateSerializationHolder and the types derived from it
(such
as System.DelegateSerializationHolder) are not permitted to be
deserialized
at this security level.

This is being done after a connection has been made to a remote object and
I'm trying to setup a callback to the client.

TIA - Jeff.

Jan 16 '06 #2
Stoitcho,
Either I'm missing something or the code isn't complete. There are a couple
of things it's looking for that can't be found. There's a class called
SubscriberInfo that it can't find the constructor for with 3 elements. I
also had to create a reference to it.

Am I missing something or
"Stoitcho Goutsev (100)" wrote:
Jeff,

Since .NET 1.1 there is more strict security demands when serializing in
remoting scenarios. Some time ago I gave advice on this topic. You can see
the thread here

http://groups.google.ca/group/micros...feb58462b45bb7
(look out for line breaks).

Read the thread there I give a code how to work this out.
--

Stoitcho Goutsev (100)

"WinDev" <Wi****@discussions.microsoft.com> wrote in message
news:78**********************************@microsof t.com...
What does this exception message mean?

Type System.DelegateSerializationHolder and the types derived from it
(such
as System.DelegateSerializationHolder) are not permitted to be
deserialized
at this security level.

This is being done after a connection has been made to a remote object and
I'm trying to setup a callback to the client.

TIA - Jeff.


Jan 16 '06 #3
Jeff,

SubscriberInfo is a class form the original poster project
What you need is the info form my first message in the thread. I didn't want
to repost it, but here it is

"Since .NET v1.1 Microsoft demand more security restrictions on remoting
serialization. As a result in .NET v1.0 it is was possible to create a
channel as
ChannelServices.RegisterChannel(new TcpChannel(XXX));
However, with v1.1 we need to do more work to relax those restrictions and
make handling events possible.

On the server site you relax those restrictions as follows
BinaryClientFormatterSinkProvider clientProvider = null;
BinaryServerFormatterSinkProvider serverProvider =
new BinaryServerFormatterSinkProvider();
serverProvider.TypeFilterLevel =
System.Runtime.Serialization.Formatters.TypeFilter Level.Full;
IDictionary props = new Hashtable();
props["port"] = 4000;
props["typeFilterLevel"] = TypeFilterLevel.Full;
TcpChannel chan = new TcpChannel(props,clientProvider,serverProvider);
ChannelServices.RegisterChannel(chan);
On the client site
BinaryClientFormatterSinkProvider clientProvider = new
BinaryClientFormatterSinkProvider();
BinaryServerFormatterSinkProvider serverProvider = new
BinaryServerFormatterSinkProvider();
serverProvider.TypeFilterLevel =
System.Runtime.Serialization.Formatters.TypeFilter Level.Full;
IDictionary props = new Hashtable();
props["port"] = 0;
props["typeFilterLevel"] = TypeFilterLevel.Full;
TcpChannel chan = new TcpChannel(
props,clientProvider,serverProvider);
ChannelServices.RegisterChannel(chan); "


--

Stoitcho Goutsev (100)

"WinDev" <Wi****@discussions.microsoft.com> wrote in message
news:19**********************************@microsof t.com...
Stoitcho,
Either I'm missing something or the code isn't complete. There are a
couple
of things it's looking for that can't be found. There's a class called
SubscriberInfo that it can't find the constructor for with 3 elements. I
also had to create a reference to it.

Am I missing something or
"Stoitcho Goutsev (100)" wrote:
Jeff,

Since .NET 1.1 there is more strict security demands when serializing in
remoting scenarios. Some time ago I gave advice on this topic. You can
see
the thread here

http://groups.google.ca/group/micros...feb58462b45bb7
(look out for line breaks).

Read the thread there I give a code how to work this out.
--

Stoitcho Goutsev (100)

"WinDev" <Wi****@discussions.microsoft.com> wrote in message
news:78**********************************@microsof t.com...
> What does this exception message mean?
>
> Type System.DelegateSerializationHolder and the types derived from it
> (such
> as System.DelegateSerializationHolder) are not permitted to be
> deserialized
> at this security level.
>
> This is being done after a connection has been made to a remote object
> and
> I'm trying to setup a callback to the client.
>
> TIA - Jeff.
>
>


Jan 16 '06 #4
Thanks for the help. I'll give it a try.

Jeff.

"Stoitcho Goutsev (100)" wrote:
Jeff,

SubscriberInfo is a class form the original poster project
What you need is the info form my first message in the thread. I didn't want
to repost it, but here it is

"Since .NET v1.1 Microsoft demand more security restrictions on remoting
serialization. As a result in .NET v1.0 it is was possible to create a
channel as
ChannelServices.RegisterChannel(new TcpChannel(XXX));
However, with v1.1 we need to do more work to relax those restrictions and
make handling events possible.

On the server site you relax those restrictions as follows
BinaryClientFormatterSinkProvider clientProvider = null;
BinaryServerFormatterSinkProvider serverProvider =
new BinaryServerFormatterSinkProvider();
serverProvider.TypeFilterLevel =
System.Runtime.Serialization.Formatters.TypeFilter Level.Full;
IDictionary props = new Hashtable();
props["port"] = 4000;
props["typeFilterLevel"] = TypeFilterLevel.Full;
TcpChannel chan = new TcpChannel(props,clientProvider,serverProvider);
ChannelServices.RegisterChannel(chan);
On the client site
BinaryClientFormatterSinkProvider clientProvider = new
BinaryClientFormatterSinkProvider();
BinaryServerFormatterSinkProvider serverProvider = new
BinaryServerFormatterSinkProvider();
serverProvider.TypeFilterLevel =
System.Runtime.Serialization.Formatters.TypeFilter Level.Full;
IDictionary props = new Hashtable();
props["port"] = 0;
props["typeFilterLevel"] = TypeFilterLevel.Full;
TcpChannel chan = new TcpChannel(
props,clientProvider,serverProvider);
ChannelServices.RegisterChannel(chan); "


--

Stoitcho Goutsev (100)

"WinDev" <Wi****@discussions.microsoft.com> wrote in message
news:19**********************************@microsof t.com...
Stoitcho,
Either I'm missing something or the code isn't complete. There are a
couple
of things it's looking for that can't be found. There's a class called
SubscriberInfo that it can't find the constructor for with 3 elements. I
also had to create a reference to it.

Am I missing something or
"Stoitcho Goutsev (100)" wrote:
Jeff,

Since .NET 1.1 there is more strict security demands when serializing in
remoting scenarios. Some time ago I gave advice on this topic. You can
see
the thread here

http://groups.google.ca/group/micros...feb58462b45bb7
(look out for line breaks).

Read the thread there I give a code how to work this out.
--

Stoitcho Goutsev (100)

"WinDev" <Wi****@discussions.microsoft.com> wrote in message
news:78**********************************@microsof t.com...
> What does this exception message mean?
>
> Type System.DelegateSerializationHolder and the types derived from it
> (such
> as System.DelegateSerializationHolder) are not permitted to be
> deserialized
> at this security level.
>
> This is being done after a connection has been made to a remote object
> and
> I'm trying to setup a callback to the client.
>
> TIA - Jeff.
>
>


Jan 17 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Salvador Ponticelli | last post: by
1 post views Thread by Barry Anderberg | last post: by
reply views Thread by Mike Grishaber | last post: by
2 posts views Thread by Natalia DeBow | last post: by
7 posts views Thread by Sharon | last post: by
4 posts views Thread by Sharon | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.