1. Sorry didn't mean to reply outside of the list. (just hit reply).
2. When I was talking about serializer not being used at all that in the case of .NET 
-> COM, sorry if it wasn't clear.
3. Maybe if you can produce small test client/server I'll be able to help.

Regards


-----Original Message-----
From: Michel Liesmons [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 06, 2003 5:41 PM
To: 'Zaslavskiy, Dmitriy'
Subject: RE: Remoting fails with Enumeration fields


Hi,

Thanks for the info, but how do you explain that, without changing
anything, dllhost.exe seems to find the enum's assembly ok
when the method gets called from another component?
The enum is defined in the same assembly as the method, and other
methods (unsing an int instead) are found quite OK.
VS.Net copies the referenced assemblies into the referencing /bin
automatically.
In short anything else publicly defined in that same assembly is found,
even the enum itself by intellisense when coding the client. It is a
pure run-time serialization problem.
As for the serializer not being used, I have my doubts, as both client
and component are pure .Net (C#) modules.
I will try tomorrow with a remoting client and keep you informed.

Kr,
Michel.


-----Original Message-----
From: Zaslavskiy, Dmitriy [mailto:[EMAIL PROTECTED]]
Sent: donderdag 6 februari 2003 21:33
To: 'Michel Liesmons'
Subject: RE: Remoting fails with Enumeration fields


Once again I don't think it's a bug!
1. When you call serviced component (meaning COM component) different
type of marshaling is involved and the serializer used in .NET remoting
is not used at all.
2. If you had problem with serviced component written in .NET than again
the problem is likely due to the fact that CLR cannot find your dll
because unless it's in GAC it will do probing. But keep in mind that
process is dllhost.exe and is not likely located in the directory you
want.

PS If have a quick sample that quite successfully makes a remote call
(.NET remoting) call passing
custom enum.

-----Original Message-----
From: Michel Liesmons [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 06, 2003 3:05 PM
To: [EMAIL PROTECTED]; Dmitriy Zaslavskiy
Subject: Re: Remoting fails with Enumeration fields


I'm quite sure it must be a bug and indeed have something to do with
serialization.
I experienced the same problem only yesterday.
Only I was not using remoting but calling from an .exe a method in a
serviced component. This implies cross process access and thus
serialization. The error message I got was exactly the same.
I tried marking the enum explicitly as serializable but to no avail.
Since it was only a test .exe I added an overload with the parameter
defined as an int. Calling the method from other serviced components in
the
same Application (process) works just fine.
I'll just ask my customer to log the problem, they have a support
contract.



This message is for the named person's use only. It may contain sensitive and private 
proprietary or legally privileged information. No confidentiality or privilege is 
waived or lost by any mistransmission. If you are not the intended recipient, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it and notify the sender. You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient. CREDIT SUISSE GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON 
or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve 
the right to monitor all e-mail communications through its networks. Any views 
expressed in this message are those of the individual sender, except where the message 
states otherwise and the sender is authorized to state them to be the views of any 
such entity.
Unless otherwise stated, any pricing information given in this message is indicative  
only, is subject to change and does not constitute an offer to deal at any price 
quoted. Any reference to the terms of executed transactions should be treated as  
preliminary only and subject to our formal written confirmation.

Reply via email to