Server Side custom exception

[escristian]

I created a Custom Exception that inherits from ApplicationException.
This is declared in an assembly that is on the server side.

I made this class serializable and overloaded all the necessary
constructors for the serialization to work. The problem is that rigth
now I'm forced to have the assembly from the server side present on the
client side. If not will get an error saying:
"Cannot find the assembly <name>, Version=<version> ......."

I cannot have this assembly on the client side, and I would prefer not
have to create a DLL only for an exception. Is there any way to get
this custom exception to work without having to carry over the server
side code?

 

[Guest]

escristian,
This does not make sense. How can you expect client code to create an
instance of a custom exception object that it knows nothing about? Is this
remoting? Your post wasn't clear about the environment.
Peter

 

[escristian]

Sorry, I forgot to mention. This is a remoting environment using C#.
The .NET is 1.1

I was hoping that Remoting with Serialization would remove the need to
have the server side DLL on the client. BUt now that I think more about
it you still need the client to know what the custom exception is all
about, so you need the server code in the client side.