I have the server-side .NET Framework 4.0 project Server1.vbproj that references System.EntrepriseServices, and some classes that inherit ServicedComponent. I compile and register the dll with regsvc on servermachine1 and the COM+ application Server1 is created. I export the COM+ application as a proxy, install it on clientmachine1, and set the remote server to servermachine1. The proxy contains only the .tlb files.
I have the client-side .NET Framework 4.0 project Client1.vbproj that references Server1.vbproj which instantiates classes of Server1 with the New keyword (not with CreateObject). When running Client1.exe on clientmachine1, an exception is thrown, stating that Server1.dll is not found. If I register Server1.dll in the GAC of clientmachine1 it works.
The penetration assessment indicated, that it is not correct to have server-side dlls on the client.
I could nowhere find how to use System.EnterpriseServices client-side, is there somewhere some documentation?
Is it possible to get the client to work only with the proxy, without the server-side dlls?
Clients are Windows 10, servers are Windows Server 2012.
