Hi Erik,

The message says that the Proxy Adapter, running inside Lightstreamer Server, tried to launch the Remote Server, but the process exited. We should then try to find the log of the Remote Server.
By its default configuration, the Remote Server produces a log called DotNetServer.log in the same directory where the exe is located (i.e. adapters\StockList_pipes\DotNetAdapter\dotnet_1.1) . Can you see it?

To simplify tracing the problem, you can alternatively configure the Remote Server in the Standalone Version and try launching manually the Remote Server with and without your compiled adapters.
Just change the library in DOCS-SDKs\sdk_adapter_dotnet\examples\DotNetStockListDe mo\Deployment_Standalone_Version\Deployment_DotNet _Server\dotnet_1.1 and run DotNetServers.bat on the parent directory.
This also causes a DotNetServer.log file to be created.

Note that some compatibility problem in the Data Adapter library can explain a failure in the Metadata Adapter part, because the Remote Server, at startup, always loads all "dll" files it finds in its directory.

We cannot explain the size difference from our compiled dll and yours. Note that we compiled the demo outside Visual Studio, by invoking
Microsoft.NET\Framework\v1.1.4322\Csc.exe
and with the following code generation options:
Code:
    define:TRACE;DEBUG
    debug:pdbonly
    optimize-
Dario