Thinking about the simplest prototype of a project that calls more than 100 existing DLL 2

The simplest prototype:

Assume that a Class Library provides a method

 
  Public ClassUsermanager
{
PublicOutput getuser (input );{...}
}
 

The input onput class represents the format of the input and output parameters respectively. serializable cannot be serialized directly across domains.

Usermanager is not serializable and cannot use marshal by value for cross-origin operations.

Usermanager does not inherit marshalbyrefobject and cannot perform cross-origin operations by Marshal by refrence.

 

There are several small technical difficulties

1. How to turn a class that does not implement serializable into a serializable class required for cross-origin operations (the following chapter solves this problem)

2. Is there a simple way to implement cross-origin simplicity?CodeOperation, just like calling a DLL directly

3. Can the final implementation be debugged?

4. Whether other functions can be attached. For example, you can enable or disable logs for all interfaces without writing additional code (Method Input and Output execution time)

5. The Code should be concentrated in the framework. The people who actually use the business should be as convenient or transparent as possible.